Okay, so I apologize in advance if this cannot be posted here. My reason for doing so, is because I need some help with a Zenwatch 2 by Asus and the thread pertaining to this device seems to be a ghosttown. So if you need, please move this where it should go, but not without offering a word of advice or two first
So obviously I have a zenwatch 2, and I was tinkering with it earlier, and somehow got it stuck in CVC fastboot or something like that. I was able to get TWRP on it (Thank god, im much more optomistic now) but I am still having trouble getting an OS back on it. At first I wasnt even able to read the internal storage from my computer, or even begin to sideload anything, but I went into the TWRP settings and repaired the partitions to EXT4 or something of that sort. Now I am able to sideload, as well as access the storage from my PC, but I have had no success in flashing a working OS.
Im usually pretty familiar with android, rooting and unlocking, but these watches seem to be a bit different.
If anyone has anything that would help, please feel free!
The exact model of watch I have is WREN W1502Q .... I think.
Thanks in advance!
UPDATE:
I got it to boot!! Now I am stuck with a hang on that screen with all the swirly dots (the four separate animations that is right before boot)
So we're making progress, but I dont know if it is just gonna take a long time to boot, or if it is hanging! Hopefully we can get over this last hump. Thanks!
UPDATE 2:
Back up and running!
Praise the Lord!
Related
EDIT: Well I managed to get clockworkmod installed and everything; still having some issues with aspects of it, but in general I'm good. I'll probably make a dedicated thread to the device; if anyone wants to suggest a proper forum section, be my guest.
Ok, so I need some assistance on installing CWM or another recovery mode on my YourPad P4. I've already rooted and installed ROM Manager, but it could not find a compatible CWM version.
Now, first off I have also been unable to get an exact or better identification of this tablet other than it being sold as a "YourPad P4" and that it's model is MID; so I might also need help getting more details to better assist the finding of a compatible or working recovery.
Here is some information about it...
* Site purchased from/detail page:
http://www.yourstoreonline.net/yourpad_p4_new_android_40/id2040716/product.html
Don't worry, I got it for ~$100 (with the 1GB RAM upgrade), not the displayed price on the site!
* About tablet page info:
Model number: MID
Android version: 4.0.3
Kernel version: 3.0.8
[email protected] #2
Build number: 20120807-A721
Also, before I start messing with it I was going to make a nandroid backup to share for others...does nandroid backup firmware as well? I've never needed to restore a backup so I have no idea what goes into it and can't find a quick answer. I'd like to make a backup of a clean as possible system to share for anyone wanting it. Although I'm surprised that its not been mentioned on xda, I'd expect this tablet to have at least been asked about once considering it was mentioned on woot.
Thanks to anyone for any help, and I apologize if this should be in a different section. If so, could a mod please move it before any fuss is made.
And now, I'm off to bed (so I won't be responding/checking this for a few hours).
Not to sure about the rules for thread bumping, but I just wanna make sure this gets seen soon (as I'll be very busy and it will be hard to work on it next week and the the days that follow).
Also I thought it was worth mentioning now that only really mentions of this tablet I can find are in posts by me, ahahahahaha
EDIT: Oh, and I havn't verified I even have a recovery partition yet as I can't cat /proc/mtd
it's been about a week now and no response; I even posted it over here http://www.androidtablets.net/forum...cs-need-help-recovery-install-yourpad-p4.html
so bumping, if anyone at the very least knows some mystical other worldly site that somehow manages the chance of providing me an answer over the ever amazing xda; please post
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
AJ88 said:
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
Thanks alot for this, I'll definitely read it over a few times before attempting. Hopefully this will work out. Thread is still open for any other input, so anyone else coming here that can provide any additional help go ahead and post.
Well I still have been unable to get a recovery option going. I tried the link mentioned by AJ88 and it didn't work for me. Essentially the link boiled down to 2 simple adb commands and a custom recovery.img. First step was to "adb push recovery.img /data/", but I ran into a permission denied issue and could not figure out a way around it (didn't want to mess with chmod, but I did run the "fix permissions" script in the clockworkmod rom manager. So instead I just pushed the recovery.img to my sdcard. Next step was "adb shell "cat /data/recovery.img > /dev/block/nandg; sync""; so instead I went "adb shell" then su to make sure I didn't get any more issues, then just "cat /sdcard/recovery.img > /dev/block/nandg; sync". Rebooted and tried all combinations of key pressings to access recovery with no luck (even tried via adb). So any ideas on my next course of action?
youtPad P4 issues
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Well I've been waiting for a reply to either of my threads with no luck, so today I figured I'd just try again the method of manually setting up a recovery, and this time I just decided to try and hold every button I could while powering and and BAM RECOVERY MODE *****ES!!!!!! So guess either I must've just screwed up last time or something. Anyways, I'll edit the OP to reflect all this later...maybe start a dedicated thread with any quirks I figure out down the line using this tablet; and of course post my nandroid backup. When I setup my 2nd YourPad, I'll make sure to make backups of any files I may have had to change (ie, nandg, etc). The question is, what section would such a thread belong?
5lita5 said:
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Click to expand...
Click to collapse
I don't feel any buyer's remorse...yet at least, haha. If I end up having the same issues as you, maybe I'll change my mind; but I really don't see much wrong yet with this tablet. I mean, obviously its cheap and all, but for the poor man its fantastic. But ya, I HATE the YourStore, they took FOREVER to ship out the tablets. Anyways, for people like you, it really makes me thing I should take point on this tablet and start a dedicated thread.
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
After reading http://forum.xda-developers.com/showthread.php?t=2433323 I am starting to think a lot of these topics go unanswered and point to a flaw in the flasher, my region.prop is also missing and can only presume the tablet requires this for an update and the factory reset removes the root so cannot push another .prop over. So for all intents and purposes the tablet be fooked. I really do hope I am wrong but if i am right then why is this flashing tool still available after so many screw ups.
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job. I've flashed many things over the years and never screwed one up so this is bit of a shock to the system, My first reaction to your reply was to reply don't be smart then my second was to go check tool again, then third was ah f*#k. 26 letters in the alphabet and sony had to call the next model an S too. I cant say i keep up with tablet technology so thought they same thing pre flash,I didnt expect my tablet to be replaced in market so quickly after i bought one. Oh well lesson learnt now the question is wtf can be done if anything. If i send in for repair do they spot this instantly and try hammering me for a heavy bill to fix. Its under guarantee but they do say software issue they wont touch it.
I did read a lot about these problems but only reference i can find was today on page 36 of the flasher tool post. I blame mondays and my obvious lack of cognitive skills on them.
dex9mm said:
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
Can it be fixed?
nkxtc said:
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job.
Click to expand...
Click to collapse
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
soilchemist said:
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
Click to expand...
Click to collapse
Now thats why i thought it was ok i read that site first too rather than here. Too much reading after the event not before. So who are these idiots at androidadvices.com? The advice below is from that site and is what got me to reset tablet. Now i'm even more annoyed at this.
Note: Just in a rare case if the device doesn’t boot up or show the home screen then long press the power button to turn off and then re follow the instructions.
nkxtc said:
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
Click to expand...
Click to collapse
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
stifilz said:
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Click to expand...
Click to collapse
nkxtc said:
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
Click to expand...
Click to collapse
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Here comes a rant
stifilz said:
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Click to expand...
Click to collapse
I did notice but i eternal optimist and sorta hoped they different files even though filesize gave it away plus I already had that file from your links in sig but wouldnt be first time a company names files the same but different regions. Factory reset did numerous times now.
Didnt realise could get adb from logo screen so got hopes up again when lo and behold there in device manager was MTP device. After couple hours messing with it and getting lots of errors saying no driver etc I figured out putting hardware id in different adb usb driver inf files (USB\VID_054C&PID_05B3&REV_0100) would give me a working driver or so I thought. The PC decided after few minutes to give yellow exclamation and driver no longer works. Persevered with it until got driver stable but from command prompt adb says no devices in list.
Now all this happened early hours since 3am so not having greatest amount of patience (4hours not bad) i took a huff turned everything off and said [email protected]#k it ive had enough. This aint ever gonna work im resigned to this fact.
Now i may have not read one tiny part of the AIO tool which turned out to be biggest mistake i made in all this however for anyone else unfortunate to have a blonde moment would it not be possible to put some sort of checker in the tool to determine what is actually attached to be flashed based on hardware ID or something before any system changes occur. Having flashed many many devices from phones to consoles each and every one has a check of some sort before hand.
However putting that aside I think its disgraceful how Sony have treated this tablet and how locked down it actually is. This pains me but the £300 wouldve been better on a damn ipad.
@stifilz appreciate help you tried to give mate
can you please help me with a soft unbricking of my lg g vista (vs880 [11b]) from verizon usa? i found the 880-11b firmware file, at least i think its the right one. if you know of/ come across this and are sure of its validity i would trust that more. i found and downloaded via a google search. i initially think i may have accidentally deleted the splash pic for the carrier when it boots. this caused it to just black screen after the lg logo n the backlight would flash like it was stuck in a boot loop just the image file was missing. after a little more research i figured out how to put it in the download mode so that i can use a pc to try repair or reinstall whatever it needs. i am unsure if i need the sdk or adk toolkits for a repair in the download mode to work. while on that screen it says its plugged in and waiting to download firmware via usb under the progress bar it tells me not to unplug until download is completed. its not showing up in "my computer" however. and i've never had to do s software/firmware download or setup when the phone wasn't in full normal working order. i simply want to put back the out of the box software back in place. firmware 88011b and 4.4.2 os. just want to be sure i get the proper files/and or programs/ directions to use those resources properly the last thing i want is to guess at something that i could ask someone more experienced for help with and end up bricking it beyond repair. any and all help is very appreciated and i must ask you to please explain each step as clearly and "dumbed down" as possible as you can. if i need to use a program i've never used before {i.e. i hear things like odin mentioned in the forums but i don't understand or have any experience with any pc to phone applications so the more detailed any instructions can be made the better. anything that most ppl who have started tinkering with their devices usually know as common sense or steps that seem implied if not specifically mentioned i'll miss. i have been reading n lurking for months n managed to root the device. but had another issue i accidentally caused soon after which resulted in a factory wipe and some time to remember what i did that rooted it after spending a day on it the first time n trying many things it took me a while to refind what i had done that worked. then this happened. i'm sure with the proper files/tools it'll be fine but i need help to know what those are and to be sure i do it right the first time. i know if i don't there may not be a second chance. thank you again in advance for your patience and help.
Of anybody could help me that would be absolutely fantastic. I was half asleep in a thread on trying to get a custom recovery for my Verizon Ellipsis 7 (quanta qmv7a) and I found a recovery.img and it was noted that it was a test. I'm just curious of anyone knows how to fix my brick because the recovery won't load and I'm now stuck in a boot loop, the "welcome" screen comes up and goes away and comes up again repeatedly. Is there a way I can adb flash this tablets stock recovery? I still have the original recovery.img I just need to figure out how to flash it when its boot looped due to a wrong recovery.img flash. Help is greatest appriciated! Thank you!
bump
-The complete lack of responses could mean that we're screwed... (or we've asked a dumb question).Today, I too was a little too eager with the Enter button without triple-checking if the version of the recovery would be compatible with my current ROM -- it obviously wasn't -- Ellipsis_boot_patched_140902-025705.img over the top of 4.4.2 -- should have done more homework
Google's bots have hit this thread -- I hope we can help others who find this thread in our predicament and give solutions -- not just be a dead-end as it is now.
It's only been 4 hours since I've been working on it... it had an unlocked bootloader so there is hope.
I can tell what _doesn't_ work straight away:
1. Pulling the battery cable -- the back cover comes off easy -- insert a credit card starting at the SIM/SD slots and work your way around the cover and then gently pull the battery harness from the battery terminal assembly -- At least I don't have to see WELCOME taunting me by flashing every few minutes.
2. Combinations of button pressing -- I tried all the dead-Andi tricks...
3. Adb and RSD-lite aren't being acknowledged.
For just a few seconds before re-cycling -- Windows DOES recognize the phone (via USB) -- enough time to (indirectly) put a batch file in the bootloader?
-- or the answer could come from a combination of all the above.
After months of tweaking, I had just gotten the 16G SD card to be stable and (fairly) transparent as the main-APP drive -- Thanks mostly in part to Vicky's recent overhauling of her app: Apps2D -- I don't want to abandon all those hours without giving it one last concerted effort.
I am also willing to give playing with the physical ROM a try (-- I pray it's not embedded in the Soc). I remembered all the fun I had with JTAGs all those years ago when I was messing with DSS systems.
The tablet was a grateful gift to me but would not be one I would have ever purchased... The Ellipsis 7 was one of the first "cheap" tablets on the market... it shows. I would never use it professionally -- but wouldn't hesitate to use it as a backup or taken out camping...
I'm giving this a 30% chance of success.... well, i'm in the market for a new tablet... maybe one of those new Win8/Marshmallow dual-booters made-in-China?
You say you have the original recovery.img could you send me that please?
ThatGuyWhoLovesRoot said:
Of anybody could help me that would be absolutely fantastic. I was half asleep in a thread on trying to get a custom recovery for my Verizon Ellipsis 7 (quanta qmv7a) and I found a recovery.img and it was noted that it was a test. I'm just curious of anyone knows how to fix my brick because the recovery won't load and I'm now stuck in a boot loop, the "welcome" screen comes up and goes away and comes up again repeatedly. Is there a way I can adb flash this tablets stock recovery? I still have the original recovery.img I just need to figure out how to flash it when its boot looped due to a wrong recovery.img flash. Help is greatest appriciated! Thank you!
Click to expand...
Click to collapse
I am still trying to work on one, could you send me the original recovery.img if you still have it? Thanks
Bondaddict said:
I am still trying to work on one, could you send me the original recovery.img if you still have it? Thanks
Click to expand...
Click to collapse
i actually threw it away, but i have another that isnt bricked ill pull the recovery from that one if you would like. it wont be for a couple weeks as my daughter was just born and i havent had time to do anything on my pc. just let me know ill get back when i can
That would be awesome
ThatGuyWhoLovesRoot said:
i actually threw it away, but i have another that isnt bricked ill pull the recovery from that one if you would like. it wont be for a couple weeks as my daughter was just born and i havent had time to do anything on my pc. just let me know ill get back when i can
Click to expand...
Click to collapse
Ya if you could do that that would be amazing! Could you also include how you suspended the pre boot?
Bondaddict said:
Ya if you could do that that would be amazing! Could you also include how you suspended the pre boot?
Click to expand...
Click to collapse
Is there a chance that you have the entire ROM? I tried to root and ended up bricking the device
Hello all!
First of all, I am no developer.
Long story short.. I purchased an HTC 10 because I was sick and tired of my at&t galaxy s5 being bootlocked. I received the 10 and set out the next day to root it. I followed a video on youtube (not saying that the info was not correct...I may have done something wrong...not trying to discredit anybody) to the letter and lo and behold I ended up in a bootloop. My heart probably came close to a complete blockage at this point. This bootloop lasted maybe a minute before it would reboot. So... In my infinite wisdom I chose to relock the bootloader. Oh Boy!!! Fun times were ahead for me!! As soon as I relocked said bootloader, the bootloop increased its timing to about 1 point 5 seconds. I remember waking up on the floor in the fetal position. Now I am stuck with a phone that adb will not recognize. It does however recognize the device at the fastboot devices prompt. So my question is this.... Is this a salvageable phone? If so, How would one go about fixing this problem?
*** Relocked ***
htc_pmew1 pvt S-ON
os-2.28.617.8
I would prefer that the money I spent on this thing would amount to something more than a small ant bed.
Any help at all would be greatly appreciated. Also I have been doing a lot of digging around and (I may be wrong) but. I could not find this scenario in the forums here. I apologize if this has already been covered.
...So..after looking around for a bit more, I discovered out that there is a way to flash a ruu/zip from an sd card. I have tried multiple times with what I thought were the right ones. As I am unable to boot into recovery, I feel I am limited as to what I should do. I have read about that I should wipe dalvik but I am very limited in my knowledge on an android system and would prefer to not mess this phone up anymore than it already is. I was trying to root and I used TWRP as the recovery but I never made it to the end before it started the loop. The Phone is an htc 10 unlocked version. and it just constantly reboots about 3 seconds apart. ADB says no device connected, so I cannot execute commands that way... really at a loss here. all the tutorials I have read refer to using and and being able to boot into rrecovery. when i boot into recovery, I get an immediate reboot and the 3 second bootloop forever. Is there a way to use twrp to somehow resolve this?Is there a tool that will help me at least get into recovery mode?
SOLVED... Ran across Batchtool by sneakyghost. Quite the bunch of tools there! Ended up solving my problem by placing the stock RUU in the root folder as the batch tool. Before I could not install from a factory RUU (would not recognize the phone through ADB or install the RUU. After the install of the batch tool I was able to get a clean install back to my factory settings.. Now I am free to mess it up again!!
BIG THANKS TO SNEAKYGHOST!!!!!
I'm unsure why the batch tool has worked for you and the sdcard method didn't - getting fastboot to work and all the bits and pieces together (drivers, Windows VCRedist, correct fastboot, correct adb) is usually more error prone than just identifying the correct zip and placing that in your sdcard root.
At this time, I'm a bit in a "scratch my head" mood, thinking this is weird. Same zip? Really the same zip didn't work from sdcard but would work in fastboot? I think I haven't come across that myself yet (non booting phones are a daily thing, almost).
I wish I had the time to analyze your steps with you, so I could gain understanding as to why that happened, so I can use that in the future, but alas! I have no time for XDA and deep digging around in issues of other people. Lately I can't even solve my own phone's problems anymore due to too many other things going on.
Well, glad it worked for your phone, anyhow. I'll keep this in mind for the next one messing up his/her phone.