installed custom rom, now adb shell causes a restar?!? - AT&T, Rogers HTC One X, Telstra One XL

installed custom rom, now adb shell causes a restar?!? - AT&T, Rogers HTC One X, Telstra One XL

I have the HTC One X with Rogers, it has an unlocked bootloader via HTC Dev, it is S On, and I did not successfully run supercid however I have installed clockwork recovery, and RageXL... Currently my phone is practically unusable, meaning I can't make calls, no wifi, no data, and I can only text (but if I open the app to send a test it crashes)...
My reading tells me that it is the radio and I need a new bootloader as well, however if I type "adb shell" into my terminal my phone restarts... I can't seem to find anybody with a similar problem, so hopefully somebody here can help?
Thanks in advance!

First off I would recommend installing TWRP 2.3.3.1 and reflashing the ROM. If its still not working I would reinstall adb on your computer. If all this doesn't work report back and we'll figure something out.
-Sugardaddy

OK, after trying TWRP a few times (it was a long adventure last night) I'm still running CWM, however my phone is almost completely usable now. That being said, unless I am in recovery mode ADB doesn't seem to recognize my device at all. RageXL is pretty nicely with the exception of no mobile data, but that is because I need a new modem I believe.
Should I put TWRP on instead of CWM to fix my issue with ADB or is it something different going on?

I don't see how changing recover will fix your issues with being able to use adb, but I'd install TWRP anyway, it's recommended to use that instead of CWM on our device.
What exactly happens when you try to use adb? Do you have the correct drivers installed on your pc?
Sent from my EVITA using xda premium

Good point, recovery shouldn't have anything to do with ADB. I'm on a Mac also. Just curious why is TWRP better than CWM?

CWM has always had issues operating correctly on our phone, issues with wiping and flashing. Also, if you're gonna use TWRP, make sure you use version 2.3.3.1 :thumbup:
Also, I have no idea about using adb on a Mac sorry.
Sent from my EVITA using xda premium

The adb issue is resolved now, I had to restart my phone but it worked. Also part of the issue was with a supersu script that included its own version of ADB, that was messing up with the ADB that is on my computer already. Sigh... Well at least it all works (ish).
Thanks!

Related

[Q] Bricked??

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

[Q] screwed something while installing cromi4.0 need some direction

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

[Q] Need some help/info please (Installing CM10)

I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks

jessepatty said:
I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks
Click to expand...
Click to collapse
What hboot? You may have to flash boot image separately in adb or s-off.

Venomtester said:
What hboot? You may have to flash boot image separately in adb or s-off.
Click to expand...
Click to collapse
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply

jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
On 1.14 the boot image needs to be flashed separately. Flash from fastboot..
Fastboot flash boot boot.img
The boot image is inside the Rom.zip your flashing. Keep a copy of the Rom on pc and extract files with winzip or whatever you like to use. But boot.img in adb folder and type the command, reboot and it should boot.
S-off can be done but only on a sense based Rom like viperXL.
Also read the stickies... They are there for a reason..
Sent from my HTC One X using xda app-developers app

This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app

jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2136172

exad said:
This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Well that explains why I was having issues on cm10.
Sent from my HTC One X using xda app-developers app

Make sure you're using the cm 10 for one xl (evita) and not the one x.
http://wiki.cyanogenmod.org/w/Evita_Info

I'll check out the links, thanks.
I can see allot has changed since December when I last messed with the phone. Back in December Clockwork recovery wasn't supported on the ATT version of the HOX. I see it now is in a touch version.

apparently I am doing something wrong as I keep getting the same indefinite CM boot logo and can't get past it. It appears I do not fully understand the process to side load the rom.
With that said, I restored it from a backup and I guess I'll just wait until I can confidently install a rom. This phone is so much different then my previous phones and tabs in regards to how it was unlocked and the install of different roms. I didn't have any problem figuring those out but this one has more steps involved which is aiding to my confusion. Maybe I'll find a step by step for my Hboot that I can follow, in the meantime I'll just keep having to look for free wifi for my tablet while I'm out and about.
You'd think there would be an easier way to enable the wifi hotspot on the phone.... LoL
Thanks for the info guys.....truly appreciated.

Try this...
http://code.google.com/p/android-wifi-tether/
Sent from my HTC One X using xda app-developers app

[Q] Not getting past HTC screen

I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!

I would run the 3.18 RUU (which you can do in fastboot).

Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.

I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?

So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium

Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app

I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium

Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477

I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium

Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.

You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium

Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm

[Q] Asus Slider SL101 Brick Redefined.

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

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

Database Info

welcome