I had previously posted this as a reply to a different thread, but my problem has gotten out of hand. I need help desperately!:crying:
I'll start from the beginning, and try to be as detailed as possible...
I own the Asus Transformer slider (sl101) ICS 4.0.3
I rooted and all the good stuff using motochopper, everything worked like a charm..
The big trouble arises when I decided to flash CWM recovery through Rom manager.. Since Rom Manager had never failed me before in showing the recoveries for "compatible" devices I decided to give it a shot at the only recovery it "attested" was compatible..The TF101 recovery...
Without further ado, I proceeded to flash that recovery ASSUMING that since both are very similar ASUS products they were compatible in some way(I know total derp failure). To a certain extent that was true, I ended up flashing CWM Recovery 6.0.1.3 and booted it up successfully.
This Is where it got bad.. So I decided to do a simple factory wipe from the recovery, only to find out that the recovery would ALWAYS get stuck on formatting /data...After the disappointment I rebooted the Tab to see if it had worked anyway AFTER being stuck on that "formatting /data"
state..Surprise surprise! BOOT LOOP on the ASUS bootup animation.
Found out the factory wipe(just my luck) had wiped the setting that would have been a life saver, the ADB interface, and no matter how far or how long I waited into the boot animation, ADB was gone.
That being said, naturally every single unbrick tool and file wpuld be useles without adb..So I said to myself, "not to worry, I can flash another recovery from CWM, right?" NO SIR! CWM would throw an error reading "can't mount sdcard" and no matter what I did, flashing zip's was a dead end..
After all that playing around I found that CWM somehow mounted an ADB interface in "recovery" mode, or that is what the "adb devices" command would show. Anywho I tried the "unbricking" tools available...NONE did the trick..
After looking around for hours and previously noticing a "/staging" partition, I stumbled upon a post in Transformer Forums, stating that any .blob file inside the aforementioned partition would be flashed during boot, so I tried to "adb push" using the previously mounted "recovery" adb interface to copy or "push" TWRP recovery blob file to the said partition.....reboot..nothing..CWM still clings to my tab..
Well, I still have the recovery ADB, so there is still hope..Therefore I found an easy flash tool that supposedly flashes TWRP and unbricks the device through adb, this was PERI http://forum.xda-developers.com/show....php?t=1681155
After three reboots in the process of using this tool and for a brief moment, a progress bar appeared in the "Eee Tab" spalsh screen, showing that the recovery was being installed.
THIS IS WHERE HELL BROKE LOOSE...After "flashing" TWRP "successfully" I manually booted the recovery only to find that NOTHING would happen, as if "booting recovery kernel image" just did nothing and proceeded to boot the device normally(which of course did NOT happen).
So then, here I am, NO adb, NO recovery whatsoever, and APX mode has done me no good...I searched and searched, only to find that Wheelie and NvFlasher are useless for the Slider and B90 Serial # devices(which again just my luck)Tried them anyway to NO avail...
I have some pretty solid reasons to be desperate here. So please, if ANYONE could provide ANY helpful tips or information, it would be very, VERY much appreciated.
P.S. I also tried the MicroSD manual OTA Update zip file downloaded from ASUS support, renaming such to EP101_SDUPDATE.zip or update.zip rendered no results, as the white fonts(fastboot?) show "skipping android ota checking"..
Help with sl101
I'll try to help here. First, download this TWRP built for the slider to your pc:
https://dl.dropboxusercontent.com/u/47619656/signed_twrp-2.6.3.9_sl101.zip
Unzip it on your pc in a separate folder and you should see a file 'twrp.blob'. Open a command prompt or terminal (if linux) and type the following commands:
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
exit
Then from the directory that you unzipped the twrp.blob in, type the following in a command prompt or terminal:
Code:
adb push ./twrp.blob /sdcard/twrp.blob
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
adb reboot
If that worked, then you see the blue flashing bar, and since you have no ROM, at least an attempt to boot one up. Then try to get back into recovery with holding volume down and power, then volume up when the white text appears. You should see twrp recovery built for your sl101. Once, in twrp, you can use the adb sideload function to transfer and flash a ROM from your PC. From the directory where your ROM.zip is, in a command prompt or terminal and tab in adb sideload mode, type:
Code:
adb sideload ROM.zip
Replacing ROM.zip with the actual name of your ROM file. If the above doesn't work then try:
Code:
adb sideload ./ROM.zip
And stay away from ROM Manager in the future, it's no good for our 101 series devices.
Thanks for your reply,:good:
I would gladly try your procedure ASAP, yet there is a big problem, I cannot get adb to recognize my tablet. I have no means of enabling it in the tablet as it simply will not get far enough in the boot process to allow adb. I pointed out in my first post that I tried a foctory reset in CWM, which got forever stuck and I rebooted in the "middle" of the process, however it seems that it did "wipe" the ADB settings, and now no matter what kind of boot settings I choose there is no way I can access adb.
I must prioritize the finding of a way to access adb, as naturally without it, I cannot input any kind of commands..
Thanks for the suggestion, yet without adb I do not see a way to try it.
Timberwolfhusky said:
Thanks for your reply,:good:
I would gladly try your procedure ASAP, yet there is a big problem, I cannot get adb to recognize my tablet. I have no means of enabling it in the tablet as it simply will not get far enough in the boor process to allow adb. I pointed out in my first post that I tried a foctory reset in CWM, which got forever stuck and I rebooted in the "middle" of the process, however it seems that it did "wipe" the ADB settings, and now no matter what kind of boot settings I choose there is no way I can access adb.
I must prioritize the finding of a way to access adb, as naturally without it, I cannot input any kind of commands..
Thanks for the suggestion, yet without adb I do not see a way to try it.
Click to expand...
Click to collapse
Sorry, I thought you said that you COULD get to adb in recovery. My apologies. Sounds like what you need is nvflash method, but may not be an option for you. If I think of anything else I'll post back.
sidneyk said:
Sorry, I thought you said that you COULD get to adb in recovery. My apologies. Sounds like what you need is nvflash method, but may not be an option for you. If I think of anything else I'll post back.
Click to expand...
Click to collapse
Indeed, AT FIRST I could somehow get into ADB's "recovery" mode through CWM, took advantage of this to flash TWRP(can't recall version), only to find that i could not boot into any recovery, neither CWM nor TWRP, just as if the system just "skipped" the recovery and went into the usual bootloop..
I tought of the APX mode too which uses NvFlash as well, yet, I found that due to the slider's serial number, no SBKs could be used with either Wheelie or NvFlash..so I hit a dead end with those..
It is complicated, yet I might have omitted something, if you could point out so, you'd be my hero.
Thanks again for your time.
Timberwolfhusky said:
Indeed, AT FIRST I could somehow get into ADB's "recovery" mode through CWM, took advantage of this to flash TWRP(can't recall version), only to find that i could not boot into any recovery, neither CWM nor TWRP, just as if the system just "skipped" the recovery and went into the usual bootloop..
I tought of the APX mode too which uses NvFlash as well, yet, I found that due to the slider's serial number, no SBKs could be used with either Wheelie or NvFlash..so I hit a dead end with those..
It is complicated, yet I might have omitted something, if you could point out so, you'd be my hero.
Thanks again for your time.
Click to expand...
Click to collapse
Hi Timberwolfhusky, any recent progress? I'm anxious to see how this goes, because I may wind up having to to go down the same path.
I also just rooted my sl101 (I used 1-Click Transformer Root_1.1 via Windows VM - I'm on a Mac) , and have a CWM recovery installed through RM, but now I'm stuck. I'm unable to run a backup, because the /sdcard isn't mounting, nor giving me the option when I manually boot into recovery. So I'm not completely screwed yet, but unable to proceed any further.
JGarrido said:
Hi Timberwolfhusky, any recent progress? I'm anxious to see how this goes, because I may wind up having to to go down the same path.
I also just rooted my sl101 (I used 1-Click Transformer Root_1.1 via Windows VM - I'm on a Mac) , and have a CWM recovery installed through RM, but now I'm stuck. I'm unable to run a backup, because the /sdcard isn't mounting, nor giving me the option when I manually boot into recovery. So I'm not completely screwed yet, but unable to proceed any further.
Click to expand...
Click to collapse
Hello and thank goodness you are interested, maybe this thread will grow to find solutions for SL101 users..
I did the same thing, I installed CWM through Rom Manager and it is to be noted that rom manager lists CWM FOR the TF101, which despite being similar to the slider, it just will not work.. I really do not know if rooting from a VM had anything to do with your problem. The most important thing here is if you still have ADB interface working.. as that should allow you to unbrick fairly easy. Can you STILL boot to CWM? if so, mounting the USB storage in "mounts and storage" in CWM should give you adb access.. With this you might want to either flash TWRP that sydneyk kindly provided in the second post or use PERI or other unbrick tools available..
I have not made ANY progress for I do NOT have any kind of access to ADB and NvFlash does not work with the slider..
Bottom line is, if you are able to flash another recovery that is not CWM you should be fine..
Please report back if you can get it solved, and do spread the word if you can as there is not much development for the slider and we could use the help..
Skipping android OTA checking
Just for the reference, I tried the OTA update functionality, which is placing the ROM update on the external MicroSD card, yet not only nothing happens or it shows an error, but trying to "update" shows "skipping android OTA checking"(I am attaching an image depicting this)
Still stuck with NO recovery, NO adb and NO OTA functionality...the ONLY glimmer of hope is NvFlash and APX mode, but we NEED those SBKs!
how isit possible that they are available for Tegra 3 devices but not for the Slider??
Still praying for help,
Peace.
For your ota to work you'll probably have to be able to first flash back a stock recovery.
Sent from my SM-N900T using XDA Premium HD app
sidneyk said:
For your ota a to work you'll probably have to be able to first flash back a stock recovery.
Sent from my SM-N900T using XDA Premium HD app
Click to expand...
Click to collapse
That is what I was afraid of...Yet how in the world am I going to flash ANYTHING without any ADB or NvFlash? I have a rope to the neck right now..I realize Rom Manager was a suicidal move..
Sent from my PC36100 using xda app-developers app
I've tried a few things since then, and the details are a bit fuzzy, but I believe I wound up using PERI (OneclickrecoveryV0.4.2) to install TWRP. Unfortunately the recovery it came with didn't seem to have any ability to interact with the touchscreen (v.2.5.0.0, I think?), and the hardware buttons don't work, so I was stuck.
I managed to pull a compatible recovery from elsewhere (v2.6.3.9), and swapped it out within PERI files so did manage to get it installed, and I can get into recovery mode now and move around, but every time I attempt to install a ROM, I get an assert error - apparently it's trying to identify my tablet as a tf101, instead of a sl101, and so the install fails. I've tried 3 different ROMs, so my guess is the recovery I'm running is what's actually generating the error, so I may have the wrong version installed, as this one appears to be not 100% compatible with a sl101. Now i'm wondering if the backup I was able to perform will even be restorable. I still have access to the working stock install, so all is not lost yet. I could abandon the process now and still have a fully functional tablet, though I've been experiencing some slowdowns lately, and would still like to get another ROM on here to see how it performs by comparison.
As a side note, I've tried using GooManager to assist with the recovery installation, backup process, and ROM download and installation, but the only useful thing I've managed to get it to do for me is reboot into recovery (now that I have it installed), but even that seems hit or miss. I also tried TWRP Manager, but all it does is display a splash screen with their logo, and then display a blank black screen after that, so it was completely useful to me.
Can anyone advise as to a working recovery and ROM combination (including version numbers)? I'd like to stick with CWM, if possible (most familiar with it), but it seems to be more problematic than TWRP, so i'll take anything that works at this point.
JGarrido said:
I've tried a few things since then, and the details are a bit fuzzy, but I believe I wound up using PERI (OneclickrecoveryV0.4.2) to install TWRP. Unfortunately the recovery it came with didn't seem to have any ability to interact with the touchscreen (v.2.5.0.0, I think?), and the hardware buttons don't work, so I was stuck.
I managed to pull a compatible recovery from elsewhere (v2.6.3.9), and swapped it out within PERI files so did manage to get it installed, and I can get into recovery mode now and move around, but every time I attempt to install a ROM, I get an assert error - apparently it's trying to identify my tablet as a tf101, instead of a sl101, and so the install fails. I've tried 3 different ROMs, so my guess is the recovery I'm running is what's actually generating the error, so I may have the wrong version installed, as this one appears to be not 100% compatible with a sl101. Now i'm wondering if the backup I was able to perform will even be restorable. I still have access to the working stock install, so all is not lost yet. I could abandon the process now and still have a fully functional tablet, though I've been experiencing some slowdowns lately, and would still like to get another ROM on here to see how it performs by comparison.
As a side note, I've tried using GooManager to assist with the recovery installation, backup process, and ROM download and installation, but the only useful thing I've managed to get it to do for me is reboot into recovery (now that I have it installed), but even that seems hit or miss. I also tried TWRP Manager, but all it does is display a splash screen with their logo, and then display a blank black screen after that, so it was completely useful to me.
Can anyone advise as to a working recovery and ROM combination (including version numbers)? I'd like to stick with CWM, if possible (most familiar with it), but it seems to be more problematic than TWRP, so i'll take anything that works at this point.
Click to expand...
Click to collapse
This is the only thing that works for me. I have been through the exact same thing that you have. I had to push blobs of some sort. All due to ROM Manager. I still use ROM Manager on my other three devices though. I never learn.
http://forum.xda-developers.com/showthread.php?t=1213723
D
Sent from my SPH-L900 using XDA Premium 4 mobile app
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
DatDude123 said:
This is the only thing that works for me. I have been through the exact same thing that you have. I had to push blobs of some sort. All due to ROM Manager. I still use ROM Manager on my other three devices though. I never learn.
http://forum.xda-developers.com/showthread.php?t=1213723
D
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
*** EDIT ***
And I only use ARHD and/or Revolver.
Sent from my SPH-L900 using XDA Premium 4 mobile app
---------- Post added at 10:11 PM ---------- Previous post was at 10:09 PM ----------
DatDude123 said:
This is the only thing that works for me. I have been through the exact same thing that you have. I had to push blobs of some sort. All due to ROM Manager. I still use ROM Manager on my other three devices though. I never learn.
http://forum.xda-developers.com/showthread.php?t=1213723
D
Sent from my SPH-L900 using XDA Premium 4 mobile app
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
*** EDIT ***
And I only use ARHD and/or Revolver.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
*** EDIT ***
http://forum.xda-developers.com/showthread.php?t=1518768
Sent from my SPH-L900 using XDA Premium 4 mobile app
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
DatDude123 said:
This is the only thing that works for me. I have been through the exact same thing that you have. I had to push blobs of some sort. All due to ROM Manager. I still use ROM Manager on my other three devices though. I never learn.
http://forum.xda-developers.com/showthread.php?t=1213723
D
Sent from my SPH-L900 using XDA Premium 4 mobile app
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
*** EDIT ***
And I only use ARHD and/or Revolver.
Sent from my SPH-L900 using XDA Premium 4 mobile app
---------- Post added at 10:11 PM ---------- Previous post was at 10:09 PM ----------
*** EDIT ***
http://forum.xda-developers.com/showthread.php?t=1518768
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
*** EDIT ***
http://forum.xda-developers.com/showthread.php?t=1245892
Sent from my SPH-L900 using XDA Premium 4 mobile app
JGarrido said:
I've tried a few things since then, and the details are a bit fuzzy, but I believe I wound up using PERI (OneclickrecoveryV0.4.2) to install TWRP. Unfortunately the recovery it came with didn't seem to have any ability to interact with the touchscreen (v.2.5.0.0, I think?), and the hardware buttons don't work, so I was stuck.
I managed to pull a compatible recovery from elsewhere (v2.6.3.9), and swapped it out within PERI files so did manage to get it installed, and I can get into recovery mode now and move around, but every time I attempt to install a ROM, I get an assert error - apparently it's trying to identify my tablet as a tf101, instead of a sl101, and so the install fails. I've tried 3 different ROMs, so my guess is the recovery I'm running is what's actually generating the error, so I may have the wrong version installed, as this one appears to be not 100% compatible with a sl101. Now i'm wondering if the backup I was able to perform will even be restorable. I still have access to the working stock install, so all is not lost yet. I could abandon the process now and still have a fully functional tablet, though I've been experiencing some slowdowns lately, and would still like to get another ROM on here to see how it performs by comparison.
As a side note, I've tried using GooManager to assist with the recovery installation, backup process, and ROM download and installation, but the only useful thing I've managed to get it to do for me is reboot into recovery (now that I have it installed), but even that seems hit or miss. I also tried TWRP Manager, but all it does is display a splash screen with their logo, and then display a blank black screen after that, so it was completely useful to me.
Can anyone advise as to a working recovery and ROM combination (including version numbers)? I'd like to stick with CWM, if possible (most familiar with it), but it seems to be more problematic than TWRP, so i'll take anything that works at this point.
Click to expand...
Click to collapse
Did you try this version that was built for the sl101?
https://dl.dropboxusercontent.com/u/47619656/signed_twrp-2.6.3.9_sl101.zip
It's a flashable zip, and if you're not able to do that, you can unzip it and find the twrp.blob inside. The reports I've gotten back is that it works fine for the sl101 and has touch working as expected. As far as ROMs go, I don't know if there any specific for the sl101, other than stock.
JGarrido said:
I've tried a few things since then, and the details are a bit fuzzy, but I believe I wound up using PERI (OneclickrecoveryV0.4.2) to install TWRP. Unfortunately the recovery it came with didn't seem to have any ability to interact with the touchscreen (v.2.5.0.0, I think?), and the hardware buttons don't work, so I was stuck.
I managed to pull a compatible recovery from elsewhere (v2.6.3.9), and swapped it out within PERI files so did manage to get it installed, and I can get into recovery mode now and move around, but every time I attempt to install a ROM, I get an assert error - apparently it's trying to identify my tablet as a tf101, instead of a sl101, and so the install fails. I've tried 3 different ROMs, so my guess is the recovery I'm running is what's actually generating the error, so I may have the wrong version installed, as this one appears to be not 100% compatible with a sl101. Now i'm wondering if the backup I was able to perform will even be restorable. I still have access to the working stock install, so all is not lost yet. I could abandon the process now and still have a fully functional tablet, though I've been experiencing some slowdowns lately, and would still like to get another ROM on here to see how it performs by comparison.
As a side note, I've tried using GooManager to assist with the recovery installation, backup process, and ROM download and installation, but the only useful thing I've managed to get it to do for me is reboot into recovery (now that I have it installed), but even that seems hit or miss. I also tried TWRP Manager, but all it does is display a splash screen with their logo, and then display a blank black screen after that, so it was completely useful to me.
Can anyone advise as to a working recovery and ROM combination (including version numbers)? I'd like to stick with CWM, if possible (most familiar with it), but it seems to be more problematic than TWRP, so i'll take anything that works at this point.
Click to expand...
Click to collapse
Sorry to hear that.. I do not know what could be the source of that "assert" error, but if there is something I did NOT find surfing through the internet, was development on the Slider, therefore if you still have a working stock ROM I'd stick to that one since we have a very unstable array of tools.. As far as I can tell CWM will only mean trouble for the SL101. Since I am not an expert developer do not be discouraged by my advice, but I just warn you that I tried a CWM and TWRP combination that totally killed my tablet ..just so you do not end like me.
As for the slowdown issue, all you can do is pray that TF101 devs put a little effort in releasing a kernel allowing overclocking, as not even that I could find..
Flashing recovery blob
sidneyk said:
Did you try this version that was built for the sl101?
https://dl.dropboxusercontent.com/u/47619656/signed_twrp-2.6.3.9_sl101.zip
It's a flashable zip, and if you're not able to do that, you can unzip it and find the twrp.blob inside. The reports I've gotten back is that it works fine for the sl101 and has touch working as expected. As far as ROMs go, I don't know if there any specific for the sl101, other than stock.
Click to expand...
Click to collapse
Hi @sidneyk
That twrp.blob looks promising, can you elaborate on how to flash it? Do you need adb? If so, never mind
Timberwolfhusky said:
Hi @sidneyk
That twrp.blob looks promising, can you elaborate on how to flash it? Do you need adb? If so, never mind
Click to expand...
Click to collapse
Well, adb is one method, but I was responding to the person who said they were able to swap a blob with peri or something, so I was assuming that person at least had some method that sorta worked. Without adb or apx mode I don't really know a way. Sorry, if I got your hopes up again. Just trying to help. I was looking through nvflash scripts and files earlier to see if I could find a way for you guys, but haven't come up with one yet.
Sent from my TF101 running OmniROM 4.4.2.
It's ok, since you mentioned a blob I tought you may have figured NvFlash out, misunderstanding from my part, apologies..
Please let us know if you find out anything new
Sent from my PC36100 using xda app-developers app
almost same problem as yours.
I have almost the same problem with an SL101. I did have ADB working but after using 1 click installer i ended up with a tablet without adb. APX works but you can't do much with it since it has not been hacked. I wonder if there is any way to get back adb. When I connect the tablet to a pc it now fails to install adb driver. I have tried a whole range of drivers but seems windows will not recognise it.
Timberwolfhusky said:
I had previously posted this as a reply to a different thread, but my problem has gotten out of hand. I need help desperately!:crying:
I'll start from the beginning, and try to be as detailed as possible...
I own the Asus Transformer slider (sl101) ICS 4.0.3
I rooted and all the good stuff using motochopper, everything worked like a charm..
The big trouble arises when I decided to flash CWM recovery through Rom manager.. Since Rom Manager had never failed me before in showing the recoveries for "compatible" devices I decided to give it a shot at the only recovery it "attested" was compatible..The TF101 recovery...
Without further ado, I proceeded to flash that recovery ASSUMING that since both are very similar ASUS products they were compatible in some way(I know total derp failure). To a certain extent that was true, I ended up flashing CWM Recovery 6.0.1.3 and booted it up successfully.
This Is where it got bad.. So I decided to do a simple factory wipe from the recovery, only to find out that the recovery would ALWAYS get stuck on formatting /data...After the disappointment I rebooted the Tab to see if it had worked anyway AFTER being stuck on that "formatting /data"
state..Surprise surprise! BOOT LOOP on the ASUS bootup animation.
Found out the factory wipe(just my luck) had wiped the setting that would have been a life saver, the ADB interface, and no matter how far or how long I waited into the boot animation, ADB was gone.
That being said, naturally every single unbrick tool and file wpuld be useles without adb..So I said to myself, "not to worry, I can flash another recovery from CWM, right?" NO SIR! CWM would throw an error reading "can't mount sdcard" and no matter what I did, flashing zip's was a dead end..
After all that playing around I found that CWM somehow mounted an ADB interface in "recovery" mode, or that is what the "adb devices" command would show. Anywho I tried the "unbricking" tools available...NONE did the trick..
After looking around for hours and previously noticing a "/staging" partition, I stumbled upon a post in Transformer Forums, stating that any .blob file inside the aforementioned partition would be flashed during boot, so I tried to "adb push" using the previously mounted "recovery" adb interface to copy or "push" TWRP recovery blob file to the said partition.....reboot..nothing..CWM still clings to my tab..
Well, I still have the recovery ADB, so there is still hope..Therefore I found an easy flash tool that supposedly flashes TWRP and unbricks the device through adb, this was PERI http://forum.xda-developers.com/show....php?t=1681155
After three reboots in the process of using this tool and for a brief moment, a progress bar appeared in the "Eee Tab" spalsh screen, showing that the recovery was being installed.
THIS IS WHERE HELL BROKE LOOSE...After "flashing" TWRP "successfully" I manually booted the recovery only to find that NOTHING would happen, as if "booting recovery kernel image" just did nothing and proceeded to boot the device normally(which of course did NOT happen).
So then, here I am, NO adb, NO recovery whatsoever, and APX mode has done me no good...I searched and searched, only to find that Wheelie and NvFlasher are useless for the Slider and B90 Serial # devices(which again just my luck)Tried them anyway to NO avail...
I have some pretty solid reasons to be desperate here. So please, if ANYONE could provide ANY helpful tips or information, it would be very, VERY much appreciated.
P.S. I also tried the MicroSD manual OTA Update zip file downloaded from ASUS support, renaming such to EP101_SDUPDATE.zip or update.zip rendered no results, as the white fonts(fastboot?) show "skipping android ota checking"..
Click to expand...
Click to collapse
@Sydneyk Off topic question here....still haven't figured the tablet yet...
anywho since you send your messages from a Note 3 can you clarify if that model you own (sm n900p) is the model with a quad S800? I am seriously considering in acquiring one but I have to make absolutely sure that it is not the "Exynos" model I'm getting...since I screwed my tablet and this EVO is stone age, I realized I needed an upgrade...
As a side note I won't give up on the SL101 for the sake of finally solving the issue for other usssrs that my also experience my same predicament...
Thanks!
Sent from my PC36100 using xda app-developers app
Timberwolfhusky said:
@Sydneyk Off topic question here....still haven't figured the tablet yet...
anywho since you send your messages from a Note 3 can you clarify if that model you own (sm n900p) is the model with a quad S800? I am seriously considering in acquiring one but I have to make absolutely sure that it is not the "Exynos" model I'm getting...since I screwed my tablet and this EVO is stone age, I realized I needed an upgrade...
As a side note I won't give up on the SL101 for the sake of finally solving the issue for other usssrs that my also experience my same predicament...
Thanks!
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
It's a quad core T-Mo US version and a nice, but expensive piece of hardware. It's a SM-N900T.
Sent from my SM-N900T using XDA Premium HD app
Related
I recently purchased a Asus Transformer, and being the android nerd I am I immediately began my rooting. After I rooted it, I began to look up roms and such. I decided to put the revolution HD Tom on it. I booted into recovery, wiped data, wiped cache, wiped dalvic, and than processed to flash the rom it flashed and said rom installed successfully. I rebooted and now nothing. I understand the wait time for boot but its been over 30 mins. I almost possitive its off and bricked. I need help as I only know how to unbrick a moto device. :/
sent from a DROIDX using S.S. 2.2... the best rom for it...
after a little searching I found a program called nvflash, I'm guessing that this is sort of like rsd lite. Ill try it later.
sent from a DROIDX using S.S. 2.2... the best rom for it...
NVFlash is only going to work if you have SBK v1.
Did you check the MD5Sum of the ROM file before flashing?
Sbk v1, what's that? And sorry I'm a noob with this transformer.
sent from a DROIDX using S.S. 2.2... the best rom for it...
It is the Secure Boot Kit of the device.
Look at your TF serial number: if you have B7O, B8O, B9O it should have the new version of SBK (v2). If it's the case, you CAN'T use NVFlash method to unbrick at the moment.
Look at this link to be able to check the SBK version of your TF:
http://forum.xda-developers.com/showthread.php?t=1290503
atothis said:
It is the Secure Boot Kit of the device.
Look at your TF serial number: if you have B7O, B8O, B9O it should have the new version of SBK (v2). If it's the case, you CAN'T use NVFlash method to unbrick at the moment.
Look at this link to be able to check the SBK version of your TF:
http://forum.xda-developers.com/showthread.php?t=1290503
Click to expand...
Click to collapse
Well if I can't turn on the device and I cant tell if its off than how can I get it into the mode asked? If that makes sence.
sent from a DROIDX using S.S. 2.2... the best rom for it...
Have you tried to force turn-off?
If not so, press and hold the power button for 10-20 seconds.
Then try to enter CWM recovery (or to boot normally).
Have you also tried to put it to charge? (Just to see if something happens).
EDIT: Did you eventually checked the serial # (On the box or on the back bottom part of the TF) ? If you have a B6O or lower, you can quite surely use NVFlash.
Tf101 is on the bottom as soon as I leave bdubs ill check to see if I can force it off and than enter recovery.
sent from a DROIDX using S.S. 2.2... the best rom for it...
atothis said:
Have you tried to force turn-off?
If not so, press and hold the power button for 10-20 seconds.
Then try to enter CWM recovery (or to boot normally).
Have you also tried to put it to charge? (Just to see if something happens).
EDIT: Did you eventually checked the serial # (On the box or on the back bottom part of the TF) ? If you have a B6O or lower, you can quite surely use NVFlash.
Click to expand...
Click to collapse
I'm guessing it will say B6O at the end of the serial. O and also what must I do in order to use nvflash, what preparation needs to be done?
sent from a DROIDX using S.S. 2.2... the best rom for it...
At the bottom of your transformer is a sticker if it says b60 you can use nvflash
If you have checked that then just look in the dev thread and you will find all you need about nvflash
Sent from my tf101 using xda premium 1.54Ghz
I tryed to hard reset it, didn't work. :/ I also checked and I have a tf101, B6O. How do I use the nvflash tool?
sent from a DROIDX using S.S. 2.2... the best rom for it...
HaXERxPaYLaY said:
I'm guessing it will say B6O at the end of the serial. O and also what must I do in order to use nvflash, what preparation needs to be done?
sent from a DROIDX using S.S. 2.2... the best rom for it...
Click to expand...
Click to collapse
Actually you need to read the FIRST three letters of the serial.
If it is a B6O, you're lucky
I have a B7O SBKv2, so I didn't used NVFlash, but you can find clear instructions here:
http://forum.xda-developers.com/showthread.php?t=1123429
Here's the general REF thread (MANY useful info, it's a sticky thread in dev section): http://forum.xda-developers.com/showthread.php?t=1044424
Ill try this all tonight and ill let you know what happens. I'm kinda nervous cause I really don't want to have high dollar brick.
sent from a DROIDX using S.S. 2.2... the best rom for it...
I got it to work im posting from it now! Thank you guys!
I have this problem and resolved with super wipe full script ( find in first post of revolution hd rom )
For use it, just download, put in sd card, run it on recovry ( install zip ... )
After wipe, I install revolver rom
Sent from my Transformer TF101
HaXERxPaYLaY said:
I got it to work im posting from it now! Thank you guys!
Click to expand...
Click to collapse
how did you get it working?
Hi everyone,
I have tried to read most of the 92 pages and still have not solved my problem.
The situation is as follows:
- I had a perfectly fine Asus Transformer B40 running Revolver 3.11 ROM with CPU OCed @ 1.6 Panda.test. While I was browsing the web the TF shut off and since then I cannot turn it on properly (boot into the OS).
- after failed attempts to reflash I wanted to get back to stock + unroot.
- I followed the steps from the first post here, I have a US version B40. I downloaded the US latest firmware from the first post and then ran the .bat file. Everything went fine and it restarted.
- then I did just this: hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
Now the problem is more or less the same: I boot up the device, it shows the ASUS logo with the spinning wheel and then it turns off or reboots continuously. Sometimes it gets after the logo to the Select Language or Country screen. Touchscreen works. But then it reboots again. Every time it does that there is also a small hardware click sound.
I have also tried to manually reflash with firmware from Asus website but I still get the Android robot with an exclamation mark inside.
I just got this for Christmas, hope you can help me somehow as I don't know what to do...
Thanks a lot!
Just walked a friend through the downgrade on his B70 over the phone, he is rooted and running PRIME 2.1.1 in less than an hour.
First, get the WW_epad-user(blah blah) 8.6.6.19.zip update (downgrade/update, available in the dev section stickies), be sure it is the 8.6.6.19, not 8.6.5.19. Place the file on your SD card in the root, also make a copy and rename it
EP101_SDUPDATE.zip
(make sure your SD card is FAT32 formatted too, this has caused problems for some I have read). If these files are placed in the root of your external SD card then when booting into recovery mode it *should* find one of these two files and ask to install the 'update'. Once updated, install razorclaw and recoveryinstaller, grab the updated CWM installer with the 8.6.6.21 patch on it, available in the dev section, and then flash your new ROM over this patch (apparently you can't flash the patch over anything but a stock ROM, so if you already have a flashed ROM you need to flash back to stock ROM, search around instructions and files are available on xda).
If when you boot into recovery (vol - and pwr, vol+ on prompt) it doesn't tell you it is installing, give it some time, others have reported that the android/yellow triangle screen is actually good to see and will install updates on this screen even though it isn't notifying you (can't confirm from first hand, but what I have read on this site from other users), if it doesn't though, try rebooting normally, other users have said the update installs from notification bar in stock android OS (this confuses me too..). If recovery mode nor rebooting installs the downgrade, double check that you have the correct files, named correctly..try on another SD card, reformat to FAT32, etc. from what I understand even though it's different for some users there is some good success flashing back to the 8.6.6.19 build from the .21. Good luck, tell us if you fix it and how!
superwipe..
Before you flash revolution, you were supposed to flash superwipe then the rom, if you havent already go do so.
here is my issue.
2 weeks ago, i rooted my phone. all was well. flashed CWM Recovery 5.0.2.1 for my Thunderbolt. I made a backup just before i rooted so that in case ANYTHING went wrong, it would unroot me and fix any problems. So, here i am, backing up apps with Titanium Backup, and it backed up fine. The next thing i did was start to uninstall HTC Bloatware... I knew which ones were the ones i could remove, plus even if i removed the wrong one, i could just restore using my image backup. After removal, the phone instantly ran better. i had over 65% free memory space... This was all well and good, until i rebooted the phone. the instant i rebooted my phone, i was getting the flashing HTC Quietly Brilliant screen. i had done NOTHING to it to cause this. It would alternate from HTC splash to Thunderbolt animation.
So, knowing what was wrong, (UI not loading) i went to recover my image from CWM. that went fine. but things just got worse. After a successful recovery (according to CWM) i rebooted, but to my surprise, now its worse. its stuck at the HTC boot logo. ALL MANNER OF ROMS DO NOT WORK!!! recoveries, new OS, anything, all the same result. AT LEAST with the thunderstick full blown ROM, i can get back to the looping splash screen, but not any further. i DONT KNOW what is wrong but i am hoping one of you mad phone geniuses out there can get my phone working. i tried getting s-off with revolutionary, but it failed because the phone has to be booted up for it to work, and is something i obviously cant do at this point... relocking the phone made things worse too because i unlocked using the HTCdev method.
This is not a boot loop, as it doesnt loop. it just sits there. i have tried every available resource on this, and other sites. i must have read over 1,000 posts in the past week to try and gather what the devil happened to my phone... If its any help, i did accidently delete the settings storage APK file, but a restore should have fixed that. i want to lock up the phone to send it in for repair but i cant gain s-off to flash a new radio with the phone in its current state. i know how to do all if these things but the phone wont let me.
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Does your computer recognize your device?
Sent from my ADR6400L using xda app-developers app
i am nearly pulling my hair out...
smtom said:
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
cyberkeeper1 said:
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
Click to expand...
Click to collapse
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
will this really work??!? lol
trter10 said:
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
Click to expand...
Click to collapse
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
new problem... i think...
cyberkeeper1 said:
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
Click to expand...
Click to collapse
ok. so the download finished fine so far as i know, but now CWM says ITS bad too. i will try again but i cant seem to flash any stock rom no matter if its OTA or pre-OTA from CWM. is there a way to flash a rom from the PC via adb or something?
Ohh! They're not flashed through CWM. They're flashed through hboot. Just rename it to PG05IMG.zip and put on SD card and boot to hboot it will ask you to flash
Sent from my ADR6400L using Tapatalk 2
i will try that. previous hboot flashes always fail. it reads the archive, but never goes to "checking zip". it loads, checks, and then parses. i was successful with my evo shift earlier today, but that thing is ancient compared to my thunderbolt. With the Shift, i was able to gain root AND s-off with an old bootloader and i dont even need a new one.
i wanted to do the same with my bootloader in case another disaster hits because then i can flash whatever RUU i want with s-off. i will make sure the MD5 SUM matches before flashing. i forgot to do that anyhow.
Hboot flash failed. went through the motions of scanning it and it scanned the whole thing and then did nothing. it returned me to Boot Choices. Like Fastboot, recovery, etc... i tried twice. are you absolutely certain that is the shipping firmware that formats the entire phone, and not just updates it? i cant send it to verizon even though they know it was illegal to lock up my phone... Anyhow, i realy need this thing working and i have racked my brain enough to damage it already... lol. if it fails again i will try to redownload it. So far it loads and does NOT ask me to start the update. could be a version issue because it does not complain about anything else.
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
lemew said:
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
yes i have. i cannot do what it asks because it requires my phone to be functional to flash it using hboot. i need a signed copy of an older RUU. hboot doesnt do anything with it. its a valid copy, and i can see all the images and contents in windows and linux, but all i can get hboot to do is read it, then it doesnt ask me to update. i dont know what to do now.
I believe there is a ruu image without hoot download there.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------
Try http://shipped-roms.com/index.php?category=android&model=Mecha
Sent from my ADR6400L using xda app-developers app
ok well i will literally try ALL of the signed images. i will see if hboot will update it.
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
How i fixed my tbolt stuck at the white HTC screen
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
mpcapps said:
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
Click to expand...
Click to collapse
I have read that post you provided probably 100 times its not working for me. flashing a custom rom actually got me past the HTC white screen and into a splash screen loop (Open Mobile). Also, I havent even been able to use the REV tool because my phone is not recognized by it without it being fully functional. you have to be fully booted up for the REV tool to use adb and start the process. thats why i need a signed copy of an older ROM with hboot flashing capability so i can fully restore my phone. i am 100% sure its a corruption issue, but i am out of clues as to how to actually get it to flash over while being s-on. with the evo shift it worked perfectly. it only took me 20 minutes to root, s-off and flash a custom rom. this phone has been a thorn in my side ever since i accepted that STUPID FOTA... i regret not knowing before hand what that OTA was and what it prevented. Now i know, too little / too late.
without s-off, i cant unlock hboot to flash it, and the fastboot mw whatever command failed also because its locked tight.
lemew said:
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
thats what i thought. is there a way to change out that eMMC, or remove it to format it manually? i mean based on the description, its technically external which implies removable.
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
lemew said:
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
too bad i cannot repartition it to allow for more RAM instead of app space. i dont care about app space because i have a 32gb card... lol. i just want that phone to be faster than what it is currently once i finally get it running.
I rooted and installed new roms for my Xoom a long time ago, but recently gave it to my wife because I bought a Surface tablet (boo, hiss, etc.).
She complained because it kept saying there was an update, but every time she tried it, it failed. So I decided to manually update it today and believe I may have bricked it.
I think I flashed the wrong images and now all I get is the M logo and it goes no further. I can still get fastboot support so tried to reflash it but that didn't help.
One other, related or not, issue is that I can get into recovery but it keeps saying it cannot mount my sdcard, so I can't update that way.
ANY help is greatly appreciated at this point.
Thanks,
Paul
webtop said:
I rooted and installed new roms for my Xoom a long time ago, but recently gave it to my wife because I bought a Surface tablet (boo, hiss, etc.).
She complained because it kept saying there was an update, but every time she tried it, it failed. So I decided to manually update it today and believe I may have bricked it.
I think I flashed the wrong images and now all I get is the M logo and it goes no further. I can still get fastboot support so tried to reflash it but that didn't help.
One other, related or not, issue is that I can get into recovery but it keeps saying it cannot mount my sdcard, so I can't update that way.
ANY help is greatly appreciated at this point.
Thanks,
Paul
Click to expand...
Click to collapse
You have the old cwm, it's why it can't mount sdcard. You must update to the newest cwm to be able to flash the newer roms, cm10.1,4.2.
Sent from my Xoom using xda premium
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Get fastboot.exe from the internet somewhere on a computer
Set that up
Download .img file for latest twrp
Enter fastboot mode on the tablet
Using fastboot on the command prompt, flash twrp to the tablet using 'fastboot flash recovery [filename].img' command
Use new recovery to try and do something else
Sent from my Xoom using xda premium
ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.
kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.
I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app
As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.
Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.
Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:
I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app
I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.
I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app
I have the HTC One X with Rogers, it has an unlocked bootloader via HTC Dev, it is S On, and I did not successfully run supercid however I have installed clockwork recovery, and RageXL... Currently my phone is practically unusable, meaning I can't make calls, no wifi, no data, and I can only text (but if I open the app to send a test it crashes)...
My reading tells me that it is the radio and I need a new bootloader as well, however if I type "adb shell" into my terminal my phone restarts... I can't seem to find anybody with a similar problem, so hopefully somebody here can help?
Thanks in advance!
First off I would recommend installing TWRP 2.3.3.1 and reflashing the ROM. If its still not working I would reinstall adb on your computer. If all this doesn't work report back and we'll figure something out.
-Sugardaddy
OK, after trying TWRP a few times (it was a long adventure last night) I'm still running CWM, however my phone is almost completely usable now. That being said, unless I am in recovery mode ADB doesn't seem to recognize my device at all. RageXL is pretty nicely with the exception of no mobile data, but that is because I need a new modem I believe.
Should I put TWRP on instead of CWM to fix my issue with ADB or is it something different going on?
I don't see how changing recover will fix your issues with being able to use adb, but I'd install TWRP anyway, it's recommended to use that instead of CWM on our device.
What exactly happens when you try to use adb? Do you have the correct drivers installed on your pc?
Sent from my EVITA using xda premium
Good point, recovery shouldn't have anything to do with ADB. I'm on a Mac also. Just curious why is TWRP better than CWM?
CWM has always had issues operating correctly on our phone, issues with wiping and flashing. Also, if you're gonna use TWRP, make sure you use version 2.3.3.1 :thumbup:
Also, I have no idea about using adb on a Mac sorry.
Sent from my EVITA using xda premium
The adb issue is resolved now, I had to restart my phone but it worked. Also part of the issue was with a supersu script that included its own version of ADB, that was messing up with the ADB that is on my computer already. Sigh... Well at least it all works (ish).
Thanks!