is it bricked or maybe not? - Eee Pad Transformer Q&A, Help & Troubleshooting

hi guys,
I have a SL101.ok here is the problem. I was on CM10 and wanted to switch to other ROMS and kernels. but somehow I got into a boot loop. I flashed JB 4.2 by team EOS, GAPPS for TF101 and elite EOS. yes, I did a full wiped. but no, the tablet refused to boot. I tried the tool made by things-o-doom . Still no luck...i can't access my recovery,cause my volume down button is broken, volume up button is sunk in but still usable... . is my tablet dead?
Sent from my supercharged :tank:

hisname said:
hi guys,
I have a SL101.ok here is the problem. I was on CM10 and wanted to switch to other ROMS and kernels. but somehow I got into a boot loop. I flashed JB 4.2 by team EOS, GAPPS for TF101 and elite EOS. yes, I did a full wiped. but no, the tablet refused to boot. I tried the tool made by things-o-doom . Still no luck...i can't access my recovery,cause my volume down button is broken, volume up button is sunk in but still usable... . is my tablet dead?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
I don't own an SL101. can it be flashed with Nvflash in apx mode? easy flasher?back to stock then root again? look for th stock version here or Maybe @ asus no too sure.
sent from TF101 with Android 4.2.2
---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------
YayYouFixedIt said:
I don't own an SL101. can it be flashed with Nvflash in apx mode? easy flasher?
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
oh that kernel didn't work for me. I think its a 4.1.2 kernel. tty kat kernel if you can get it flashed by usb
sent from TF101 with Android 4.2.2

YayYouFixedIt said:
I don't own an SL101. can it be flashed with Nvflash in apx mode? easy flasher?back to stock then root again? look for th stock version here or Maybe @ asus no too sure.
sent from TF101 with Android 4.2.2
---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------
oh that kernel didn't work for me. I think its a 4.1.2 kernel. tty kat kernel if you can get it flashed by usb
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
flash by USB? how?
Sent from my supercharged :tank:

hisname said:
flash by USB? how?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
good question. I couldnt see anything about it while googling. but there might still be a way by nvflashing stock no? as long as you can goto apx mode dont give up hope.
sent from TF101 with Android 4.2.2

YayYouFixedIt said:
good question. I couldnt see anything about it while googling. but there might still be a way by nvflashing stock no? as long as you can goto apx mode dont give up hope.
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
yep, I can go into APX mode. but sadly not recovery. damn the volume down button AFAIK most recovery tools here do not support SL101. except the one by things o doom...
Sent from my supercharged :tank:

hisname said:
yep, I can go into APX mode. but sadly not recovery. damn the volume down button AFAIK most recovery tools here do not support SL101. except the one by things o doom...
Sent from my supercharged :tank:
Click to expand...
Click to collapse
did you try these instructions http://mobility.forumsee.com/a/m/s/...asher-install-cwm-root-unbrick-one-click.html
sent from TF101 with Android 4.2.2
---------- Post added at 12:40 PM ---------- Previous post was at 12:25 PM ----------
YayYouFixedIt said:
did you try these instructions http://mobility.forumsee.com/a/m/s/...asher-install-cwm-root-unbrick-one-click.html
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
oops thought it said it works but it doesnt
sent from TF101 with Android 4.2.2

You might have to take the tablet apart if you want to manually press the volume down and get into recovery.

Solar.Plexus said:
You might have to take the tablet apart if you want to manually press the volume down and get into recovery.
Click to expand...
Click to collapse
WTF? Take out apart? is there an easier way or something?
Sent from my supercharged :tank:

hisname said:
WTF? Take out apart? is there an easier way or something?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Well, I do not know of any way to get to recovery or APX mode without using the volume buttons. Since you have a SL101, APX mode is pretty useless since the SBK keys are not known to use NVFlash.
If you cannot boot to a ROM, the only way to get to recovery is VOL DOWN and POWER. If your VOL DOWN is not working, you are pretty much not gonna get anywhere if you cannot boot.
Sorry that Asus did not build in an additional back door beyond using the hardware buttons in case you happened to break them.

There's just got be a way to take the tablet apart though.

Solar.Plexus said:
There's just got be a way to take the tablet apart though.
Click to expand...
Click to collapse
Google search for "Asus Slider Teardown":
http://www.techrepublic.com/blog/cr...ardown-solid-tablet-but-not-without-flaws/399
And
http://www.youtube.com/watch?v=JG9gEYRALtU

ok guys, I know this sounds stupid and retarded. I highly doubt that anyone has ever asked such a question in this forum.. The question is:is there any possible way I can brick my SL101??reason I am asking is because I am still covered by my warranty. but ASUS still knows that I rooted my tab because of the team EOS boot animation.
Sent from my supercharged :tank:

I've already sent my rooted tablet to Asus for rebooting problems and they replaced it with no problem. It was still cover by warranty.
Maybe they didn't looked, or just didn't care about it.
No way to be sure it'll be ok for you, but in all case (if you're sure you can't fix the volume-up button by yourself) you're not going anywhere with your tablet.
Good luck.

147keul said:
I've already sent my rooted tablet to Asus for rebooting problems and they replaced it with no problem. It was still cover by warranty.
Maybe they didn't looked, or just didn't care about it.
No way to be sure it'll be ok for you, but in all case (if you're sure you can't fix the volume-up button by yourself) you're not going anywhere with your tablet.
Good luck.
Click to expand...
Click to collapse
+1. I RMA'd my rooted SL101 to TX and had no issues. They asked if they could power it up to verify eveything worked.
D

but it is sitting at team eos boot animation, will Asus not get suspicious or anything?
Sent from my supercharged :tank:

hisname said:
but it is sitting at team eos boot animation, will Asus not get suspicious or anything?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Depends on if they even check it.
On a side note and not wanting to hijack this thread, my SL101 was bought second hand. Is there a way to see if the tablet is still under warranty?

Solar.Plexus said:
Depends on if they even check it.
On a side note and not wanting to hijack this thread, my SL101 was bought second hand. Is there a way to see if the tablet is still under warranty?
Click to expand...
Click to collapse
Typically it's one year. Hit asus.com and register it. It will tell you.
D

As soon as you see a boot animation adb should be broadcasting, get into an adb shell (if you dont know how, there are many tutorials around) use the command "reboot recovery" and it will reboot straight into recovery.
If you dont see the boot animation or adb is not working, i cant help more sorry, There might be some kind of debugging bridge inside the tablet but that will require some googling and then still its a pretty advanced procedure. Good luck:good:

JoinTheRealms said:
As soon as you see a boot animation adb should be broadcasting, get into an adb shell (if you dont know how, there are many tutorials around) use the command "reboot recovery" and it will reboot straight into recovery.
If you dont see the boot animation or adb is not working, i cant help more sorry, There might be some kind of debugging bridge inside the tablet but that will require some googling and then still its a pretty advanced procedure. Good luck:good:
Click to expand...
Click to collapse
but remember I wiped everything in recovery and flashed a new rom. how could adb be enabled? adb device shows "no device found"
Sent from my supercharged :tank:

hisname said:
but remember I wiped everything in recovery and flashed a new rom. how could adb be enabled? adb device shows "no device found"
Sent from my supercharged :tank:
Click to expand...
Click to collapse
USB Debugging has to be enabled in the ROM, and your cable has to be good. If you have a custom recovery, ADB should also work in there for most things.

Related

XI9000 Q&A

Well made this thread to ask the question haha
Would you suggest this rom or erikk's one? both are alpha
It looks like Eriks is a full Sony port and this is only a modified aokp with some Sony apps
Sent from my SGH-T959V using xda app-developers app
Mhm...okay. I was just actually about to test it out.
Sent from my SGH-T959V using Tapatalk 2
pisherthefisher said:
It looks like Eriks is a full Sony port and this is only a modified aokp with some Sony apps
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I wanted something easy
Has anybody gotten it to flash? I just tried, and I get a recovery loop. Fortunately, was able to power cycle back into recovery and get miui flashed. I was afraid at first I was going to have to one click back and start over.
gregcapps said:
Has anybody gotten it to flash? I just tried, and I get a recovery loop. Fortunately, was able to power cycle back into recovery and get miui flashed. I was afraid at first I was going to have to one click back and start over.
Click to expand...
Click to collapse
I'll look into it, and a question for experienced porters or devs. When I compile it (yes I am a zip noob) do I have to select no compression, or it doesn't matter?
th3controller said:
I wanted something easy
Click to expand...
Click to collapse
I didn't mean to make it sound like that's a bad thing. Some people will prefer your rom because of the aokp features and some will prefer eriks for stock sony.
Either way, thank you for contributing your rom to the sgs4g development. It's very much appreciated
"flashing failed" in TWRP.
I'll try a new DL and let you know what happens.
---------- Post added at 06:32 PM ---------- Previous post was at 06:15 PM ----------
2nd DL, "Checking state of BML/MTD..." and then recovery loops.
DO not attempt to flash the zip file. It is improperly compiled, I will have a fix soon probably by tomorrow or tonight.
If you attempted to flash and got stuck on a boot loop, flash back to stock OR flash another ICS ROM.
Im stuck on the loading screen and can't get in download mode after being stuck in bootloop
Bricked
Phone stuck on load up screen and won't go into recovery or download mode.
chedy2009 said:
Phone stuck on load up screen and won't go into recovery or download mode.
Click to expand...
Click to collapse
First what model of phone do you have? Second if it is indeed the t959v you're not bricked. To get into recovery hold BOTH volume buttons and power. Once the boot screen gets brighter let go of power only.
I do have t959v but i tried what youre saying but the screen doesnt get brighter it just says dim
OK. Try this. same button combo. As soon as you see the splash screen count to two then let go of POWER. If that doesn't work do it by counting to three.
Tried that to but still nothing idk how flashing a rom could cause this
chedy2009 said:
Tried that to but still nothing idk how flashing a rom could cause this
Click to expand...
Click to collapse
What ROM were you on before you flashed? And flashing a ROM shouldn't cause this. You said you can't enter DL mode either?? Have you used Odin or Heimdall before??
to go to stock follow hechoen's saying, but on TEAM ACID logo, wait for a LIGHT CHANGE and let go of the buttons. That is how I goto recovery every single time.
I trying to put the Xperia rom that we just got in the t959v forum but it was a bad link that just puts your phone into a bootloop.
chedy2009 said:
I trying to put the Xperia rom that we just got in the t959v forum but it was a bad link that just puts your phone into a bootloop.
Click to expand...
Click to collapse
Comment removed. Never a good idea to comment before my first mug of coffee.
Sent from my SGH-T959V using xda premium
gregcapps said:
Comment removed. Never a good idea to comment before my first mug of coffee.
Click to expand...
Click to collapse
Or the 6th beer. lol Greg did you flash this yesterday?? And if you did did it break recovery for you? or DL mode?

[Q] [SOLVED] Urgent! Status 7 when installing a ROM and wont install OTA

Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help
It has a password screen. what does that even mean? is that encrpyted from the seller as I can ask the seller to put it in... What am i even meant to do?
weeo said:
Hi,
i have a Xoom and it wont install any ROMS. It is a wingray model and it gets status 7 (symlink) when installing CM10 and errors when install Superuser.zip. It isnt recovery as GAPPS install. Its running CWM and i cant get the tablet to boot up. I also used HWI69.zip and restored the images and no its askes for a password? Wth? But I really want CM10 back on my tablet. I restored ALL the images. Can i get rid of this password screen?
Please help
Click to expand...
Click to collapse
Boot into fastboot, then unlock it
Code:
fastboot oem unlock
Mjamocha said:
Boot into fastboot, then unlock it
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?
weeo said:
Hi,
Thank you for reply but I got it working. It's on 3.01 now but how do I root this properly and get it on CM10?
Click to expand...
Click to collapse
Universal Root
or
7Heavens Projekt
Mjamocha said:
Universal Root
or
7Heavens Projekt
Click to expand...
Click to collapse
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks
weeo said:
It'll have to be 7heavens as the other one hasn't got a download link. File has been deleted
Thanks
Click to expand...
Click to collapse
The universal root - has the links witin the instructions. I just tried the links and they are valid.
Mjamocha said:
The universal root - has the links witin the instructions. I just tried the links and they are valid.
Click to expand...
Click to collapse
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app
weeo said:
Have you got a rooted Xoom? Could you take me through the process as it never works for me
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10
matt4321 said:
How far have you got? Have you unlocked the bootloader through fastboot?
Once that's done it's fairly easy. Just fastboot flash a custom recovery. I recommend Team Rogues recovery: http://forum.xda-developers.com/showthread.php?t=1235170
then reboot the device, but go into recovery before the device boots or the recovery is overwritten. To get into recovery: power on, 2 seconds later press the down button, then press the up button once you see 'Android Recovery'
Then flash the zip I have attached to root the device. Choose the JB one if you're on jelly bean, anything else, so honeycomb or ICS use the other one.
From there it's the same as any other device. Backup apps etc, make a nandroid, wipe data/factory reset, install CM10
Click to expand...
Click to collapse
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.
weeo said:
Oh ok. I'll flash that as I'm on honeycomb. Will report back if I get a status 7 again.
Click to expand...
Click to collapse
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well
matt4321 said:
That's something to do with CM reads the device as XOOM but on stock a wingray is MZ604 so if I remember rightly that's what causes the status 7, to get around it, once rooted use a build prop editor to change your model to XOOM not MZ604. I think that's the way to get around it if my memory serves me well
Click to expand...
Click to collapse
Thank you. So that's what a sym link error is?
weeo said:
Thank you. So that's what a sym link error is?
Click to expand...
Click to collapse
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution
matt4321 said:
Don't me hold to it, but I seem to remember others getting status 7 errors and it was just to do with how the CM zip reads your device. You can also turn off script verification in android recovery. I think that was also another solution
Click to expand...
Click to collapse
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.
weeo said:
Thanks. Doing it now. Just install SU. Good luck with Gigatechworld... formerly known as Orion... BTW i know this as im your website owners friend.
Click to expand...
Click to collapse
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean
matt4321 said:
Glad you got everything working alright. Cheers. sweet! you know friends through xda or you actually know know him? if you know what I mean
Click to expand...
Click to collapse
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion
weeo said:
XDA. We've been friends for 2 years. I use to make ROMS for the ZTE blade. I think he started talking to me when I made HTC Sense with a few others on the blade. I have him the idea for Orion
Click to expand...
Click to collapse
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?
matt4321 said:
that's pretty awesome! I remember you over at modaco, used to be fairly active there as the zte blade has a big community there but the xoom has a bigger one here. how come you didn't come aboard with us on the blog?
Click to expand...
Click to collapse
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .
weeo said:
I was active a lot here too. Till I shut my account down. I already have my own website. That's where the idea was set off from.
Success, CM10 is booting on my Xoom .
Click to expand...
Click to collapse
That's awesome!
Nice to hear you have CM10 running too, so much better than stock
matt4321 said:
That's awesome!
Nice to hear you have CM10 running too, so much better than stock
Click to expand...
Click to collapse
Thanks to you
Sent from my Xoom using XDA Premium HD app

Need people to run adb commands for twrp 4.2

Hey guys!!
We may have a solution to the recovery issue found after updating to the 4.2 build!!
However, someone needs to run some commands in ADB for the TeamWin team.
I am NOT on the 4.2 update or i would do it myself.
But if there is someone on the 4.2 update who isnt very familiar with ADB, i am more than happy to run a TeamViewer remote desktop session to figure this out.
I cannot wait to solve this!
Thanks for reading guys!
elesbb said:
Hey guys!!
We may have a solution to the recovery issue found after updating to the 4.2 build!!
However, someone needs to run some commands in ADB for the TeamWin team.
I am NOT on the 4.2 update or i would do it myself.
But if there is someone on the 4.2 update who isnt very familiar with ADB, i am more than happy to run a TeamViewer remote desktop session to figure this out.
I cannot wait to solve this!
Thanks for reading guys!
Click to expand...
Click to collapse
You don't say what they wanted run.
I will be doing this myself in the next few hours but if someone would like to do it now can they please install terminal emulator from market if you are already on 4.2.1 update and run the following 2 commands and paste the output here.
ls /dev/block
mount
Deleted
flumpster said:
You don't say what they wanted run.
I will be doing this myself in the next few hours but if someone would like to do it now can they please install terminal emulator from market if you are already on 4.2.1 update and run the following 2 commands and paste the output here.
ls /dev/block
mount
Click to expand...
Click to collapse
It's because you need to be on the freenode chat with them while doing it. I don't think it's simply those two commands because they want some commands ran while inside TWRP
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
It's because you need to be on the freenode chat with them while doing it. I don't think it's simply those two commands because they want some commands ran while inside TWRP
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Yea figured that out but can't do it right now. Would help otherwise. The read out from those commands was too long to post. Better to have some who can go freenode to help.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Lol. I give up.
I am one of the devs from the prime forums and was just trying to help you out because I was the person that edited twrp to work on data2sd installs.
I will head back to the prime forums and try to get it to work there instead
flumpster said:
Lol. I give up.
I am one of the devs from the prime forums and was just trying to help you out because I was the person that edited twrp to work on data2sd installs.
I will head back to the prime forums and try to get it to work there instead
Click to expand...
Click to collapse
I'm confused lol. I can't do anything lol. You gotta talk to the guys over at TWRP I was just merely getting volunteers to help out.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ok I have re-updated to 4.2.1 and seem to have a successful way to now to go back and forth between 4.1.1 & 4.2.1
Here is a screenshot of those two commands "ls /dev/block" & "mount" which shows the partitions still in ext4, which I think blows my theory out the door
I have also been contacted by eyeballer to jump into the twrp on freenode chat but just waiting till were both online
pjc21 said:
Ok I have re-updated to 4.2.1 and seem to have a successful way to now to go back and forth between 4.1.1 & 4.2.1
Here is a screenshot of those two commands "ls /dev/block" & "mount" which shows the partitions still in ext4, which I think blows my theory out the door
I have also been contacted by eyeballer to jump into the twrp on freenode chat but just waiting till were both online
Click to expand...
Click to collapse
Awesome paul!! How do you go back and forth between 4.2 and 4.1? Just flash the different .blob files?
Oh also look for Dees_Troy on freenode. He can help as well. Its who i was talking to.
elesbb said:
Awesome paul!! How do you go back and forth between 4.2 and 4.1? Just flash the different .blob files?
Click to expand...
Click to collapse
First I did a clean wipe from twrp then installed WW_epad-user-10.4.2.20.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed that zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification. I clicked and installed and once the system had rebooted into new android 4.2.1 system I get a triangle notification with a downgrade option to 10.4.2.20
---------- Post added at 12:41 PM ---------- Previous post was at 11:45 AM ----------
Hi,
Have just been talking to Dees_Troy and this is what he had to say
<Dees_Troy> We are going to have to update the kernel
<Dees_Troy> The new bootloader changed something about the partition scheme
<Dees_Troy> I will post a test build tomorrow in the 300 twrp thread
<Dees_Troy> Without the new kernel the entire internal emmc chip doesn't show up at all
<Dees_Troy> Having the new kernel will fix it but I won't be able to patch it to allow backup and restore of boot / kernel until we get source
<Dees_Troy> If you hang around another hour I might have time to make a test build
So where getting somewhere now :good:
Hopefully only a matter of hours or days now till we should have a working recovery with 4.2.1
pjc21 said:
First I did a clean wipe from twrp then installed WW_epad-user-10.4.2.20.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed that zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification. I clicked and installed and once the system had rebooted into new android 4.2.1 system I get a triangle notification with a downgrade option to 10.4.2.20
---------- Post added at 12:41 PM ---------- Previous post was at 11:45 AM ----------
Hi,
Have just been talking to Dees_Troy and this is what he had to say
<Dees_Troy> We are going to have to update the kernel
<Dees_Troy> The new bootloader changed something about the partition scheme
<Dees_Troy> I will post a test build tomorrow in the 300 twrp thread
<Dees_Troy> Without the new kernel the entire internal emmc chip doesn't show up at all
<Dees_Troy> Having the new kernel will fix it but I won't be able to patch it to allow backup and restore of boot / kernel until we get source
<Dees_Troy> If you hang around another hour I might have time to make a test build
So where getting somewhere now :good:
Hopefully only a matter of hours or days now till we should have a working recovery with 4.2.1
Click to expand...
Click to collapse
That is some sexy news! At least we will get root again! omg i think i have a hard on now xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Well I've got a long night ahead of me so I'm thinking about flashing the stock recovery and doing the update
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 09:56 PM ---------- Previous post was at 09:44 PM ----------
elesbb said:
That is some sexy news! At least we will get root again! omg i think i have a hard on now xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
+1 x10
Sent from my SAMSUNG-SGH-I747 using xda premium
keep us updated paul!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
keep us updated paul!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Will do, just waiting to hear back about test build :good:
Here is slightly more detailed method of what I did:
What I did is from running CROMI, I booted into twrp and first I did a clean wipe then installed WW_epad-user-10.4.2.20.zip which can be extracted from the WW_epaduser_10_4_2_20_UpdateLauncher.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed EP201_768_SDUPDATE.zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification in the notification menu of loaded android os.
I clicked and installed and once the system had rebooted into new android 4.2.1 system I get another triangle notification in notification menu with a downgrade option to 10.4.2.20.
If you do not get the notification to downgrade back to 4.1.1 you can try copying the WW_epad-user-10.4.2.20.zip to you internal sd card and you should then get notification after a few seconds.
There is no need to boot into stock recovery, just click on the notification in the notification menu that pop up from loaded android os.
You can boot into fastboot and flash twrp if you want but it will be encrypted/unusable so best to wait for the new build of recovery.
Feel like hugging you man... (no homo) appreciate all your doing... and everyone trying to get this thing working.. was wondering. I have only the new bootloader with the weird fastboot... would this be beneficial to me at all? And im willing to try a fastboot of recovery for testing, lol cause ill be able to tell you fairly quickly whether its working for my type of scenario. .
Lemme know
:thumbup:
Sent from my SPH-D710 using Tapatalk 2
Hmmm... I dont know whats going on man... maybe my bootloader is screwed up. It says it writes it. But again. It seems like the tablet just locks up.. that green box over the rck doesnt flash after writing. No download bar or anything.. there any way to reflash the bootloader as writeable? Or maybe an older version as writeable? Damn this sux..
Sent from my SPH-D710 using Tapatalk 2
Goddly said:
Hmmm... I dont know whats going on man... maybe my bootloader is screwed up. It says it writes it. But again. It seems like the tablet just locks up.. that green box over the rck doesnt flash after writing. No download bar or anything.. there any way to reflash the bootloader as writeable? Or maybe an older version as writeable? Damn this sux..
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
After you are flashing that new twrp.blob are you restarting the tablet before trying to go into recovery ?
The flashing just places it to staging area ready to flash on next restart.
As in .. reboot regular? Power button.. after writing completes I cant reboot from command
Sent from my SPH-D710 using Tapatalk 2
---------- Post added at 01:14 AM ---------- Previous post was at 01:12 AM ----------
It just seems like my bootloader is locking up.... im about to throw this thing against the wall.... I cant do anything with it...
Sent from my SPH-D710 using Tapatalk 2
I'm sorry I'm late, but for the future a little trick. If anyone will run commands in terminal emulator, at the end of command like: ls /dev/block type >/sdcard/lsoutput.txt and then you can post or attach this txt file.
Just to make it a little easier.
If you will do logcat with this txt output don't break it because it runs a little longer until it finishes.

Now i killed it

Hi
I just did the dumbest thing
I was on stock 4.2.1 and installed TWRP for 4.1. cause i wanted to go back to 4.1
Now when i do vol- power, no recovery just says device unlocked, asus logo....
Any way possible out of this mess???
PLSSSSSSS
Anyone?
maybe :
HTML:
http://forum.xda-developers.com/showthread.php?t=2179874&page=9
riderskull said:
maybe :
HTML:
http://forum.xda-developers.com/showthread.php?t=2179874&page=9
Click to expand...
Click to collapse
No m8 ty anyway
I cant get to fastboot mode or recovery it self
DodgeBullets said:
I was on stock 4.2.1 and installed TWRP for 4.1. cause i wanted to go back to 4.1
Click to expand...
Click to collapse
To put it bluntly, you ****ed yourself. It's bricked. Only way to fix right now is send it in to Asus, expect $80-$200 to fix it. That will probably be the only way to fix it.
You screwed up. You flashed TWRP for 4.1 when you are on 4.2.1. There is no coming back from that if you can't flash. You don't even have fastboot. So nobody here can help you.
sevenalive said:
To put it bluntly, you ****ed yourself. It's bricked. Only way to fix right now is send it in to Asus, expect $80-$200 to fix it. That will probably be the only way to fix it.
You screwed up. You flashed TWRP for 4.1 when you are on 4.2.1. There is no coming back from that if you can't flash. You don't even have fastboot. So nobody here can help you.
Click to expand...
Click to collapse
Yeah...
I can get APX mode PC recoggnizes it alredy instaled the driver for it...
Can i do anything in APX mode?
I bricked mine a while back. I purchased my tablet at Walmart. Took a chance and went back to exchange for a new unit. The guy was clueless, gave me a new tablet at no charge. He didn't even try to turn it on.
Asus TF300T, CleanROM Inheritance
I think that's the way Godly bricked his tablet... If so, there's no way to unbrick it, at least until now...
Sent from my ASUS Transformer Pad TF300T using CROMI

TWRP 2.6 Password + Others

I was updating my 4.1 bootloader to the 4.2. I first downloaded the firmware from the website, updated successfully. Then i installed twrp2.6 using fastboot, and right when i boot in, it asks me for a password. I naturally dont know the password, so i decided to just turn it off and try tomorrow. Now I cant boot into the bootloader and it goes straight to twrp.
any ideas? thanks
As many others said use twrp 2.5 -4.2
Twrp 2.6 causes problems I think you have a brick now
Sent from my sensational HTC Desire C
noahvt said:
As many others said use twrp 2.5 -4.2
Twrp 2.6 causes problems I think you have a brick now
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Oh boy that is disappointing news. Can I do anything to remedy this issue?
Akosp said:
Oh boy that is disappointing news. Can I do anything to remedy this issue?
Click to expand...
Click to collapse
if you can't acces the bootloader you're out of luck :'(
Akosp said:
Oh boy that is disappointing news. Can I do anything to remedy this issue?
Click to expand...
Click to collapse
if you mean when you boot into twrp you need a password then just turn off you tablet the hold the volume down and power on your tablet then use fastboot to flash the proper version of twrp and then you should be good to go
noahvt said:
if you can't acces the bootloader you're out of luck :'(
Click to expand...
Click to collapse
Yeah it boots straight into twrp. Thanks for the help guys, anyone looking for parts? :laugh::crying:
Did you get this fixed?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
robgee789 said:
Did you get this fixed?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
Click to expand...
Click to collapse
ive done just about everything I can on my part. I could not set up nvflash since my tablet was already on the jb bootloader. I'm looking for someone who can j-tag my device at the moment, but as far as I can tell my device is bricked indefinitely :\
Akosp said:
ive done just about everything I can on my part. I could not set up nvflash since my tablet was already on the jb bootloader. I'm looking for someone who can j-tag my device at the moment, but as far as I can tell my device is bricked indefinitely :\
Click to expand...
Click to collapse
can you use adb while in twrp or does the password stop you?
robgee789 said:
can you use adb while in twrp or does the password stop you?
Click to expand...
Click to collapse
im pretty sure this password is not letting me do anything other than turn off. if i try to browse my files every partition shows up as 0mb.
It might be worth a try mate you never know
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4
Akosp said:
im pretty sure this password is not letting me do anything other than turn off. if i try to browse my files every partition shows up as 0mb.
Click to expand...
Click to collapse
what about trying this mate?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12

Categories

Resources