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
Related
ok so i rooted my xoom the other day flashed hammer head 2.1. restored my tablet to stock rooted rom buwhen i did i have now found a way to lock my device. i can boot up and have my su icon available to me however i cannot gain root access even through adb it tells me the file system is read only. so i figured i some how unrooted the device and proceeded to begin the root process for honeycomb. however when trying to push su over to the tablet it tells me the file failed to transfer because the file system is read only what do i do now? Any help would be appreciated.
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
your a noob mate seriously... these board are full of people like you... 1.. download the stock images from
http://developer.motorola.com/products/software/MZ604_HWI69.zip/
if your device is a wifi only and then push the files with fastboot...
ie.. unzip the folder into where the adb fastboot exe are
1. fastboot flash system system.img
2. fastboot flash boot boot.img
3. fastboot flash user user.img
4. fastboot flash recovery recovery.img (as you obviously cant handle root..)
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not talking mounting in cwm here bud
Get to fastboot mode not android recovery same process power plus vol down
Then flash the files not push as mounting in cwm only put the files on sd card not flashing it outright from what your reply was
I was a noob once and soft bricked everything and yet i read and read and fixed stuff myself through searching.. Cuz ultimately if its bricked what do u have to lose then ey lol just find and try everything cant make a worse paperweight than one u may already have eh
But get to fastboot not cwm then flash the files like i said and it will almost certainly work
Sent from my HTC Sensation 4G using XDA Premium App
Thats my other problem my sd card slot isnt wrkn that was my initial instinct. If i try to flash to the sd card it says no directory found. Ive used 3 different sd cards and get the same message. Im really thinkin i got a bad sd slot even when it was rooted and running i had issues with the sd card not wrking. I had several back ups on it when it did wrk and those dissappeared as well. I bought the xoom soley because of the sd card slot was pretty much going to be my saving grace when doing back ups if i ever messed up. I tried wrking it in fastboot as well if i try to flash to the system its read only. If i flash to the sd card directory not found. I know these questions are irritating to more savy individuals and i looked around trust me the last thing i like to do is say der i dun broke it i need an adult. Im just makin sure i didnt over look something more savy ppl know about. I honestly think its bricked at this point. Ive tried what you said and any other way i can think of but i alway get some kind of error.
Sent from my ADR6400L using XDA Premium App
Sent from my ADR6400L using XDA Premium App
What version of clockwork mod recovery are you using?
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would use this recovery instead of 4.0.0.2.
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
you needed to flash the recovery with FASTBOOT.. not adb push chmod stuff; much easier and the process works
read the top post again.. get the recovery.img file (the v3 one the other fellow told you to grab)
1. hold the volume down button and the power button... some text will come on up the top about fasboot protocol and then
2. leave it plugged in to your computer and DONT TOUCH THE XOOM...
3. get your cmd.exe prompt window out and navigate to where your adb.exe AND fastboot.exe files are (should be tools or platform-tools...)
4. Place the recovery.img file into the explorer window where the adb.exe and fastboot.exe both are.... (this should be there as u keep trying to use adb commands but do it again to make sure)
5. type fastboot flash recovery recovery.img
thats the recovery.img flashed...
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Well, there's your answer. You did not successfully unlock.
Glad that you learned some useful things.
flying honey comb on xoom mz601
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
aKolp2010 said:
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
Click to expand...
Click to collapse
You should open a new thread with your issue. Seems the OP in this one has fixed his issues by replacing his Xoom. You'll get better attention by creating a new thread in this forum.
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Well u do have APX mode... is there a day to do something with that?
I7
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
krhainos said:
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Click to expand...
Click to collapse
the bold part is where I can really use some help!!!!
have a tf300t, neither unlocked nor rooted atm.... I never got an OTA after purchase, always had to manually download zip and update, i cannot even unlock the damn device!!!! some unknown network error issue, even tough m fully connected ! its begining to irritate me to the core that anyone asking me advice on what to buy , i say straight up that if its asus it will be crap don't buy it!
i can really use some help regarding this.... it looks like some serial number issue..... :'(
ASUS Rep HELP me please!
Paschalis said:
I7
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
I've been trying to figure this out. But so far nothing. I've tried flashing cm10 images in fastboot. I built a recovery and used it to try and go back to stock but it give me a mismatch error. I tried flashing cm10 in recovery and everything takes me back to asus screen. Any other ideas I could try?
I would love to be able to use my tablet again.
darthvince said:
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
Click to expand...
Click to collapse
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Paschalis said:
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
krhainos said:
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
Click to expand...
Click to collapse
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Drgravy said:
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Click to expand...
Click to collapse
I have a TWRP version for someone to test here: http://forum.xda-developers.com/showthread.php?t=1843694
Flash with fastboot.
I created an RMA request with Asus, the fellow on the phone says it's bewteen $87 to $100 to repair the OS on a device with an unlocked bootloader. This excludes the cost of you shipping Asus the tablet. However, it includes the cost of labor, diagnostic, and shipping back to you.
For those of you weighing your options, there's one answer.
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Rompf said:
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Click to expand...
Click to collapse
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
TF300T in repair in Texas as well...
krhainos said:
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
Click to expand...
Click to collapse
My TF300T is in Grapevine TX having the same exact thing done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
bjanice44 said:
My TF300T is in Grapevine TX having the same exact hting done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
Click to expand...
Click to collapse
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
krhainos said:
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
Click to expand...
Click to collapse
Thanks
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What I understood is that's a partitioning difference on JB... Bricked mine too, more and more showing up on these boards... I guess the more issues will show up, the bigger the chance we can have someone fix them (Not me, that's for sure )
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
i recently tried to install jellybean but the rom did not work on nexus s, i stupidly removed the only working rom from my 'sd' card and now my phone only boots into a black screen, i have tried to put a known working rom on my phone but every pc i try to connect my phone to says the device has malfunctioned and windows cannot install software. i have tried to use adb but that also cannot find my device. am i looking at getting another nexus with a broken screen and using my working screen to gain a decent phone back or am i missing a vital programme that will fix my utter cockup? thanks in advance
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i am only famililar with adb to the point of rooting, i have tried to download the drivers but only can see .dll files in the driver folders no option to install said drivers. i can get into power and vol up if that is fastboot?? the problem been is i installed a rom which was meant for the nexus s and i didnt read all comments and later found out it does not work with the nexus. i now cannot access the sd storage to put a working rom onto it . when i open cmd and type adb shell it says device not found. brains ready to explode right now. any help on adb is greatly appriciated
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i do not know how to flash factory images, im am very much a noob to rooted phones and playing with software.
i can get into fastboot and at the bottom it says
usb control init
usb control init end
top says fastboot mode
product name herring
hw version rev 11
bootloader version i9020xxka3
baseband version i9020xxkd1
carier info eur
ser 33304eb5103500ec
lock state unlocked
my laptop does not recognise the phone so i dont know how to flash a factory image. this is the cmd sequence i get
adb shell
error device not found
tried mounting sd card and data but no joy
also tried mounting usb storage.
all i get is device has malfunctioned and will not run
tried downloading google usb drivers and samsung drivers all to no avail.
fingers crossed you can tell me something i dont know as i really cant afford to buy a new phone
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
much appriciated and i hope you can too. thank you thank you thanks you
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
FirePoncho86 said:
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
Click to expand...
Click to collapse
still adb cannot find device.......... any links for known drivers for nexus s on win 7 64 bit?
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
reinsalled sdk tools, still phone not recognised by laptop. gonna try get a cheaper android and flog this one on ebay as someone else might know how to repair it. thank you for your time and help but it appears its all in vain......... damn stupid phone!
[deleted]
Rodya234 said:
the phone is probably fine if you can get into fast boot.
Click to expand...
Click to collapse
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i wish someone could just see this, pdanet asks me to connect my phone to finnish installing the drivers, problem is the phone is NOT RECOGNISED i know exactly what you are all saying to do but my phone will not connect at all. more than happy to post it to one of you guys on here to fix but like i said ive tried everything and have pulled nearly all my hair out in the process
Samsung repair? I know what you're talking about, it happened to me, I was completely bricked, all I could so was send it to Samsung repair..
Sent from my Nexus S using xda app-developers app
Damn, if only you could get it recognized you'd probably be able to flash custom recovery through fastboot and I guess you'd be able to install from sd without data loss.
Sent from my Nexus S
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
cubaniche1 said:
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
Click to expand...
Click to collapse
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
jimpmc said:
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
Click to expand...
Click to collapse
Hey thanks for the reply! Actually, no I was not installing 4.2. I would like to install a newer version of twrp but I cant do anything in twrp because it says its encrypted. I did read that other thread but all the options given are not available to me. I cant get to fastboot.
BUT heres an update:
I got the PC to recognize my device as a Transformer. But I couldn't get the naked drivers nor the newer Asus drivers to work. So I modified the .ini file for both the MTP install and USB driver install to include the Hardware ID shown in windows under device manager properties for the device. Basically I modded the .ini so that it also looks for the device ID, then saved and had windows look at the folder I gain to install the driver and this time is installed. So now I am going to try to use a fastboot command....Ill update if this works. Otherwise I may need to try adb and Im a total newb at adb...
UPDATE:
Got the driver installed but 2 issues:
1: Device manager says Device Cannot Start
2: I cant get recovery menu to show. Tablet goes right into TWRP recovery after looping through the ASUS boot screen twice.
I am stumped. I don't want to give up but I think I may have to
UPDATE
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
cubaniche1 said:
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
Click to expand...
Click to collapse
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Nexus 10 has it's drawbacks too, I love my TF300T.
UPDATE:
Installed new mainboard and got her back up and running quickly. Already updated to 4.2.1. I like it. Well done ASUS!
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Lol. I love my TF300T. Sure, i can buy a better tablet but I would also have to spend a lot more money. I've only got $299 invested in my 32gb tablet plus $49 in my dock. I'm a happy camper. My tablet , when connected to the dock, will last almost twice as long as the Nexus on one charge. I can also keep using the tablet while the dock is charging. I really never even need to put the tablet itself into the charger. You can't do that with the more expensive Nexus 10.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
klownin5643 said:
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Have you added the patch yet? This will allow TWRP to pick up your sd card.
I tried flashing the patched one via fastboot but it did not seem to take. Its still encrypted. I'm thinking its not flashing properly. I'm not the only one having this issue. Hopefully I can just wait it out till a fix is found. I'm afriad of screwing it up to where its completely unuseable.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
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