Related
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
UPDATE 15-06-2011:Bumble-Bee (Apache14) is just as much to thank for this as me! Both of us (from AndroidRoot.Mobi) have worked hard on making this happen! Thanks to Roach for providing the nvflash-ready Prime 1.4 ROM!
UPDATE: The Prime 1.4 linked is European (WW) build! Roach will release 1.5 soon probably and there'll be both WW and US available. I'm planning to write a quick guide on how to root when running stock 3.1 already (it's pretty easy!)! E.g. to stay on full stock and *just* have root
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Awesome! Thanks a lot!!
rayman84 said:
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Click to expand...
Click to collapse
WOW, It's "just like that"? Really that's all what you have to do to unbrick a device? I guess times when flashing roms was dangerous have passed
Great job
Very thanks and keep up the good work!!!
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
atlaswingpasaway said:
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
Click to expand...
Click to collapse
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
combat goofwing said:
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
Click to expand...
Click to collapse
You don't need this your already rooted. This is a easy way to root and it can also revive bricks, custom flash different partitions and who knows what other functions can be done with nvflash.
Sent from my HTC Vision using XDA Premium App
Will this wipe your data partition if using this to get a rooted custom rom on?
seshmaru said:
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
Click to expand...
Click to collapse
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Canadoc said:
Will this wipe your data partition if using this to get a rooted custom rom on?
Click to expand...
Click to collapse
Using the script included it will wipe all user data. But it may be tweaked later.
Sent from my HTC Vision using XDA Premium App
atlaswingpasaway said:
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Click to expand...
Click to collapse
Yes if u want a custom rom with root. No more downgrading firmwares anymore like before
Cannot mount SD card in clockwork mod?
EDIT: Nevermind. I tried a different microsd card and it worked fine. False alarm... Move along... nothing to see here
I used the NVFlash utility to flash Prime 1.4 without a hitch but now that I'm trying to deploy the overclock kernel clockwork mod is not playing nice. I get an error E: Can't mount /sdcard when trying to choose a zip file. My understanding is that /sdcard is not the microsd anyway. How do I resolve this? I already tried reformatting the microsd card on my pc but that didn't solve the issue.
Thanks!
-Matt
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
/Removable/MicroSD/ is the MicroSD card slot on the TF104
/SDCard is the 30gigs on the 32gb NAND
Also check the CWM installed. If it's the old one it erases your sd card and internal card on data wipes. You don't want that.
Sent from my HTC Vision using XDA Premium App
david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
It's /Removable/MicroSD
But I think the key thing here is that /sdcard is whatever the booting process mounts as /sdcard. This is why CWM has no problem listing the zip files for ROMs, etc. as being from the sdcard. It has accessed it through the actual block device which doesn't change. The whole internal sdcard that we see is some trickery that allows us to have access to all the space on our internal memory, but CWM doesn't know or care about that.
Sent from my Transformer TF101 using XDA Premium App
So...
No rooting, and no CWM..
Just use the tools and profit?
It flashes CWM for future flashing fun.
Sent from my HTC Vision using XDA Premium App
i just dont seem to get it.. . so does this give my stock 3.1 root?
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.
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 a Samsung Galaxy S2 Skyrocket (SGH-I727 / AT&T) that I cannot get to connect to a PC after weeks of trying. I have tried to read through hundreds of threads regarding this issue and it seems others have had similar issues but nothing quite like this.
When I connect my phone to a PC, it does charge but Windows XP or Windows 7 will not recognize the phone. Anytime it is connected an error pops up stating "USB Device Not Recognized. One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it."
So to clarify, I have tried the following suggestions from others to troubleshoot and try to narrow down the issue:
1.) I have tried 4 separate USB cables, including the original OEM Samsung brand data cable that came with the phone.
2.) I have tried 3 separate PC's (2 with Windows 7, 1 with Windows XP).
3.) I have installed Samsung Kies on all 3 PCs, uninstalled and reinstalled the program as well as the Samsung Drivers on multiple occasions.
4.) I have done a factory/data reset on the phone twice to see if this was an issue caused by other apps I've downloaded in the past.
5.) I have tried to use USB Debugging/Developer option and then connect the phone to no avail.
6.) I have tried USB Mass Storage option before connecting the phone.
7.) I have tried to connect the phone to a PC in Samsung's default recovery mode and still showed it was not a recognizable device.
8.) I have tried a friend's galaxy S3 on all cables and PC's mentioned above and Kies immediately recognizes her phone.
9.) I have attempted to clean the physical microusb port with a small brush to make sure the contacts were clean and not being blocked by something.
10.)I have done a battery pull and about 20+ phone resets for all above mentioned attempts.
Based on all of these attempts without any success, it seems to me that this being a PHONE hardware issue is highly probable. I've ruled out just about every other scenario and I'm wondering at this point if my phone's Micro USB port is fried somehow.
Has anyone heard of this or is this a reasonable possibility?
I have tried just about everything I can so far, if anyone has any other suggestions or has any information that may confirm my suspicion, please let me know.
This all came about in the past week due to Jelly Bean being finally released by AT&T / Samsung for the Skyrocket and unfortunately, this update only seems to be available via Kies and a direct data cable to a PC. I have tried to go to Settings > About Phone > Software Update > Check for Updates (while connected to Wifi with a full battery) and the phone has told me 3 times over the past 3 days that my current Ice Cream Sandwich v4.0.4 Android is the most current software up to date. I'm guessing they're not planning on releasing Jelly Bean to the Skyrocket via OTA air updates....so now I'm stuck.
Bizarre issue you got there mate!
Sorry to disappoint you, but this isn't the right section for your device.
Please report ur post to the moderators and have it moved here:
http://forum.xda-developers.com/forumdisplay.php?f=1372
Thank you..
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Bizarre issue you got there mate!
Sorry to disappoint you, but this isn't the right section for your device.
Please report ur post to the moderators and have it moved here:
http://forum.xda-developers.com/forumdisplay.php?f=1372
Thank you..
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
you sent him to the i777 forum?
as to op, seems a bad/dead usb port
read this on installing stock firmware even w/a dead usb port http://forum.xda-developers.com/showthread.php?p=29977559#post29977559
vincom said:
you sent him to the i777 forum?
as to op, seems a bad/dead usb port
read this on installing stock firmware even w/a dead usb port http://forum.xda-developers.com/showthread.php?p=29977559#post29977559
Click to expand...
Click to collapse
Wow, thank you so much. This is the first thing I've seen from anyone regarding a possible fix outside of direct USB connection. I sincerely appreciate it!
xyberelite said:
Wow, thank you so much. This is the first thing I've seen from anyone regarding a possible fix outside of direct USB connection. I sincerely appreciate it!
Click to expand...
Click to collapse
You should also try a different computer if you can. It works on my laptop but not my pc. I have no idea why and have tried everything I can think of. Also, use the usb ports on the back of the computer, not the front
Edit: sorry I didn't read your whole post.
Sent from my SAMSUNG-SGH-I727
You should probably hit this.
vincom said:
you sent him to the i777 forum?
as to op, seems a bad/dead usb port
read this on installing stock firmware even w/a dead usb port http://forum.xda-developers.com/showthread.php?p=29977559#post29977559
Click to expand...
Click to collapse
Well after getting into the details on the post, it looks like this is created for a phone that already has a custom recovery such as CWM or TWRP installed. Since I do not have a USB port to use on this phone as of right now, is there any way to install a custom recovery on my phone without using USB?
I did download the stock 4.1.2 Jelly Bean firmware directly on the phone's default directory already and it's sitting there in a zip format. If I'm not able to root and/or install a custom recovery without using a USB cable, would it be possible to install the stock firmware using the default samsung recovery mode?
xyberelite said:
Well after getting into the details on the post, it looks like this is created for a phone that already has a custom recovery such as CWM or TWRP installed. Since I do not have a USB port to use on this phone as of right now, is there any way to install a custom recovery on my phone without using USB?
Click to expand...
Click to collapse
Yes you need to search the skyrocket threads the answer is out there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xyberelite said:
Well after getting into the details on the post, it looks like this is created for a phone that already has a custom recovery such as CWM or TWRP installed. Since I do not have a USB port to use on this phone as of right now, is there any way to install a custom recovery on my phone without using USB?
I did download the stock 4.1.2 Jelly Bean firmware directly on the phone's default directory already and it's sitting there in a zip format. If I'm not able to root and/or install a custom recovery without using a USB cable, would it be possible to install the stock firmware using the default samsung recovery mode?
Click to expand...
Click to collapse
no afaik, but read below
mtdew said:
Yes you need to search the skyrocket threads the answer is out there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
if there is ive never seen it, let us know how, that is how to install a rom/firmware w/out custom recovery and w/a dead usb port
Crap if he's bone stock then no if it were stock rooted he could use dd commands with terminal emulator.
Also nowhere in his description did he ever say he deleted the old drivers from device manager.
Also I'm wondering how you are installing these drivers.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
vincom said:
no afaik, but read below
if there is ive never seen it, let us know how, that is how to install a rom/firmware w/out custom recovery and w/a dead usb port
Click to expand...
Click to collapse
Well I did find this older thread that will supposedly allow me to install CWM and root without using a USB cable or PC. I'm going to try this since you all have confirmed that I'm not able to install a stock firmware/rom using stock recovery.
http://forum.xda-developers.com/showthread.php?t=1501719
Edit - Didn't work, apparently this was for 4.0.3, not 4.0.4.
I'm going to need to figure out how to root and get CWM on my phone just to install Stock Jelly Bean all without using a USB cable. Still no luck so far.
mtdew said:
Crap if he's bone stock then no if it were stock rooted he could use dd commands with terminal emulator.
Also nowhere in his description did he ever say he deleted the old drivers from device manager.
Also I'm wondering how you are installing these drivers.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I initially thought he had cwm/twrp installed
xyberelite said:
Well I did find this older thread that will supposedly allow me to install CWM and root without using a USB cable or PC. I'm going to try this since you all have confirmed that I'm not able to install a stock firmware/rom using stock recovery.
http://forum.xda-developers.com/showthread.php?t=1501719
Edit - Didn't work, apparently this was for 4.0.3, not 4.0.4.
I'm going to need to figure out how to root and get CWM on my phone just to install Stock Jelly Bean all without using a USB cable. Still no luck so far.
Click to expand...
Click to collapse
that's not for our phones, that would of bricked ur device if it had flashed successfully
get ur usb port fixed or try some tips in fixing it in the 1stop sticky
edit: try this http://forum.xda-developers.com/showpost.php?p=34906725&postcount=6
vincom said:
I initially thought he had cwm/twrp installed
that's not for our phones, that would of bricked ur device if it had flashed successfully
get ur usb port fixed or try some tips in fixing it in the 1stop sticky
edit: try this http://forum.xda-developers.com/showpost.php?p=34906725&postcount=6
Click to expand...
Click to collapse
It wouldn't work. Nothing will install in Android System Recovery <3e>. Everything I tried still came back with Signature Verification Failed.
I also tried lifting the "tongue" inside the usb port on the phone several times previously and that didn't work either. I must assume at this point the usb daughterboard or something inside is messed up.
Since stock recovery can't install any type of files and I can't connect the phone to a PC in any way and my phone is 100% stock without root or any custom recovery, I can only imagine I'm stuck in this situation. I have yet to see any solutions for getting root or installing CWM without having a USB connection that works. Unless I can do either of those things, it looks like I'm SOL for updating from ICS to JB.
If they had only made Jelly Bean an Over the Air update, none of this would be a problem really.
xyberelite said:
It wouldn't work. Nothing will install in Android System Recovery <3e>. Everything I tried still came back with Signature Verification Failed.
I also tried lifting the "tongue" inside the usb port on the phone several times previously and that didn't work either. I must assume at this point the usb daughterboard or something inside is messed up.
Since stock recovery can't install any type of files and I can't connect the phone to a PC in any way and my phone is 100% stock without root or any custom recovery, I can only imagine I'm stuck in this situation. I have yet to see any solutions for getting root or installing CWM without having a USB connection that works. Unless I can do either of those things, it looks like I'm SOL for updating from ICS to JB.
If they had only made Jelly Bean an Over the Air update, none of this would be a problem really.
Click to expand...
Click to collapse
Too dangerous the ota bricks tons of people when they do it I can only assume at&t is tired of it and opts for kies only. Also you could buy a daughter board and replace it. It's a relatively easy fix.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Too dangerous the ota bricks tons of people when they do it I can only assume at&t is tired of it and opts for kies only. Also you could buy a daughter board and replace it. It's a relatively easy fix.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So .... lesson learned here is that you CANNOT root a phone or install any custom recoveries such as CWM or TWRP without having a working USB connection. As a result, you CANNOT install any updates, stock firmwares and especially custom roms without the above.
Only option at this point is to order the replacement part for the USB port on the phone or to purchase a new phone (if it's outside of the warranty period).
xyberelite said:
So .... lesson learned here is that you CANNOT root a phone or install any custom recoveries such as CWM or TWRP without having a working USB connection. As a result, you CANNOT install any updates, stock firmwares and especially custom roms without the above.
Only option at this point is to order the replacement part for the USB port on the phone or to purchase a new phone (if it's outside of the warranty period).
Click to expand...
Click to collapse
No you need USB to root that's it technically. If you have root you can install a recovery IMG without a computer using a terminal emulator and dd commands.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thanks for the update. Hopefully it will help others:thumbup:
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
mtdew said:
No you need USB to root that's it technically. If you have root you can install a recovery IMG without a computer using a terminal emulator and dd commands.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
yes and no, its the chicken and the egg kind of question, for the sr to get root u need to flash the su files, but u need to have a custom recovery to flash the su files. is there a way to get the su files onto the sr w/out a custom recovery? I haven't seen one yet unless there was a oneclick method which I never used
vincom said:
yes and no, its the chicken and the egg kind of question, for the sr to get root u need to flash the su files, but u need to have a custom recovery to flash the su files. is there a way to get the su files onto the sr w/out a custom recovery? I haven't seen one yet unless there was a oneclick method which I never used
Click to expand...
Click to collapse
I used a one click waaaaaaaaay back when the phone was released probably wasn't supported lol but this was long ago on 2.3.5.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
I used a one click waaaaaaaaay back when the phone was released probably wasn't supported lol but this was long ago on 2.3.5.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
There is no one click available for 4.x forward.
I am wondering, however, if something like this would work:
http://forum.xda-developers.com/showthread.php?t=1877270
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