Related
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
I managed to borrow a Samsung Satellite laptop, so I could root and unlock my Nexus 6. Laptop is brand new. Everything was great on unlocking and rooting using Wogfresh's Nexus Tool Kit.
Then I decided to stop the forced encryption. Used Wug's Tool Kit again. At the end it says phone will reboot in 15 minutes. I waited over a half hour. Then I tried rebooting the phone. Now it flashed teamwin.
I can get it turned off. And I can still get it into recovery, bootloader mode, etc. I worked on this from 16:30 - 05:30 yesterday. I have been working today for another 3-4 hours.
Wug's Tool, the computer will not recognize the phone. Any help would be greatly appreciated. This is sooooo frustrating! I have uninstalled drivers, updated drivers, usbs too. I did everything Wug's kit said to do.
Sent from my SGH-I337 using Tapatalk
first off, stop using toolkits!
doing it properly is just as easy, and takes about 4-5 minutes, to unlock the bootloader, flash the recovery, flash the supersu zip, and to flash a custom kernel that wont bring on encryption(but you have format data for un-encryption to work).
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
simms22 said:
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Click to expand...
Click to collapse
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
addcancercat said:
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
chris6278 said:
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
Click to expand...
Click to collapse
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
simms22 said:
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
Click to expand...
Click to collapse
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
chris6278 said:
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
Click to expand...
Click to collapse
show me one post where i acted like an ass when someone needed help.
Simms is correct, its much easy to unlock using fastboot rather than a tool kit. When I first started modding it took me >5 minutes to learn how to do this. It always works and can really help you if you mess something up using a tool kit. If the OC doesn't recognize your phone, what screen is it showing (the TWRP logo) have you tried to hold power and volume down to boot into the boot loader? If you can boot into BL then you can flash anything via fastboot and fix this problem easily.
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
addcancercat said:
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
Click to expand...
Click to collapse
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
simms22 said:
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
Click to expand...
Click to collapse
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
this should help you out. if you have anything to adk about it, ask there or here. good luck! http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
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!!
Hi,
I have an unbranded and unlocked nexus 6. I wanted to root and install twrp so I can begin flashing custom roms... Only problem is, I don't have a pc at home to ADB flash twrp, etc.... Is there any method to flash custom rom without having a machine at home? I have absolutely no need for a pc at home, until this precise moment when I get a new phone and I want to start flashing, lol. Im gonna assuming the answer is NO, im thinking there may be some OTG method with files from a thumb drive, but I'll wait to hear from the experts. Thanks in advance.
I have been wondering that very question myself. I really doubt it's possible, but since I have had my N6 and LG G Pad, I don't ever use my antique Pentium 4 Dell PC hardly at all.
Sent from my Nexus 6 using Tapatalk
It's totally possible but highly recommended against. There is an app to root, which then you use flashify to flash recovery but if you ever have a problem, you won't be able to fix it because you need a PC to get a rom back on your phone if you accidentally wipe the os or do some other mischief that prevents you booting, you wont be able.to unlock your bootloader which means you won't be able.to.flash stock or return for warranty purposes either, so as.much as you want to do this, it would really put you in an awful position and you'd be screwed if something goes wrong, which the chances are, it will.
danarama said:
It's totally possible but highly recommended against. There is an app to root, which then you use flashify to flash recovery but if you ever have a problem, you won't be able to fix it because you need a PC to get a rom back on your phone if you accidentally wipe the os or do some other mischief that prevents you booting, you wont be able.to unlock your bootloader which means you won't be able.to.flash stock or return for warranty purposes either, so as.much as you want to do this, it would really put you in an awful position and you'd be screwed if something goes wrong, which the chances are, it will.
Click to expand...
Click to collapse
I have no issues with the first potential problem you mentioned (having to get a rom back on phone using a pc) because I have a backup phone, plus if it gets to that stage, I can use a friends computer if I really need to. But the last comment you made about the chances of an error occurring and saying that it most likely will and i'll be unable to get it back to stock scares me. Is this method really that unreliable? I will read up on it more, and search through the forums.
If you can provide details of the app to root, that would be great. Also, how reliable is the app to root alone by itself? Minus the flashify portion...
nseriessaga said:
I have no issues with the first potential problem you mentioned (having to get a rom back on phone using a pc) because I have a backup phone, plus if it gets to that stage, I can use a friends computer if I really need to. But the last comment you made about the chances of an error occurring and saying that it most likely will and i'll be unable to get it back to stock scares me. Is this method really that unreliable? I will read up on it more, and search through the forums.
If you can provide details of the app to root, that would be great. Also, how reliable is the app to root alone by itself? Minus the flashify portion...
Click to expand...
Click to collapse
It's not the method that's unreliable the app "kingroot" (I believe it is called) works fine. The issues occur with everything and anything else root users do. Flashing a rom, a mod, wiping the os via recovery etc.
Then if anything hardware goes wrong, returning the device for repair under warranty will likely be rejected if its not stock.
danarama said:
It's not the method that's unreliable the app "kingroot" (I believe it is called) works fine. The issues occur with everything and anything else root users do. Flashing a rom, a mod, wiping the os via recovery etc.
Then if anything hardware goes wrong, returning the device for repair under warranty will likely be rejected if its not stock.
Click to expand...
Click to collapse
Gotcha, so maybe I can just root and install apks of apps I really want like adaway, etc... then I should be fine as long as im not using the flash method correct?
nseriessaga said:
Gotcha, so maybe I can just root and install apks of apps I really want like adaway, etc... then I should be fine as long as im not using the flash method correct?
Click to expand...
Click to collapse
I'm not going to commit to an answer there
One thing I will say though, you'll never be able to update with an OTA, so if you're going to root, have a custom recovery,. Allow.oem unlock and have an unlocked bootloader.
Best bet is to do the proper.routing and unlocking using your friends of as a one off. You can then safely.maintain the phone without a pc and use the pc in am emergency. Not unlocking the bootloader from the beginning is.asking.for.trouble
Man I need a new keyboard
danarama said:
I'm not going to commit to an answer there
Click to expand...
Click to collapse
lol I understand.. thx m8
nseriessaga said:
lol I understand.. thx m8
Click to expand...
Click to collapse
Edit above
danarama said:
I'm not going to commit to an answer there
One thing I will say though, you'll never be able to update with an OTA, so if you're going to root, have a custom recovery,. Allow.oem unlock and have an unlocked bootloader.
Best bet is to do the proper.routing and unlocking using your friends of as a one off. You can then safely.maintain the phone without a pc and use the pc in am emergency. Not unlocking the bootloader from the beginning is.asking.for.trouble
Man I need a new keyboard
Click to expand...
Click to collapse
k, I already used the kingroot method and verified using root checker. Installed adaway and everything seems to work perfectly (so far anyway). Uninstalling Kingroot unroots the phone from my quick series of test that I've run so OTA updates doesn't seem like it'll be a problem.
I agree though, if I really want to do any rom flashing, ill just unlock, root, and flash using "proper methods".
Appreciate all your help man.
nseriessaga said:
k, I already used the kingroot method and verified using root checker. Installed adaway and everything seems to work perfectly (so far anyway). Uninstalling Kingroot unroots the phone from my quick series of test that I've run so OTA updates doesn't seem like it'll be a problem.
I agree though, if I really want to do any rom flashing, ill just unlock, root, and flash using "proper methods".
Appreciate all your help man.
Click to expand...
Click to collapse
Uninstalling Kingroot removes root but does not uninstall all modified files. Will show as modified and thus no OTA updates. Another thread on same thing here somewhere. Have to flash system back to stock with PC for any updates.
---------- Post added at 11:13 AM ---------- Previous post was at 11:01 AM ----------
It's also not safe to update without bootloader unlocked anyway. Too many reported bootloops with OTA.
prdog1 said:
Uninstalling Kingroot removes root but does not uninstall all modified files. Will show as modified and thus no OTA updates. Another thread on same thing here somewhere. Have to flash system back to stock with PC for any updates.
---------- Post added at 11:13 AM ---------- Previous post was at 11:01 AM ----------
It's also not safe to update without bootloader unlocked anyway. Too many reported bootloops with OTA.
Click to expand...
Click to collapse
Exactly this. All root methods edit.existing files but do not restore them after unroot. So the system is modified. We're.100% certain there will be no OTA.
Unlock the bootloader and do it properly.
Ok thanks guys. I guess eventually I'll have to get my hands on a PC lol. Thanks again
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Highway 55 said:
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I agree. I need some one with skype to walk me though it. I literally followed step by step guides on youtube without knowing what I was doing, it was my fault.
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
I hope everything turns out okay and you get your phone working again. I would Skype with you but I'm on dad duty with my kids tonight. Good luck!
Sent from my Nexus 6 using Tapatalk
Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
That was your mistake. If never messed with Android worst thing you could do is jump right on a Beta build.
---------- Post added at 08:14 PM ---------- Previous post was at 08:08 PM ----------
Easy to fix if unlocked and have TWRP. Recommend going to stable build first and work your way up. At least will have a working phone. Make a backup up stable build and then play all you want. Could have made backup of stock before even flashed M and would have been golden.
What did you do when you got the corrupt message? I'm asking because many people get this message but if you ignore it, it should boot up anyway.
slosrtnick said:
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
Click to expand...
Click to collapse
yeah I got it! i watched a video on re-flashing M? I think? It works now, I'm still not sure how to back up my stuff properly but I have a working phone! Thanks for the reply!
Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
It sounds like all you need to do is: when you get to that "phone is corrupt" screen, press volume down and then the power button to continue.