Database Develop

[q] nexus 7 toolkit auto update v4.3.4

Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave

Nexus 7 toolkit auto update v4.3.4
NinjaMogglet said:
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Click to expand...
Click to collapse
Can anybody help please?,

No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.

Confirmation
Logan_M said:
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Click to expand...
Click to collapse
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks

NinjaMogglet said:
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
Click to expand...
Click to collapse
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD

Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Unfortunately having the SDK does not mean I can actually use it
I got in over my head, hence trying to learn/read about it it on XDA
I found the thread that appeared to offer what I want,
a toolkit that I should be able to use to unlock/root with.
Thanks

But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
you dont have to know how to use the entire SDK, all you need to do is be able to follow directions. every nexus is rooted the exact same way. the only thing the toolkit does is hide the commands. you could take the few minutes to learn these commands
fastboot oem unlock
fastboot flash recovery nameofrecoveryfile.img
reboot to recovery
adb push SuperSU.zip /sdcard/ (or /data/media, whatever)
flash supersu.zip with your custom recovery....
Sent from my Nexus 7 using Tapatalk HD

Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pirateghost said:
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks

NinjaMogglet said:
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
Click to expand...
Click to collapse
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.

All Understould
Pirateghost said:
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
Click to expand...
Click to collapse
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...

NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
not sure why you need to go anywhere other than right here on XDA....
theres a freakin sticky for it even...
http://forum.xda-developers.com/showthread.php?t=2150661

NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.

Still not clear??
smt8544 said:
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Click to expand...
Click to collapse
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks

NinjaMogglet said:
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
Click to expand...
Click to collapse
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do

Thanks
Pirateghost said:
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Click to expand...
Click to collapse
Thanks...
I did not ignore your link, I read all the pages.
Especially the one's that pointed out the ommisions, like un-lock first, and some of the key presses.
I will get back to this when I'm bright eyed, not 01:25 in the morning.... Just in case.
Thanks again

[Q] Bricked my HTC ONE - please help will reward

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.

[Q] Restore Stock Recovery without a computer?

Is there any way to restore stock recovery without using a computer?
I bought a Verizon Moto X developer edition used and the guy has TWRP on it. So now I can't update to 4.4 with that on here.
I don't care if I lose all data in the process.
I'm just having a ridiculously hard time getting anything to recognize my phone on windows 8.1 and I don't have a ton of time in the first place.
I tried a factory reset from twrp but twrp didn't go away.
I DO have an old laptop with... xp on it if anyone has a step by step guide that works 100% they could point me to?
came from galaxy nexus btw.

TheBungle said:
Is there any way to restore stock recovery without using a computer?
I bought a Verizon Moto X developer edition used and the guy has TWRP on it. So now I can't update to 4.4 with that on here.
I don't care if I lose all data in the process.
I'm just having a ridiculously hard time getting anything to recognize my phone on windows 8.1 and I don't have a ton of time in the first place.
I tried a factory reset from twrp but twrp didn't go away.
I DO have an old laptop with... xp on it if anyone has a step by step guide that works 100% they could point me to?
came from galaxy nexus btw.
Click to expand...
Click to collapse
My phone was recognized by windows 8.1 and 7. Sounds like you have an issue with your drivers if its not recognizing the phone.

TheBungle said:
Is there any way to restore stock recovery without using a computer?
I bought a Verizon Moto X developer edition used and the guy has TWRP on it. So now I can't update to 4.4 with that on here.
I don't care if I lose all data in the process.
I'm just having a ridiculously hard time getting anything to recognize my phone on windows 8.1 and I don't have a ton of time in the first place.
I tried a factory reset from twrp but twrp didn't go away.
I DO have an old laptop with... xp on it if anyone has a step by step guide that works 100% they could point me to?
came from galaxy nexus btw.
Click to expand...
Click to collapse
you should use the last version of fastboot (or mfastboot), and you can set fastboot.exe to run in win7 compatibility mode

waiflih said:
you should use the last version of fastboot (or mfastboot), and you can set fastboot.exe to run in win7 compatibility mode
Click to expand...
Click to collapse
Think you could link me to the best directions for this phone? I'm reading a lot of different threads and must be way over my head. I do remember it being a hassle with my droid x all those years ago

TheBungle said:
Think you could link me to the best directions for this phone? I'm reading a lot of different threads and must be way over my head. I do remember it being a hassle with my droid x all those years ago
Click to expand...
Click to collapse
These directions for returning to stock using RSD Lite look pretty good, and include a video:
http://forum.xda-developers.com/showthread.php?t=2446515

kclantz said:
These directions for returning to stock using RSD Lite look pretty good, and include a video:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
OK so I've gotten adb working but can't get RSD lite to recognize my device. Can I just use ADB?
I'm so paranoid of bricking my new device that I fought to activate for two weeks. God damn verizon.
edit to add:
I think RDSlite is the way to go. any commonly known way to get it to find my device?

So i use: adb reboot bootloader
from there if I do: adb devices
it comes up blank like there's nothing attatched.
any ideas?
if there's a donate feature, I'll gladly donate a couple beers to anyone that can help me get this working in the next half hour...
It's not much but...

So I got everything working.... I think. RSD Lite seemed to work fine. Letting everything settle in before attempting the 4.4 update...
Thanks for pointing me in the right direction.
I thought a dev edition would have been a bit more... nexus-ey behind the scenes. Oh well, great device so far...

TheBungle said:
So I got everything working.... I think. RSD Lite seemed to work fine. Letting everything settle in before attempting the 4.4 update...
Thanks for pointing me in the right direction.
I thought a dev edition would have been a bit more... nexus-ey behind the scenes. Oh well, great device so far...
Click to expand...
Click to collapse
Glad you got it figured out, sorry I kind of left you hanging, I got busy at work.
I spent the last two weeks or so bricked and its definitely fun. Be glad you have the Dev edition. My MAXX is not, so I had to wait for the FXZ file to be released, couldn't flash anything else. Not getting the Dev edition was a huge mistake.

At the end of my patience....please help me!!!

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

[Q] Think I soft-bricked my Nexus 6...any ideas?

Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.

JeffDenver said:
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
Click to expand...
Click to collapse
Install factory images using fastboot
https://developers.google.com/android/nexus/images
You might have "soft bricked" it, but if you still have bootloader access you are fine

I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?

JeffDenver said:
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
Click to expand...
Click to collapse
you update via fastboot, while youre in the bootloader. adb has nothing to do with it.

When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.

When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.

JeffDenver said:
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
Click to expand...
Click to collapse
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.

I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app

Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112

Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
SDK is updated. I assumed it updated drivers as well. If not, where do I get those?
I do understand that fastboot only works while in the bootloader. I have not attempted to use it while in Android.

JeffDenver said:
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
Click to expand...
Click to collapse
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.

Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do I get that from?

JeffDenver said:
Where do I get that from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56913254
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Evolution_Freak said:
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
Better fear the bootloader downgrade soft brick
Sent from my Nexus 6 using XDA Free mobile app

Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you know what adb is?
:/

rootSU said:
Are you sure you know what adb is?
:/
Click to expand...
Click to collapse
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app

mwalt2 said:
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Click to expand...
Click to collapse
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?

Konfuzion said:
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.

to repeat again, you use fastboot to flash the factory img, while youre in the bootloader. it should take you just several minutes to do, or a little bit longer if you are being very carefull. adb has nothing to do with it.

JeffDenver said:
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Click to expand...
Click to collapse
its probably a good idea to factory reset since you're going up a major version and have already had problems.

rootSU said:
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
Click to expand...
Click to collapse
The reason I suggested wugs, is the first thing it has you do after installation is walks you through removing old drivers and installing the correct drivers and making sure that the phone is recognized. Then it will download the needed files and check the md5's which would help to avoid further problems.
Sent from my Nexus 6 using XDA Free mobile app