Related
OK, it goes without saying that to do rooting and flashing you need to have at least a basic understanding of the English language, a decent IQ and the ability to follow basic instructions.
However, with the CWM mod that's out there for this phone, there are dangers in trying to use for anything other than flashing. IMO, the problem is that those discussions are getting buried in long threads that were originally meant for other Subjects. I feel that CWM needs to have a thread of its on to benefit EVERYONE, especially the newbies. So I am starting it off with this simple instruction:
DO NOT TRY TO USE A ROM MANAGER AT THIS TIME! THE DEVS WILL LET YOU KNOW WHEN YOU CAN USE IT
ALSO; DO NOT USE CWM TO RESTORE AT THIS TIME YOU WILL BE BRICKED
#2 IF YOU WANT TO GET INTO CWM FROM START-UP TO FLASH A ROM - HOLD DOWN THE VOL UP BUTTON + HOME BUTTON + POWER BUTTON, WHEN YOU SEE THE SAMSUNG LOGO, RELEASE THE POWER BUTTON.
TO END THE CONSTANT QUESTIONS ABOUT THE "GO BACK" MENU OPTION: SCROLL COMPLETELY THROUGH ALL MENU OPTIONS TWICE, THE GO BACK OPEN WILL THEN APPEAR
I ask the devs to post info. here even if it has been posted in one of the threads.
Forum Management FTW!
If one of the devs could throw up the file to flash CWM and the instructions, that might be helfpful as well.
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
kejar31 said:
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
Click to expand...
Click to collapse
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
hoppermi said:
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
Click to expand...
Click to collapse
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
kejar31 said:
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
Click to expand...
Click to collapse
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
I have found pressing the vol up and vol down at the same time enables the "go back" option. It will state that it is enabled.
It will pop up when you select another option first.
Sent from my voodoo Droid Charge ED2
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
And ShotgunSam you might as well add don't restore w/ CWM in your big red warning.
boostedjti said:
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
Click to expand...
Click to collapse
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
I have one that was bricked for this reason. If anyone has any ideas I will test them out. I am good with adb shell and have been trying to figure out how to change the bootmode=7 which I think is the sdcard to 6 which I think is the nand. Can't find where the file is in the system because I can't boot. Or a signed update zip that boots Android of the sdcard like the hd2 might work.
stranula said:
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
Click to expand...
Click to collapse
Go to the epic 4g forums and in development you'll find a thread that contains an update.zip that will use cwm 3.0.2.x. adb push that update to your sd card or just transfer it. Flash jts cwm compatible kernel through odin then try applying the update.zip.
Just a theory. If cwm boots, you can then flash a rom and that may work.
hoppermi said:
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
Click to expand...
Click to collapse
That was something I mentioned on irc the other day lol great minds think alike.
Has anyone with bricked phones tried to reach out to Koush?
Sent from my ADR6400L using Tapatalk
kejar31 said:
Has anyone with bricked phones tried to reach out to Koush?
Click to expand...
Click to collapse
Koush has been worse than useless for the Galaxy S.
Well he does have the Charge listed as a supported device on his website.. if its bricking he might help.. so if my phone were bricked I would at least try and start with him
Sent from my ADR6400L using Tapatalk
I tweeted at him and said the problem. No response yet. Ill keep posted. Everyone should tell him
Sent from my SCH-I510 using XDA Premium App
Koush is looking into it.
Sent from my SCH-I510 using XDA Premium App
Thanks OP for this tread. I agree 100%.
1) I think some "bootloopers" have had success entering download mode when their SD card was pulled.
2) Have any brickers/bootloopers tried the JIG method to force download mode?
Google JIG:
http://forum.xda-developers.com/showthread.php?t=819551
http://www.youtube.com/watch?v=iSaeaAcJHqw
http://www.youtube.com/watch?v=GjDkShT-65Y
http://samsungjigs.blogspot.com/
http://shop.ebay.com/skisky1/m.html
3) Also, I *think* someone who had bootloops was able to clear his data/cache folder somehow/someway. And I *think* he was either able to stop the bootloops or at least get into download mode. But maybe I am thinking of something else here.
Would empty cache/dbdata/movinand.bin files be helpful for Odin? We could rip them out of one of the Fascinate Odin packages to be included with a "Restore to stock" Odin package. Based on the error I've seen of someone that tried to restore, it looks like /data is getting FUBARd and that's causing the problem, but it's not something I want to personally test since my phone is working.
Anyone having issues after a restore, please see if you have adb shell access. If so, please grab a logcat and post it here.
Sent from my SCH-I500 using XDA App
so the phone works fine but i cannot charge with it off as regardless or rom while it is off if i plug the charger in it boots into recovery mode. IF my battery was to completely drain i would'nt be able to charge it with out a standalone battery charger
due to this fact i'm looking for solutions to the actual problem not someone to say don't let it die. it probably never will as i would just switch it off but still i'd like to be able to turn my phone off and charge it if i wanted to
Has anyone else experienced this or heard about this and have actual useful info, i don't need to be told flash a new rom etc i'm always flashing roms. It's not an urgent issue i'd just like to know seeing as i seem to be one of the only people experiencing this
I think you have an old recovery that doesn't allow charging.
Update to latest 4EXT.
Jack_R1 said:
I think you have an old recovery that doesn't allow charging.
Update to latest 4EXT.
Click to expand...
Click to collapse
thanks looking into this now, when i install the 4ext recovery updater is that going to replace CWM or Rom manager premium :S
dw i found the answer *EDIT*
switching to 4ext solved it thanks again !
So this is a recovery problem? I also have this but I don't wanna change recovery.
Sent from my HTC Desire S
MarlX said:
So this is a recovery problem? I also have this but I don't wanna change recovery.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Then you stay with your problem.
Yes, obviously it's a recovery problem. Recovery that supports charging was done starting CWM 5.0.0.6 (hack) and 5.0.0.8 or so (official). The latest CWM should support charging too. Personally, I fail to see even one smallest reason not to upgrade recovery.
MarlX said:
So this is a recovery problem? I also have this but I don't wanna change recovery.
Sent from my HTC Desire S
Click to expand...
Click to collapse
i had the latest cwm touch and couldn't charge, 4ext is alot better though, the free version has nearly every rom manager premium feature i'd switch if i was you, well i did switch lol
Okay, thanks. I'm not changing ROM often so I guess I can stay with CWM. The only prob that I have is that it boot to recovery while charging (when off) but I also doesn't shut down my phone when charging, so it doesn't matter that much.
GGLDN said:
i had the latest cwm touch and couldn't charge, 4ext is alot better though, the free version has nearly every rom manager premium feature i'd switch if i was you, well i did switch lol
Click to expand...
Click to collapse
Jack_R1 said:
Then you stay with your problem.
Yes, obviously it's a recovery problem. Recovery that supports charging was done starting CWM 5.0.0.6 (hack) and 5.0.0.8 or so (official). The latest CWM should support charging too. Personally, I fail to see even one smallest reason not to upgrade recovery.
Click to expand...
Click to collapse
Sent from my HTC Desire S
You would certainly see multiple benefits from upgrading to 4 ext recovery, especially writhe touch version....even the free version although would recommend that you buy the paid version to support the quality developer
Swyped from my DesireS
I updated to knew baseband and i lost my recovery to flash roms what to do know?
Capt. Martin#30 said:
I updated to knew baseband and i lost my recovery to flash roms what to do know?
Click to expand...
Click to collapse
That's correct.........it has been said many times that you need to re-flash the CWM to be able to flash/restore
idbl_fanatic said:
That's correct.........it has been said many times that you need to re-flash the CWM to be able to flash/restore
Click to expand...
Click to collapse
How do i get it back now?
Capt. Martin#30 said:
How do i get it back now?
Click to expand...
Click to collapse
With NV-Flash. Just do the exact same thing you did the first time before the updating to newer baseband to get recovery.
Hope this helped!
Sent from my LG-P999 using XDA
Try these
These will get Clockwork mod and Root back. Of course if you use Bluetooth for calls you may be up the creek without a paddle for calls until the developers can nail down whats up. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1056847 -[RECOVERY][APP] 4-28:One-Click NvFlasher ClockWorkMod Touch 5.8.1.3/5.0.2.0/4.0.1.5
http://forum.xda-developers.com/showthread.php?t=1039985 -[ROOT] G2x Root via SuperOneClick
Whyzor said:
Bluetooth not working during calls is a confirmed problem with recent CM7 builds. Star this issue so it gets more attention, no guarantee it'll be fixed though.
http://code.google.com/p/cyanogenmod/issues/detail?id=5349
Click to expand...
Click to collapse
Link to thread here: http://forum.xda-developers.com/showthread.php?p=27414835
Try and get as many people to star that so perhaps the developers won't keep telling us it's "Hit or miss" and not a big issue.
Capt. Martin#30 said:
How do i get it back now?
Click to expand...
Click to collapse
I had an extreme case just this week where simply re-flashing the CWM alone still didn't work. In my case, to get back on track I had to flash the Stock Recovery first then afterward testing to be sure I had access, I flashed CWM and all was fine again. Just an FYI if you run into that situation.
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus
riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.
lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk
Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Well u do have APX mode... is there a day to do something with that?
I7
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
krhainos said:
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Click to expand...
Click to collapse
the bold part is where I can really use some help!!!!
have a tf300t, neither unlocked nor rooted atm.... I never got an OTA after purchase, always had to manually download zip and update, i cannot even unlock the damn device!!!! some unknown network error issue, even tough m fully connected ! its begining to irritate me to the core that anyone asking me advice on what to buy , i say straight up that if its asus it will be crap don't buy it!
i can really use some help regarding this.... it looks like some serial number issue..... :'(
ASUS Rep HELP me please!
Paschalis said:
I7
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
I've been trying to figure this out. But so far nothing. I've tried flashing cm10 images in fastboot. I built a recovery and used it to try and go back to stock but it give me a mismatch error. I tried flashing cm10 in recovery and everything takes me back to asus screen. Any other ideas I could try?
I would love to be able to use my tablet again.
darthvince said:
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
Click to expand...
Click to collapse
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Paschalis said:
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
krhainos said:
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
Click to expand...
Click to collapse
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Drgravy said:
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Click to expand...
Click to collapse
I have a TWRP version for someone to test here: http://forum.xda-developers.com/showthread.php?t=1843694
Flash with fastboot.
I created an RMA request with Asus, the fellow on the phone says it's bewteen $87 to $100 to repair the OS on a device with an unlocked bootloader. This excludes the cost of you shipping Asus the tablet. However, it includes the cost of labor, diagnostic, and shipping back to you.
For those of you weighing your options, there's one answer.
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Rompf said:
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Click to expand...
Click to collapse
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
TF300T in repair in Texas as well...
krhainos said:
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
Click to expand...
Click to collapse
My TF300T is in Grapevine TX having the same exact thing done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
bjanice44 said:
My TF300T is in Grapevine TX having the same exact hting done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
Click to expand...
Click to collapse
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
krhainos said:
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
Click to expand...
Click to collapse
Thanks
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What I understood is that's a partitioning difference on JB... Bricked mine too, more and more showing up on these boards... I guess the more issues will show up, the bigger the chance we can have someone fix them (Not me, that's for sure )
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.