Related
Hey guys,
after some research I found one suggestion that I can't test yet so maybe until my battery runs out one of you can help me:
I unlocked my TF300T ICS 4.0.3 and had CWM running. Probably because of some mistakes of mine it stopped booting at some point and now I can't access recovery, Fastboot, and when I was able to get into CWM, the internal storage didn't work, which is where the NAND backup was stored. Now it only shows the flat white ASUS logo with "device is unlocked" in the corner. When I try to turn it off it automatically reboots.
ADB shell can't find the device so I'm all out of ideas, except that I just read that that once it runs out of battery life the bootloader automatically resets. Maybe that'll help.
Does anybody have any ideas as to how or if I can actually fix this mess?
crstn said:
Hey guys,
after some research I found one suggestion that I can't test yet so maybe until my battery runs out one of you can help me:
I unlocked my TF300T ICS 4.0.3 and had CWM running. Probably because of some mistakes of mine it stopped booting at some point and now I can't access recovery, Fastboot, and when I was able to get into CWM, the internal storage didn't work, which is where the NAND backup was stored. Now it only shows the flat white ASUS logo with "device is unlocked" in the corner. When I try to turn it off it automatically reboots.
ADB shell can't find the device so I'm all out of ideas, except that I just read that that once it runs out of battery life the bootloader automatically resets. Maybe that'll help.
Does anybody have any ideas as to how or if I can actually fix this mess?
Click to expand...
Click to collapse
I let mine discharge all the way, and then I recharged it. I can confirm that it does NOT reset the bootloader.
jrfaulkin said:
I let mine discharge all the way, and then I recharged it. I can confirm that it does NOT reset the bootloader.
Click to expand...
Click to collapse
Ya it didnt work for me either. So is that thing bricked or what? :/
crstn said:
Ya it didnt work for me either. So is that thing bricked or what? :/
Click to expand...
Click to collapse
Well, not totally. We are going to need a whole lot of help though to be able to get bootloader flashed. We can access the device via APX. I think we need the partition table information and the secure bootloader keys (which ASUS has to release to us) in order to use NvFlash to flash the bootloader. Word is that the developers who came up with this procedure for the TF201 are working on this, and have been for a couple of months. Hopefully, a bunch of people bricking their devices all of the sudden will turn up the urgency on this. I'm not holding my breath, but I am keeping my fingers crossed!
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
Count me in on the bricked parade. Except I did mine a while back. I may be missing something but how do you get to APX mode? I just reformatted my computer so I haven't got drivers or ADB set up yet. I probably should try before asking, however I don't ever remember getting into it before.
Sent from my SCH-I535 using Tapatalk 2
enomele said:
Count me in on the bricked parade. Except I did mine a while back. I may be missing something but how do you get to APX mode? I just reformatted my computer so I haven't got drivers or ADB set up yet. I probably should try before asking, however I don't ever remember getting into it before.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You can get in to APX mode by switching it on, holding the volume up button and than use the pinhole reset while keeping the volume up button pressed. If you have it connected to your PC, it will show up. No drivers tho, so it probably won't bring you far.
The problem with waiting for an NVFLASH solution is that we probably need an adapted bootloader to start with for it to work. Since its impossible to make any changes to it without fastboot, I wonder if any solution will become availlable. I will wait another month or so, and then send it to ASUS if no solution is provided here.
I'm sure the costs for repair will be less than the $200 that the nexus costs (and to be true, although the Nexus is a great machine, it's not comparable to the wonderful TF300 )
Sphinix said:
You can get in to APX mode by switching it on, holding the volume up button and than use the pinhole reset while keeping the volume up button pressed. If you have it connected to your PC, it will show up. No drivers tho, so it probably won't bring you far.
The problem with waiting for an NVFLASH solution is that we probably need an adapted bootloader to start with for it to work. Since its impossible to make any changes to it without fastboot, I wonder if any solution will become availlable. I will wait another month or so, and then send it to ASUS if no solution is provided here.
I'm sure the costs for repair will be less than the $200 that the nexus costs (and to be true, although the Nexus is a great machine, it's not comparable to the wonderful TF300 )
Click to expand...
Click to collapse
I was quoted between $87 and $100 to "repair the OS" on my tablet. It's still at the Asus RMA center, so I have no update on what they did with it. I've been posting progress over in this thread : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
Yeah, I saw your posts somewhere else as well... All the best, I've been hearing horror-stories about having to replace the mainboard etc. That would be a bit too much, I imagine :-|
just a quick update:
i sent the transformer back to amazon and they took it back no questions asked.
phew...
Same happened to me, I sent it to Asus about a month ago, they just replayed to me with a mail, saying that is out of warranty because of the bootloader unlocked, and that is gonna cost me $122 for the mainboard, and $65 for labor, it seems that the mainboard got really bad bricked, and they are replacing it....
Really bad for me, but at least I would have it back...
jrfaulkin said:
Well, not totally. We are going to need a whole lot of help though to be able to get bootloader flashed. We can access the device via APX. I think we need the partition table information and the secure bootloader keys (which ASUS has to release to us) in order to use NvFlash to flash the bootloader. Word is that the developers who came up with this procedure for the TF201 are working on this, and have been for a couple of months. Hopefully, a bunch of people bricking their devices all of the sudden will turn up the urgency on this. I'm not holding my breath, but I am keeping my fingers crossed!
Click to expand...
Click to collapse
Unfortunately NVflash will only run on unbricked ICS Bootloader devices. You have to flash some files before you can use the special APX for TF300. So if you are already bricked it will not help.
Sphinix said:
Yeah, I saw your posts somewhere else as well... All the best, I've been hearing horror-stories about having to replace the mainboard etc. That would be a bit too much, I imagine :-|
Click to expand...
Click to collapse
I've just been quoted $122 + $65 + $10 shipping. Which comes out to a shade under $200 total.
End of the line, folks.
I'm not paying Asus $200 to fix a $300 tablet, and I'm basically going to be throwing in the trash at this point if I get it back.
I've unlocked, rooted and ROM'ed probably 100 times on 25 different Android phones and tablets, this looks like my first official TF700 paperweight.
I saw another thread with a couple of people who did the same boneheaded thing I did: tried to install CWM the wrong way. Can't get into the ASUS recovery any more, either I hold volume down and get "Booting into recovery" (then hangs, no adb), or I hold volume up instead and I get a blank screen but it IS recognized as an APX device.
NVFLASH can't do anything at this point, the other thread had no good news either. Why ASUS can't have a "reset to factory recovery and bootloader" option is beyond me. Too late to return to NewEgg.
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20). I have a second TF700 that I unlocked, rooted, and installed CWM the right way. Is there any way using NVFLASH to get the blob from there and putting it on my bricked TF700 or is the blob encrypted to the device? I'm likely out of luck if I try to take the S/N sticker from my second TF700 and put it on the bricked one, ASUS will croak on that most likely.
Are there ANY other options? Short of just opening it up and looking at what's inside? That's a $600 visit I'd like to avoid.
Thanks.
ScaryBob said:
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20).
Click to expand...
Click to collapse
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply.
I used to keep EVERY original box... and yes, I do remember the serial number being there, but the ONE TIME I need the serial number, and all it is is a flimsy sticker on the device itself... And the ONE TIME I don't have the box.
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
It also seems like they would have SOME WAY to just let the end user put back a stock bootloader on the device, then we would all save a lot of time! Other than the fantastic learning experience here, I really want to find a way to salvage this completely useless but fascinating piece of technology.
I wonder if NVidia could help with this... probably not. I guess I'll look.
There must be some way to get a stock bootloader back on my TF700!!!!
Wait a minute man can you boot on Fastboot mode? When you turn on with volume down you can choose the mode to start?
ScaryBob said:
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
Click to expand...
Click to collapse
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
MartyHulskemper said:
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
Click to expand...
Click to collapse
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
ScaryBob said:
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
Click to expand...
Click to collapse
I haven't heard of anyone coming back from where you are. I wish you luck. If you are able to recover somehow on your own, you will be giving this community a great gift by sharing your secret.
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hi:
My tf700t is bricked, no fastboot, only apx after a bad CMW installation, is there any way to restore or re flash using the tools and obvious understanding that you guys have. I really don’t want to send the device back to asus, and will be willing to donate to your site / cause / developers account if you guys could assist me in this matter. Thanks in advance for your time.
jtrosky said:
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I suppose that is an option -- it's not doing me any good as a brick, the worst they can do is send it back.
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
danger-rat said:
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
Click to expand...
Click to collapse
In the OP that was mentioned as well, but with the sidenote he didn't really want to open it up.
Mmmh... fastboot not working is not good... not good at all. I don't see any other option then than sending it back and see what ASUS does with it. As you said, the worst they can do is send it back... No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
MartyHulskemper said:
No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
Click to expand...
Click to collapse
...and charge $380 for it (there was some quote in another thread).
_that said:
...and charge $380 for it (there was some quote in another thread).
Click to expand...
Click to collapse
No, that's if they do absolutely nothing but write a check. (In that thread, at least in my memory, nothing was even actually done on that 700. )
when you guys mean "bad CWM install" what exactly does that mean so we can make sure we can save a few extra souls from doom?
Im pretty sure that is when they install CWM through the Rom Manager app.
mj23kb24 said:
Im pretty sure that is when they install CWM through the Rom Manager app.
Click to expand...
Click to collapse
Yes, since a few days after release (at most), we've known that Rom Manager is not compatible with the TF700. That's why you do not see it in any tutorial. Failure to read before doing leads to bricks in very, very many cases, and the 700's case is no different.
As we've concluded before, in terms of OP relevancy, I guess that sending you expensive baby in anyway would we the way to go (now if you'd only have fastboot available...).
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
WoodenAnts said:
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
You need to provide some more info, are you on Jelly Bean or ICS? When this issue started? More details = higher chances to get help and solve your issue.
Lol sorry, i should know this by know. Was a long day. Uhh yes i was on a JB custom rom When the issue started. The rom had a couple hickups so i wanted to go back to my old one, so i did the nornal, nandroid, titanium backup, etc and flashed new rom. I believe what it did was delete the recovery image that it had, and then attempt to put on a new recovery as some roms do (to much annoyance) but this particular time it failed to install the new recovery for one reason or another. So i had no recovery for a while till i flashed it with fastboot, cwm 6.0.14 i think. So i tried doing a restore before this all happened, and recovery said it successfully restored, but when i reboot, it holds on the asus splash screen. Same with any Roms. And yes I wiped everything as well. Is that enough info?
Sent from my GT-I9300 using xda app-developers app
So I see this seems to be working for Sprint users... Anyone tried this for verizon?
I have a second stock Verizon GS3 sitting here and all the other required bits to try it if someone can give me a little help on how/what to extract from the working phone.
BTW I bricked my stock ROM rooted phone by plugging in a usb flash card adapter I have used in the past. I'm wondering if the paragon ntfs mounter app is partially to blame... SuperSU had recently started giving notifications paragon had been granted SU access ever time the screen was enabled.
Thanks
_sadpanda said:
So I see this seems to be working for Sprint users... Anyone tried this for verizon?
I have a second stock Verizon GS3 sitting here and all the other required bits to try it if someone can give me a little help on how/what to extract from the working phone.
BTW I bricked my stock ROM rooted phone by plugging in a usb flash card adapter I have used in the past. I'm wondering if the paragon ntfs mounter app is partially to blame... SuperSU had recently started giving notifications paragon had been granted SU access ever time the screen was enabled.
Thanks
Click to expand...
Click to collapse
Are you able to boot into recovery or download mode? Doesn't sound like a hard brick.
If you can't then the only way to recover from it is jtag, that method stated in the thread you linked wouldn't work.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Are you able to boot into recovery or download mode? Doesn't sound like a hard brick.
If you can't then the only way to recover from it is jtag, that method stated in the thread you linked wouldn't work.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
its a hard brick. no lights even while charging, no response from buttons or usb jig
I went ahead and cracked it open anyway and sure enough... if a similar solution does exist, we would definitely need another leaked document. boards are completely different.
JTAG it is.
_sadpanda said:
its a hard brick. no lights even while charging, no response from buttons or usb jig
I went ahead and cracked it open anyway and sure enough... if a similar solution does exist, we would definitely need another leaked document. boards are completely different.
JTAG it is.
Click to expand...
Click to collapse
This is the second thread I've seen where a device was bricked by plugging in a peripheral device. This definitely shouldn't happen.
I would call up Samsung and tell them what happened, they might fix your phone or give you a new one for free. This isn't your fault this happened.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
This is the second thread I've seen where a device was bricked by plugging in a peripheral device. This definitely shouldn't happen.
I would call up Samsung and tell them what happened, they might fix your phone or give you a new one for free. This isn't your fault this happened.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Are the situations occurring from the same ROM and/or Kernel?
DubleJayJ said:
Are the situations occurring from the same ROM and/or Kernel?
Click to expand...
Click to collapse
That's a good question, the user in the other post used Cyanogenmod 10.1.
Either way, I don't see how a peripheral device could overwrite a bootloader and hard brick a phone. But it's definitely happened twice.
http://forum.xda-developers.com/showthread.php?t=2374046
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's a good question, the user in the other post used Cyanogenmod 10.1.
Either way, I don't see how a peripheral device could overwrite a bootloader and hard brick a phone. But it's definitely happened twice.
http://forum.xda-developers.com/showthread.php?t=2374046
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I was on no-wipe jelly bean.
Being that its hard bricked is there any reason they would not replace it? (ie no way to tell it was rooted etc) The top right corner of my frame has a dent in it (dropped while removing a difficult clam shell case) but other then that, no wear or damage.
_sadpanda said:
I was on no-wipe jelly bean.
Being that its hard bricked is there any reason they would not replace it? (ie no way to tell it was rooted etc) The top right corner of my frame has a dent in it (dropped while removing a difficult clam shell case) but other then that, no wear or damage.
Click to expand...
Click to collapse
If your phone honestly got bricked by a peripheral device, I'd call Verizon and they will send you a refurbished phone. But if it was your fault I'd pay the 60 bucks and get it jtag. My phone had lots of dents but Verizon still didn't charge me for a replacement but then again I could have gotten lucky
Sent from my SCH-I535 using xda premium
Watoy said:
If your phone honestly got bricked by a peripheral device, I'd call Verizon and they will send you a refurbished phone. But if it was your fault I'd pay the 60 bucks and get it jtag. My phone had lots of dents but Verizon still didn't charge me for a replacement but then again I could have gotten lucky
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
took it to verizon store today. told the guy what I did, he played with it for a few minutes, looked at his screen for a while, checked to make sure there was no obvious damage to the usb port then told me my new phone would be arriving at my home tomorrow. warranty claim through samsung, NOT assurian insurance claim.
That is a lot better then what samsung told me via the live chat... They tried to have me load recovery, then said I would have to mail them the phone (usually 2 days) wait for repair (usually 5 days) then wait for return shipping (usually another two days).
I'm glad it worked out and I didn't have to pay for JTAG. I wonder what rom the replacement will ship with...
I hard bricked my Verizon Samsung Galaxy S3.
I got the thing rooted just fine and I went to install a new ROM. I downloaded EZ unlock to unlock the bootloader and it all went fine. Then I went to restart it and nothing. It won't turn on at all. It doesn't enter recovery mode or download mode. It doesn't light up when it's plugged into the wall charger or laptop. My computer does make the sound when I connect the phone, but nothing shows up. When I open Odin I can get it to recognize the phone if I press the buttons to go into download mode but then it looses the connection as soon as it says added.
I followed this guide http://forum.xda-developers.com/showthread.php?t=2581166 but it didn't work.
I can't believe I did this. I feel like a total fool. You know that sick feeling that sinks into your gut? Yeah, I have it. I need this thing fixed like now but I don't know what to do. Any help would be greatly appreciated.
lgfuad said:
I hard bricked my Verizon Samsung Galaxy S3.
I got the thing rooted just fine and I went to install a new ROM. I downloaded EZ unlock to unlock the bootloader and it all went fine. Then I went to restart it and nothing. It won't turn on at all. It doesn't enter recovery mode or download mode. It doesn't light up when it's plugged into the wall charger or laptop. My computer does make the sound when I connect the phone, but nothing shows up. When I open Odin I can get it to recognize the phone if I press the buttons to go into download mode but then it looses the connection as soon as it says added.
I followed this guide http://forum.xda-developers.com/showthread.php?t=2581166 but it didn't work.
I can't believe I did this. I feel like a total fool. You know that sick feeling that sinks into your gut? Yeah, I have it. I need this thing fixed like now but I don't know what to do. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You can either use the method you posted or get it jtag'd. Those are your only 2 options in this scenario.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You can either use the method you posted or get it jtag'd. Those are your only 2 options in this scenario.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your reply.
I really got myself stuck in the creek.
I was looking up the jtag stuff last night but I'm still confused about it. Is it a program I can download or a usb stick that I have to buy? Can I get it from a store or do I have to purchase one off Ebay?
Thanks again.
lgfuad said:
Thank you for your reply.
I really got myself stuck in the creek.
I was looking up the jtag stuff last night but I'm still confused about it. Is it a program I can download or a usb stick that I have to buy? Can I get it from a store or do I have to purchase one off Ebay?
Thanks again.
Click to expand...
Click to collapse
It's complex, it rewrites your bootloader to your mother board using a riff box. It isn't something easy that you could buy and operate yourself.
You'd send it out to someone. They'd break apart your phone and rewrite the boot image, put it back together, then send it back. Costs anywhere between $20-60.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's complex, it rewrites your bootloader to your mother board using a riff box. It isn't something easy that you could buy and operate yourself.
You'd send it out to someone. They'd break apart your phone and rewrite the boot image, put it back together, then send it back. Costs anywhere between $20-60.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I just want to thank you again for your replies and your patience with my... noobishness.
I swear, I'm never messing around with my phone again. I had my old phone for 4 years and never fooled around with it. I had this one for 2 weeks and destroyed it.
Is there a company you could recommend that I could send it to? I'm in the U.S., Midwest region.
lgfuad said:
I just want to thank you again for your replies and your patience with my... noobishness.
I swear, I'm never messing around with my phone again. I had my old phone for 4 years and never fooled around with it. I had this one for 2 weeks and destroyed it.
Is there a company you could recommend that I could send it to? I'm in the U.S., Midwest region.
Click to expand...
Click to collapse
No problem, glad I could point you in the right direction.
It's not an issue about you messing with your phone. You just have to read more and understand what you're doing before attempting anything. All the information about 4.3 having a locked bootloader and not using ez unlock was readily available. Just next time you decide to root your phone, just read up as much as you can about it before attempting the process.
I really have no recommendations for jtag because I've never had to use it, but I know some eBay sellers can get pretty cheap.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No problem, glad I could point you in the right direction.
It's not an issue about you messing with your phone. You just have to read more and understand what you're doing before attempting anything. All the information about 4.3 having a locked bootloader and not using ez unlock was readily available. Just next time you decide to root your phone, just read up as much as you can about it before attempting the process.
I really have no recommendations for jtag because I've never had to use it, but I know some eBay sellers can get pretty cheap.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
OMG I got it working. I just had to buy a different card.
Yeah, you're completely right. I'm certainly going to read everything before I attempt something like this again.
Thank you again!
Before the hate police flood my new thread - yes I have searched xda for the answer(s) - but haven't had any luck. I've searched for 2 weeks before writing this.
I did a stupid thing. My device is unlocked and rooted but still had the Asus OS and i tried to change the fonts. Now it won't get past the ASUS boot screen. I also don't get the 3 (or 4 or 5) icons that are supposed to come up.
I've tried the power/volume buttons, motochopper, the Asus unlock (probably unnecessary) and a number of other things my searches but no luck.
I'm trying to find a step-by-step guide that can possibly help me with my particular problem.
After I completely get it going again I am going to install Cyanogen or KKrombi or some other OS.
This is a process that I am famliar with and have been doing since my T-Mobile G1 to my OPO without problem, but this time I am stumped.
Thank you for your time and help. Just point me to another thread or something & I'll take it from there.
How did you try to change the fonts??
Never heard before that somebody hard bricked the tablet that way and that's what you did it seems. Hate to tell you this, but if you cannot get into the bootloader (screen with 3 icons) this tablet is toast.
berndblb said:
How did you try to change the fonts??
Never heard before that somebody hard bricked the tablet that way and that's what you did it seems. Hate to tell you this, but if you cannot get into the bootloader (screen with 3 icons) this tablet is toast.
Click to expand...
Click to collapse
Bugger. I used Rom Manager to do it. It's funny I saw the icons once but not since.
Yeah bricked sounds right.
dnmoscato said:
Bugger. I used Rom Manager to do it. It's funny I saw the icons once but not since.
Yeah bricked sounds right.
Click to expand...
Click to collapse
Yep, using ROM Manager has bricked quite a few of these babies. That explains it. Sorry man....
I know you mentioned using various tools already, but have you tried fastboot commands with it connected directly to your computer?
Sent from my Nexus 6 using Tapatalk
It's something that I've tried but never been able to do it correctly - well not since my G1 - and that was step-by-step from Cyanogenmod pre-Inc.
Didn't see bernblb's second reply. If he says it is bricked, then it most likely is. I haven't toiled around on my TF700 for a long time now.
Sent from my Nexus 6 using Tapatalk
Yeah it probably is. My own fault. Trouble is it really suited my wants and needs. Guess it's back to Swappa.