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
Hiya
I have an Alcatel Onetouch Pop C1 4015D (and for the record, I'm never buying this brand or similar junk again). I just got it un-bricked after a few months thanks to the online USB firmware updater. It's currently in pretty much its factory-default state again, preinstalled crapware and all.
What I'd like to do is install a custom ROM on it, to have a clean system I can actually enjoy owning, e.g. AOSP (if that is what I think it is: the basic, clean Android system). The problem is that I'm getting a little overwhelmed with information, tutorials linking to more tutorials, tutorials linking to downloads for which I have to "complete a survey" and such (abort abort abort), 2 different tutorials for the same thing stating different ADB commands, a few outright scams, etc etc etc. There's tons of information out there, but 90% of it seems wrong, irrelevant, device-specific or otherwise unusable. I've already spent hours on this and still haven't gotten anywhere.
I'd be very grateful if someone actually reliable could walk me through the entire, correct process, please. :fingers-crossed:
I'm just going to write down the bits and pieces of info I already have:
I've already rooted it with Framaroot; no problems there, superuser works.
I've found this site that lists several ROMs, presumably specifically for the C1, including the standard ROM and a cleaned version: tinyurl dot com/o24wqoe. The AOSP one strikes my fancy and is on my SD card already.
The same site says I can just put the provided ROMs on my SD and install them as updates via stock recovery, but I highly doubt that because I read everywhere you specifically can't do that. Sounds like fake advice to me.
I'm told I'd need to unlock my bootloader, but once in fastboot/bootloader mode none of the offered fastboot unlock commands really do anything. The "..." appears in my console and then nothing.
I've tried installing TWRP and CWM recoveries, but you know, "your device is not supported". There's this video of a C1 with a custom recovery (watch?v=_TGgXIp3fWM) and the comments claim it's CTRecovery, but I can't even find anything about that. I already submitted requests for a fix for my device to twrp and cwm half a year ago before I bricked this thing, and one person promised he was gonna make a build for me, but nothing came from any of that.
I think that's just about all the useful things I can extract from this whole mess of information I have...
Please help me make sense of this overload of info and device-specific shenanigans, and walk me through what seems to be such a simple process for everyone with a mainstream device?
For the record, I'm back down to barely being up-to-date on what is what anymore. I'm more than familiar enough with the theoretical side (bootloaders, partitions, bios, etc) because of my heavy computer usage (professional programmer), but once I get into Android I'm just lost. All that fancy terminology nobody seems to bother to explain, things that are taken for granted but aren't really obvious (like a guy demonstrating the installation of a custom ROM, and only mentioning 10 minutes into the excessively long video that you need to install a custom this and custom that first), so many alternative methods for the same thing that have different dependencies (unlocking bootloader vs custom recovery), etc... I don't know anymore what's device-specific and what isn't, who is telling the truth, what a given tutorial is actually making me achieve in the end, etc. TL;DR I'm lost, I'm not stupid but I'm not gonna pretend to know anything about Android's subsystems anymore at this point.
wow u wrote a full post and u speaked for me as have the same problem
Custom recover
i have made a recovery for the 4015x
and got one of the roms to work
(and a fixed stock recovery)
there are 6 versions of this phone and at least two different partition tables that ive seen
but getting it back from softbrick id use the "mobile upgrade s 4.1.1" from the alcatel site
alcatel,mobiles,all mobiles, pop c1, support and on the right hand side down load the program and follow
this forces a stock rom back on the phone (no root and all data wiped)
im waighting on the mods to let me post links so i can host the roms and recoverys
but if you want to mess with the roms your self you can edit the partition tables and get the roms to install.
id use the app "diskinfo" to check what partitions your system and data etc etc are useing and chainge this in the roms.
hope this helped
p.s. if not i could poss look at editing the aosp rom for you and host if for a bit
just waighting on beeing able to post links :s
Alcatel onetouch c1 pop
MY PHONES flash light or led light comes on but it wont come on at all jus remains black wont start ....i tried restoring rom but ,it was useless ,well i used the upgrade tool and there wasnt the right models for my phone what should i do now .oh and also my phone has no stock rom from nowhere on google im so in need of getting back my phone .how can i fix a bricked or whatever phone its a alcatel one touch pop c1 4015a
What is the online USB firmware updater? Mine is also bricked
I am in a bootloop that takes me to the "choose language" over and over. I have adb access but am having trouble figuring out which file to download and the commands to get a good file on my HDX 8.9.
I've done a bunch of searching but nothing seems to match what I need. Any help or links would be greatly appreciated!
Thanks
This is an easy one, but don't feel bad. It vexed me too. It is because it wants a to connect to the server and verify your account and device (in doing so, it will also try to push an update).
The solution is to click the orange "complete registration later" (or something like that) text which shows up centered on the bottom.
I'm rooted and connected to wifi already..I'm downloading update kindle 14.5.2 but I'm guessing that I'll lose root.Tthe screen blinks on the desktop of the kindle then goes back to the language...like it doesnt know what to do next.
I also see an update file thats rooted but it doesn't appear to be the right one for me...
So many instructions and downloads that it gets confusing.
Also, thanks leko for the great help with adb!!!
Oh_wow said:
I'm rooted and connected to wifi already..I'm downloading update kindle 14.5.2 but I'm guessing that I'll lose root.Tthe screen blinks on the desktop of the kindle then goes back to the language...like it doesnt know what to do next.
I also see an update file thats rooted but it doesn't appear to be the right one for me...
So many instructions and downloads that it gets confusing.
Also, thanks leko for the great help with adb!!!
Click to expand...
Click to collapse
You can root 4.5.2. If the update fixes the issue then just root and you'll be good. Once your rooted, find instructions to disable OTA here so you don't automatically update to 4.5.4, like what happened to me.
-Zman8881
Is there a rooted download I should use instead? I'm still not positive that I'm doing the right thing which is why I asked for help. And I'll definitely block those ota's..thanks for that tip
Oh_wow said:
Is there a rooted download I should use instead? I'm still not positive that I'm doing the right thing which is why I asked for help. And I'll definitely block those ota's..thanks for that tip
Click to expand...
Click to collapse
There is no pre-rooted 4.5.2; you have to root if needed. Whether you retain root from an earlier install depends on where you came from and the method used to upgrade.
The looping problem you describe has happened to others. You'll need to poke around to find the solution. Hopefully someone will pop in with a direct link or more specific instructions. Point is it's solvable. Don't do anything radical while searching/waiting for resolution.
Sent from my Kindle Fire HDX 7 using XDA Forums Pro.
I've already learned the hard way that jumping in without knowledge is painful (R.I.P my 1st kindle). This device is twitchy but the searching I've done so far has be a great learning experience! And that's the thing, I really want to learn how to do this stuff...unfortunately I may not explain the problem correctly and am terrified of getting shot down by more knowledgeable folks. I've survived modifying the Droid x, note 2 and note 3 so I know I can do this...eventually☺
Oh_wow said:
I've already learned the hard way that jumping in without knowledge is painful (R.I.P my 1st kindle). This device is twitchy but the searching I've done so far has be a great learning experience! And that's the thing, I really want to learn how to do this stuff...unfortunately I may not explain the problem correctly and am terrified of getting shot down by more knowledgeable folks. I've survived modifying the Droid x, note 2 and note 3 so I know I can do this...eventually☺
Click to expand...
Click to collapse
The only time you'll get shot down around here is if you do bad stuff (eg: flash incompatible components) that have been well covered in the forums. People are willing to help if you ask questions before getting into trouble. Kindles (at least HDX models) are tough to tame and easy to ruin.
Are you having difficulties now? You reported a soft bootloop (stuck on language screen) in a earlier post. Has that been resolved?
Davey126 said:
The only time you'll get shot down around here is if you do bad stuff (eg: flash incompatible components) that have been well covered in the forums. People are willing to help if you ask questions before getting into trouble. Kindles (at least HDX models) are tough to tame and easy to ruin.
Are you having difficulties now? You reported a soft bootloop (stuck on language screen) in a earlier post. Has that been resolved?
Click to expand...
Click to collapse
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (if I'm quick, I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Oh_wow said:
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (f I'm quick it there that I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Click to expand...
Click to collapse
This is a really random thought and I'm not sure if it will work, but when you get into the desktop try to power off and power back on. You need to be quick, but it might work.
Random is good...but it didn't work in this case.
Thanks
Oh_wow said:
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (if I'm quick, I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Click to expand...
Click to collapse
Sorry for the delay in responding; was out with family.
Like many others I am the beneficiary of the experiences, suggestions and knowledge generously shared by others. It's the collective community you need to thank
Have you looked at this thread? Post #2 seems to offer a solution. Others noted the need to disable (or more correctly not enable) wifi during initial setup which suggest a factory reset may be part of the solution. Another thread indicated the 'language looping' problem was related to corruption in the default launcher. Installing another (eg: Nova) via ADB restored some control and ability to further diagnose from within FireOS. However, this was for the prior version of FireOS (3.x "Otter") and may not be applicable to Fire OS 4 ("Sangria").
Davey126 said:
Sorry for the delay in responding; was out with family.
Like many others I am the beneficiary of the experiences, suggestions and knowledge generously shared by others. It's the collective community you need to thank
Have you looked at this thread? Post #2 seems to offer a solution. Others noted the need to disable (or more correctly not enable) wifi during initial setup which suggest a factory reset may be part of the solution. Another thread indicated the 'language looping' problem was related to corruption in the default launcher. Installing another (eg: Nova) via ADB restored some control and ability to further diagnose from within FireOS. However, this was for the prior version of FireOS (3.x "Otter") and may not be applicable to Fire OS 4 ("Sangria").
Click to expand...
Click to collapse
There's a chance it's me being stupid, but don't you need root access to do that solution? If not, do you think this kind of idea could work to get around the earlier version error or even disabling OTA without root access?
Zman8881 said:
There's a chance it's me being stupid, but don't you need root access to do that solution? If not, do you think this kind of idea could work to get around the earlier version error or even disabling OTA without root access?
Click to expand...
Click to collapse
@Oh_wow indicated in a earlier post that his device remains rooted. Otherwise most of the recovery techniques discussed in the links would not work. Sorry to dampen your hopes ...
You could try installing an alternate launcher. That should work. However making it default is annoying. If the install works and helps with the screen, I can help with setting it as default.
Download the launcher (I like Nova)on your computer. You can probably find it on apkmirror. Then, run this command.
Adb install and drag the file.
A little note. The and install command is potentially dangerous, but for some apps it is safe, and I am mostly certain a launcher counts.
Also, have you tried clicking the register later button?
lekofraggle said:
You could try installing an alternate launcher. That should work. However making it default is annoying. If the install works and helps with the screen, I can help with setting it as default.
Download the launcher (I like Nova)on your computer. You can probably find it on apkmirror. Then, run this command.
Adb install and drag the file.
A little note. The and install command is potentially dangerous, but for some apps it is safe, and I am mostly certain a launcher counts.
Also, have you tried clicking the register later button?
Click to expand...
Click to collapse
Bonanza! That solved the language question but it is annoying that Nova won't stick as default. I'd love to know how to set it! Thanks!
Now what? Gapps? Wait, safestrap or TWRP?
Nevermind---I lost root and the toolkit isn't working,,,good grief
Oh_wow said:
Bonanza! That solved the language question but it is annoying that Nova won't stick as default. I'd love to know how to set it! Thanks!
Now what? Gapps? Wait, safestrap or TWRP?
Click to expand...
Click to collapse
Getting 3rd party launchers to 'stick' has been a issue on newer releases of FireOS. However, regaining some control over your device does offer the opportunity to fix the problem with Amazon's launcher if it can be identified (eg: missing/renamed file) or rolling back to 3.2.8 and followed by an upgrade to 4.5.2 (there is risk in doing this; make sure you understand the procedure before diving in).
Native TWRP is not an option on 4.5.2. Nor would it help.
You could install Safestrap v4 followed by a patched version of 4.5.2 which should fix the launcher problem. You could continue running FireOS under Safestrap or remove it; the version installed under Safestrap would remain as the default OS. If you keep Safestrap you also have the option of running Nexus v4 or CM11 which offer a more native Android experience and full access to the Google Play store, services and apps.
You should still have nova though. So, you can download cve
Here
, and then have unfettered (well mostly) access.
As far as your other question.
You can run these commands from adb or the app command runner (if you can find it, they took it out of the play store).
There are two ways...
#1 If you do not want to use the stock launcher at all, run this command...
Code:
pm block com.amazon.kindle.otter
To undo, run
Code:
pm unblock com.amazon.kindle.otter
To just make it so the launcher does not work, but the other kindle pieces do (like your library), use this command.
Code:
pm disable com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher
To reverse this, run...
Code:
pm enable com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher
I do not think you even need root for these commands if you run them from adb, but I could be wrong.
Some words of caution. If your device upgrades through ota while otter is blocked (or probably disabled), you will brick your device (unless you have a working recovery/unlocked boot loader and know how to use them to completely restore your system.
If you block otter without a working alternate launcher, you may brick your device, but and could save you by reversing the command.
Good luck.
~Leko
Thank you for all those instructions!
I'll report back how it works for me...
Oh_wow said:
I am in a bootloop that takes me to the "choose language" over and over. I have adb access but am having trouble figuring out which file to download and the commands to get a good file on my HDX 8.9.
I've done a bunch of searching but nothing seems to match what I need. Any help or links would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
Did you install gapps an got
stock on setup
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!