Before I explain my problem, let me first say that I am a novice when it comes to modifying phones. Shortly after buying my Razr, I knew that I wanted to root my phone, but I didn't know how. I found a program (that I can't recall now) rooted it, and had no problems. My problem came when I wanted to accept the OTA upgrade. I tried using Voodoo to keep my root while I accepted the OTA update, but that's where things when wrong. I don't know everything that went wrong because it seemed like nothing that I was doing was having any effect. It was having an effect, but not the effect that I wanted. After some uneducated decisions on my part, I found my Razr stuck in a bootloop. After trying to "fix" things, I gave up on it, but I decided to hold onto the phone. I replaced it with an HTC Rezound and moved on. I chose the Rezound only because it wouldn't take long to get it and it was affordable.
Last week, I decided that using the Rezound (it's definitely not all bad) has made me want to revive the Razr. I ordered BlackHat's adapter and used MattLGroff's utility (http://forum.xda-developers.com/showthread.php?t=2192467) to wipe my phone and flash JB.
This worked, with two exceptions. First, the phone still wouldn't charge. I came across a forum post that talked about successfully charging a phone in the car when it wouldn't charge inside with a computer or wall outlet. I was skeptical, but it worked. After charging the phone in the car, I can now charge it inside with a computer or wall outlet.
The second problem remains, and I am wondering if something that I did to soft-brick the phone caused a hardware problem. That seems unlikely, but I am new to this, so anything's possible as far as I'm concerned. In the attached picture, you can see that the bottom third of the screen shows up almost like static on a TV, but it's broken down into a grid. Also, the right half of the screen shifts up almost the height of the screen. Both of these problems come and go, but the "static" at the bottom of the screen comes much more often. I have to navigate through folders and menus before the shifting problem happens. Regardless, if I am at the home screen, for example, and I shift right or left (or navigate anywhere for that matter), the screen will be clean with no errors for a moment. After a second or so, the glitches usually show up.
I almost forgot about the last issue. When I wake the screen, it's quick and responsive; however, when I turn off the screen (by tapping on the power button), there is a lot of lag in the animation. Normally it would be a quick and smooth transition to the thin, horizontal line, and then it would quickly disappear. Now I can watch as it slowly blurs and stretches. It works, but it lags. This happens every time I turn off the screen.
Does anyone know what could cause this? Am I beyond repair? After typing this out, I doubt that it's a hardware problem, mainly because the static and shifting are not constant. But again, I'm totally new to this.
If anyone has any suggestions that involve utilities, then it would be ideal if I can use Linux. I have access to a Windows computer, but not at home.
Thanks in advance to anyone who can offer some insight.
Does anyone have any insight into this? Two months later and I'm still stumped. It doesn't matter how I use MattLGroff's utility...the same issues are still present. Could I maybe use a utility that will revert me to an older system? That way, I might be able to receive an OTA upgrade to JB.
I'm grateful for ANY input...
Thanks!
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
AztekSoul said:
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
neffje said:
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
Click to expand...
Click to collapse
hi,i had the same bug with rds lite didn't show me the spec of the phone,but only --------.
try anyway and remember to have the motorola driver in the pc (i don't know if works with wine,i had try only i my other windows pc)
Related
So I have a bad feeling here. I was fixing my ad hoc problem and accidentally renamed my /system/bin folder to "bin - Copy" not sure how I did it, a finger swype n boom it was that way. Could not change it back. Rebooted and now I can't get passed the Eee Pad boot screen. Any one know how to fix this?
I've got a similar problem.
There should be a sollution where you start up, holding the powerbutton and volume up. You feel a vibrate and the screen stays black.
with this way you can connect your transformer, and access it. But I don't know how.
Windows reconiges the device as and APX (under linux as an Nvidia device) But I can't connect to it, don't have the drivers and so.
So is anyone knows how to access the prime trough this method, our problem could be solved using adb pulling and pushing these folders.
Greets
If you connect it to your computer can adb access it??
Nope. Going to try a couple more things this evening.
Sent from my PC36100 using XDA App
Well, I tried a bunch of different things: microsd recovery, wipe data, recovery, "up volume/pwr button", broke down n called Asus. So here's what happened in case anyone else comes across this thread: microsd method to flash firmware=nothing, anytime I entered recovery Andy laid down and opened his chest cavity and red triangle !, wipe data done. signature match=freeze up at that screen, no reboot. hard reset with paper clip=nada just reset to frozen eee pad screen. I have linux 11.10 and 10.04BT on another hdd so I booted to both b/c I read a post somewhere about booting the prime by holding up volume/pwr and its supposed to be some kind of nvidia diagnostic mode. Interestingly in windows it changed from an unknown MTP usb to APX device doing this, in Linux it never even came up either way. I don't know enough about this, so I tried searching and reading=nothing fruitful. I'm a Linux and ADB noob so I read and read and read some more, but after trying a few walk throughs, my Prime just seems to be dead. So I called Asus and played dumb, said it froze after trying to update to ICS. He walked me through these other steps I mentioned to no avail. Then he gave me an RMA# so I went ahead and mentioned the excessive light bleed and non-functioning GPS. He noted those issues and now I'm sending it in apparently. I was REALLY hoping to avoid this b/c this was my fault, but my experience with the Prime has prompted me to ad my 2 cents/rant in the general thread.
I wish this had a better outcome, but with the bootloader locked I and many others have been unnecessarily doomed to RMA.
Well that sucks big time... hope you get another soon
hoping to hear about an update to this other than sending it in. unfortunatley i have just done the exact same thing.
There are APX drivers in the dev section. My Prime changed from APX device to Asus Transformer prime APX mode when I installed them. After that I don't know what to do; I think we need an nvflash for the Prime or something.
Mine went into APX mode after the last OTA update failed and won't leave APX mode for anything, so I was looking for a way to connect to it to flash an update or something, but no luck so far. Maybe Asus will release a tool for us to fix a failed OTA update, would be a lot better than sending my tablet away for a month so they can do it.
I searched and searched for this too. Couldn't get anything to work.
As for an update, as of about a couple hours ago, looks like they are sending me a new tablet. Has a different serial number listed as "ready to ship" and states "original serial number: C1O....." which is the s/n of the tab I sent in.
So we'll see if this one comes with no light bleed and working gps. Don't think I'll be screwing this one up! Gonna be extra careful...
I was in the same situation, stuck. I tried everything you did as well and nothing. "Doktaphex" gave me this link http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119 in my post and it worked perfectly. I was sooo damn happy to see Andy actually working instead of laying down when I entered RCK
Oops...shoulda read through. Hehe sorry bout that :/
That would've been just one more thing to try on top of all the other things I tried. If it actually works, then ALL the other ppl that say to use this microsd recovery method need to read your link and actually know what they are talking about. I read method after method and tried them all to no avail.
I did this and that worked for me : http://forum.xda-developers.com/showpost.php?p=22857274&postcount=21
Got my replacement Prime today. Putting it through the paces now. GPS isn't noted on the box, but I don't remember if it was on my first one. Still a C1O serial. Went ahead and updated first, bc I don't care about HC.
GPS: Can see 4 but signal stays under 35, no locks. will try again tom from Dallas
BT/Wifi issue: None, Does not degrade
Wifi range: Not bad, little better than my phone
Light bleed: Better than last, but still 5 spots along bottom and right side
Side Note: put a 64gb microsd in the tab and a 64gb microsd w adapter in dock. Both work fine, now up to 192gb.
I'm very happy Asus replaced this so quick (week and 1 day). I'm not a picky person so I am fine w the lesser light bleed, I will never use gps but it would be nice to have as an option. I bricked my first tab and would gladly have paid for them to reflash it, heck if they called me even now and said, "hey, we found that you bricked your own tab, here's a bill to reflash" I'd gladly pay it. So far I have to agree w everybody's sides to every issue, which is crazy to think, but everyone has legitimate points. Except ppl that expect Asus to still warrant after unlocking n flashing roms, that's ridiculous.
Alright So I bought this Atrix for 50 bucks. Guy was having problems and coulnt figure it out. Its rooted and unlocked. When I plug the charger into it (the stock wall charger. not to the computer) it goes to the M boot screen. I can't get to any other screen to come up. When I hold the volume buttons down, I get "Cant start RSD Battery too low to flash". also, When I plug it in, The green LED lights up for a second then turns off as it goes to the Motorola screen. I can't turn it on either with just the battery. any Ideas?
crazydavy said:
Alright So I bought this Atrix for 50 bucks. Guy was having problems and coulnt figure it out. Its rooted and unlocked. When I plug the charger into it (the stock wall charger. not to the computer) it goes to the M boot screen. I can't get to any other screen to come up. When I hold the volume buttons down, I get "Cant start RSD Battery too low to flash". also, When I plug it in, The green LED lights up for a second then turns off as it goes to the Motorola screen. I can't turn it on either with just the battery. any Ideas?
Click to expand...
Click to collapse
I had this problem just last night. I searched around xda and the internet, and came upon this: http://www.atrixforums.com/forum/mo...e-rsd-lite-flash-sbf-file-motorola-atrix.html
Give it a shot. If it doesn't turn on now, what's the worse that'll happen by trying this?
Just charge the battery and flash a SBF with RSDLite.
Make sure that you don't downgrade the ROM. Read sticky for more info about hardbricking risks.
Wrong section.
Sent from my MB860 using Tapatalk 2
What SBF file do I need? Im not sure what is on the phone and I dont wanna Brick it if I can avoid it.
Go the latest SBF(the latest being 2.3.6/4.5.141 if you have an ATT atrix. Otherwise a full list of SBF files are here http://www.filefactory.com/f/89f588286a560e39/ ). Bricking occured when downgrading, so long as you upgrade or stay the same you should be fine.
rkkaranrk said:
Wrong section.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, admin?
I bit the bullet and did it. All was going good till my cat jumped on my computer desk and then failed saying something about switching to BP or something along those lines. Now I cant get the phone is RSD again
Was your battery charged enough? Sometimes if your battery is low it won't complete the flash.
What directory is your sbf file located at? Sometimes it won't work unless you put it directly in the C:\ drive.
Have you got the latest RSDlite?
What SBF did you flash?
Did you use the usb ports at the back of the pc?
If you can't get it in RSD again then I suggest giving it a charge for an hour or so and trying again later. Also check the md5 of the sbf file to check that the file is correct. Sometimes the 'Switch phone to BP Pass through mode' can be fixed just from trying a different usb port or computer.
crazydavy said:
I bit the bullet and did it. All was going good till my cat jumped on my computer desk and then failed saying something about switching to BP or something along those lines. Now I cant get the phone is RSD again
Click to expand...
Click to collapse
congratulations your mobile device is sucessfully bricked.
mine did[(do)will] the same, you have to take it to the assistance, i know what must be done, the assistance guys told me, but it can only be done by them.
so, you better hope you dont have the same problem as mine. [but if you got the error talking about didnt booting radio////failed to switch to BP(or some s**t like that) you probably have it, and only motorola can fix it.]
Edit: we know is the wrong section but only modetators can complain/report/warn. if we are not, lets just help the poor dude while the problem is unsolved.
guidoido004 said:
congratulations your mobile device is sucessfully bricked.
mine did[(do)will] the same, you have to take it to the assistance, i know what must be done, the assistance guys told me, but it can only be done by them.
so, you better hope you dont have the same problem as mine. [but if you got the error talking about didnt booting radio////failed to switch to BP(or some s**t like that) you probably have it, and only motorola can fix it.]
Edit: we know is the wrong section but only modetators can complain/report/warn. if we are not, lets just help the poor dude while the problem is unsolved.
Click to expand...
Click to collapse
Have you googled the error? If you have, you'd find that it is a common error and I haven't seen any cases where they didn't eventually get fixed. OP just needs to get back in to RSD and have another go. The guys from 'assistance' don't know what they're doing, they'll take any reason to say that 'only motorola can fix it' because they don't know any better.
devize said:
Have you googled the error? If you have, you'd find that it is a common error and I haven't seen any cases where they didn't eventually get fixed. OP just needs to get back in to RSD and have another go. The guys from 'assistance' don't know what they're doing, they'll take any reason to say that 'only motorola can fix it' because they don't know any better.
Click to expand...
Click to collapse
I wold haVE GOOGLED IT BUT RSD lite closed on me. I would get back into RSD but I can't get the phone back into it. I power on and hold the volume buttons and it doesnt do anything.
And also now while its stuck on the Motorola boot screen, Unlocked is missing from the corner like it use to be there.
Well after just fidiling around with it, it just started working. After about 45 minutes of just sitting there on the motorola screen, it booted up. Now its time to set it up all the way and put CM7 on it im guess.
I wasn't talking to you about googling the error, I was talking to the guy who had said that your phone was bricked when clearly it wasn't. The error would have been a fail at 'Switching Device to BP Pass Through' stage which does not mean you're device is bricked.
Anyway, good to see you fixed it. And the unlocked text goes away when you flash an SBF, that's normal. Get cm10 on it
I went back through and kind of got that after the fact haha. Im glad I got it fixed also too. Not I can get rid of the dreaded Iphone 4 :\ and be back where I belong. Is there a stable CM10 for it? I havent gotten to look around much yet since I was fixing the main problem.
All,
I have to say thanks for the help in advance, well I'm in the military and I have never done anything to my G-tablet. All I used it for was to OOVOO and talk with my kids when I am in the DESERT Guys over there are always doing crazy stuff to theirs and crazy stuff always happens to them, some good some bad. :cyclops: Well here it goes my brother-in-law took my tablet without my knowledge and decided he would upgrade me to a better system :crying::crying::crying::crying: well he killed it!!!!!!! and I leave to go back to the desert in a week or so. He says something must of been wrong with it before he touched it, yeah likely story!!! it worked fine when I used it last. I have to say I have little knowledge on how to do things to this tablet IE rooting roms and all of that stuff, not saying I'm not willing to learn just very dumb when it comes to doing it. I'm one of those give it to me step by step by step
So this is what I have done so far
1. I plug it in to my Computer Windows Vista Home premium 64 bit system and it does not recognize it.
2. I opened it up and have disconnected the internal battery cord and plugged it back in still no life
3. I pressed the little white button and no reset happened
4. Held down the power button and down sound button and (3 birds ViewSonic - Detect a recovery key pressed - Booting recovery kernel image) popped up then nothing it just sits like that.
5. I have also let the battery completely drain to zero then charge it back up and still nothing.
Please help me and I'm sorry if I've been rambling on but talking to my kids when I'm deployed is the only thing I look forward to doing when I'm in the desert, Once again I would like to thank the smart guys on this forum for helping us not sooooo smart ones with our problems.
desert G-TABLET said:
All,
I have to say thanks for the help in advance, well I'm in the military and I have never done anything to my G-tablet. All I used it for was to OOVOO and talk with my kids when I am in the DESERT Guys over there are always doing crazy stuff to theirs and crazy stuff always happens to them, some good some bad. :cyclops: Well here it goes my brother-in-law took my tablet without my knowledge and decided he would upgrade me to a better system :crying::crying::crying::crying: well he killed it!!!!!!! and I leave to go back to the desert in a week or so. He says something must of been wrong with it before he touched it, yeah likely story!!! it worked fine when I used it last. I have to say I have little knowledge on how to do things to this tablet IE rooting roms and all of that stuff, not saying I'm not willing to learn just very dumb when it comes to doing it. I'm one of those give it to me step by step by step
So this is what I have done so far
1. I plug it in to my Computer Windows Vista Home premium 64 bit system and it does not recognize it.
2. I opened it up and have disconnected the internal battery cord and plugged it back in still no life
3. I pressed the little white button and no reset happened
4. Held down the power button and down sound button and (3 birds ViewSonic - Detect a recovery key pressed - Booting recovery kernel image) popped up then nothing it just sits like that.
5. I have also let the battery completely drain to zero then charge it back up and still nothing.
Please help me and I'm sorry if I've been rambling on but talking to my kids when I'm deployed is the only thing I look forward to doing when I'm in the desert, Once again I would like to thank the smart guys on this forum for helping us not sooooo smart ones with our problems.
Click to expand...
Click to collapse
1.- Try other windows version, works fine on Windows 7 x32 / x64 - tested my self
3.- wich white reset button? i never saw it !
4.- You tried POWER+VOLUME (+)? - POWER+VOLUME(-)?(this its for nvflash as far i know, im also a begginer)
Your tab is not dead, but it is not properly flashed either. If you hold power and Vol UP and it shows booting recovery but doesnt boot it, then there is a bad recovery flashed, or none at all. To fix this, you will have to NVFLASH a recovery/OS on it. There are better than stock OS's but since you need it for webchating with family I would suggest Frankentab.
Download this file:
http://teamdrh.com/DRH-Downloads/Full_Stock_NVFlash_CWM_5504_Touch.zip
Then extract it somewhere you can find it.
Using a usb Male to usb mini cable, the one that came with your tablet, plug your tab into your computer (tab turned off)
Hold down the VOL DOWN button and press power button and hold it too. The three birds should pop up, then go away, black screen.
After black screen, computer will say found new hardware. You must manually choose the drivers needed, and their location will be in a folder titled "flash usb drivers" and it is inside the folder you downloaded and extracted.
After the drivers are installed, without turning anything off, run the file nvflash_gtablet.bat which is inside the extracted folder you downloaded. This will take a while, but once it is done, you can turn off and turn back on your tablet. After a few minutes, it should completely boot back into a stock ROM.
If you are cool with this, then you are done. If you would like to run something MUCH FASTER then let me know when you get to this point and I will show you how to accomplish this. If you run into any problems report back and I or someone will help.
Just had this problem on a new (well refurbished) gTab I got during black Friday. Works great and is not hard to fix the issue once in APX. hardest part was getting the drivers installed (running win 7 x64).
I had to go to the CWM page to download the correct version of the recovery, the version listed in the guide is outdated, or not listed that it is for 1.1 only and not 1.2.
Seems like a great tablet, can't wait to get using it. Thanks!
camman85 said:
Just had this problem on a new (well refurbished) gTab I got during black Friday. Works great and is not hard to fix the issue once in APX. hardest part was getting the drivers installed (running win 7 x64).
I had to go to the CWM page to download the correct version of the recovery, the version listed in the guide is outdated, or not listed that it is for 1.1 only and not 1.2.
Seems like a great tablet, can't wait to get using it. Thanks!
Click to expand...
Click to collapse
do you remember where you downloaded the right recovery version for windows 7 ?
I'm trying to root my Unlocked T-Mobile G1 via Kingroot. I followed the procedure step by step. (I mean, c'mon, how hard is it to use this program, really?) Obviously I'm very new to most of this, but I have done my research on Rooting! I know the Pro's and Con's, I know there are multiple ways to do this ( Some requiring a bit of know-how with the computer language) and I figure this way is the easiest ((for me)).
Here is my issue.
I downloaded all the drivers. I turned on Android USB Debugging. I've mounted the SD card. I plugged it all in, and got the page with the lovely, red "ROOT" button. I pushed it. I pulls the scripts, it checks the connection, it begins the process. My device goes black very briefly then appears all of these lovely colors (Red, Orange, Yellow, Blue, Green, White) It displays the model number, manufacturer date, phone model, phone company it was sold to, etc. And it sits. The program reads "Waiting for Device." for about 2 or 3 minutes, then it says "Root Unsuccessful! WaitForDeviceTimeOut!" I checked and re-checked the list of compatible devices, and mine is on there. (Though it is called an HTC DREAM instead of T-Mobile G1 but I doubt that truly matters.) I then disconnect the phone, pull the battery, turn it back on, it's fine. I've tried this several times to no avail. I'm not using the original USB cord, but my computer and the program reads it, It stays connected. It charges.
Am I missing a step?? Doing something wrong?? Is there another, newbie proof way I can root this phone?? I figured this was the simplest, without having to manually hack into my phone and type commands into it. I've googled and googled and googled this problem, with no result. Kingoroot seems to be rather new, and though I messaged the support team, I've yet to hear anything back.
Any suggestions would be helpful. Sorry if this is a stupid post.
Thank you!
Rooting the g1 by the "old" method is very simple and I'd be happy to walk you through it, but feel free to use any of the one click apps, most of those came about after I learned things on my own and since that time I've always been against do-it-for-me-tools of any kind as there is no knowledge to be gained
Let me know if you need a hand with the old school way otherwise search out one of the many other one-click-root options for the dream (same thing as g1)
Sent from my Nexus 4 using Tapatalk 2
Hi everyone, so I have a 1GB/8GB Omate Truesmart that has been awesome. After having the Imperium Operative ROM on it and realizing the sensors were not working, I decided to try and revert back to the stock firmware. However, that's where the trouble started. My cradle wasn't working properly during the process and stopped in the middle of it, and now I can't even boot my watch on (unless there's some alternative way). On top of that, anytime I try to connect it to any of my USB ports, it keeps saying on my Windows 7 laptop that the USB device is not recognized, and I tried uninstalling and reinstalling the drivers again.
So, if anyone can please help me and guide me in "unbricking" the watch and just being able to have my laptop recognize it so I can actually do the stock firmware process, I'd be really grateful. Thanks a lot!
You used Sp flash tool correct? I'd suggest reading the unbricking guide first but answer these first:
What color was the progress bar when it stopped?
Have you tried a different port?
Have you pulled the battery yet?
Sent from my GT-P5110 using Tapatalk 2
Actually fixed it!
kuronosan said:
You used Sp flash tool correct? I'd suggest reading the unbricking guide first but answer these first:
What color was the progress bar when it stopped?
Have you tried a different port?
Have you pulled the battery yet?
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
Hey kurunosan, so I did follow the unbricking guide exactly, but because my cradle is a little bit finicky (the microUSB has to be plugged into it in an exact position for it to be read by the laptop), it had messed up during the unbricking process and therefore, caused it to be "bricked". To answer your questions though, the color of the progress bar was yellow, I tried all the different ports around my laptop, as well as my work laptop. And I wasn't able to pull the battery because I haven't been able to unscrew the back yet (I blame those crazy small screws lol).
BUT, I was finally able to fix the drivers issue and my watch was recognized by my laptop finally. If I have time later in the next day or two, I'll try and make a guide about it if something like that happens to anyone. Or if anyone is curious or has had it happen to them, you can feel free to PM me.
I'm just glad that my TrueSmart is finally functional again!
shadowninja23 said:
Hey kurunosan, so I did follow the unbricking guide exactly, but because my cradle is a little bit finicky (the microUSB has to be plugged into it in an exact position for it to be read by the laptop), it had messed up during the unbricking process and therefore, caused it to be "bricked". To answer your questions though, the color of the progress bar was yellow, I tried all the different ports around my laptop, as well as my work laptop. And I wasn't able to pull the battery because I haven't been able to unscrew the back yet (I blame those crazy small screws lol).
BUT, I was finally able to fix the drivers issue and my watch was recognized by my laptop finally. If I have time later in the next day or two, I'll try and make a guide about it if something like that happens to anyone. Or if anyone is curious or has had it happen to them, you can feel free to PM me.
I'm just glad that my TrueSmart is finally functional again!
Click to expand...
Click to collapse
The good news for you is that because it was only yellow, your watch was just stuck in preloader mode and you hadn't fully bricked it.
If you disconnected it while the progress bar was purple, you'd be in some serious trouble.
I'm very familiar with preloader and it's such a pain in the ass when the drivers do gymnastics and switch ports or flat out don't work.
Preloader
kuronosan said:
The good news for you is that because it was only yellow, your watch was just stuck in preloader mode and you hadn't fully bricked it.
If you disconnected it while the progress bar was purple, you'd be in some serious trouble.
I'm very familiar with preloader and it's such a pain in the ass when the drivers do gymnastics and switch ports or flat out don't work.
Click to expand...
Click to collapse
Oh gotcha, did not know that about the preloader. Well, good thing that was the only case then!
I have had a similar experience with my Truesmart. I originally tried to apply Lokifish's Root + Enhanced Security patch. This unfortunately failed for some reason and resulted in me not having root or any USB functionaility.
So I went through the process of putting the watch back to stock. I followed the process to the letter, but something went wrong during the process and it ended up with SPTools giving up (looking at the logs it looks like it lost USB connectivity - attached). Now the watch seems to be bricked. I have attempted the process again but SPTools is not detecting anything.
Any help or advice would be very much appreciated....I am a very sad bunny at the moment :crying:
I would prefer to not have to remove the battery (for obvious reasons), but will do if there is no other way round it.
Beta_Tester666 said:
I have had a similar experience with my Truesmart. I originally tried to apply Lokifish's Root + Enhanced Security patch. This unfortunately failed for some reason and resulted in me not having root or any USB functionaility.
So I went through the process of putting the watch back to stock. I followed the process to the letter, but something went wrong during the process and it ended up with SPTools giving up (looking at the logs it looks like it lost USB connectivity - attached). Now the watch seems to be bricked. I have attempted the process again but SPTools is not detecting anything.
Any help or advice would be very much appreciated....I am a very sad bunny at the moment :crying:
I would prefer to not have to remove the battery (for obvious reasons), but will do if there is no other way round it.
Click to expand...
Click to collapse
The patch will tell you if there's an error. It will show the command with the word "failed".
Regarding SPTools attempt to return to stock. In looking at the log it was continuously connecting and disconnecting which usually demotes either a driver,dock or USB issue. It is most likely in a bootloader mode but locked up. I suggest you leave the TS alone for a few hours or possibly overnight and attempt to flash it again.
Unfortunately you have given my very little to go on so other than general fixes there's not much I can tell you. In the future if you run into any issues flashing anything or running scripts it is best to post in that projects support thread and wait for help.
The log clearly shows multiple disconnects, probably because of a bad query. I suggest the same thing Loki did.
Sent from my Galaxy Nexus using Tapatalk 2