Related
:crying: please somebody help me, im desperate, my dad just bought me the htc one x at&t for a gift after my galaxy s 2 got stolen a while back, i had previous exerience rooting, unlocking, and modding basic stuff, the only thing i didnt like about the phone was the multitasking button instead of a menu button, so i rooted it and unlocked the bootloader using the method on onexroot.com and it all worked and i installed twrp recovery, but when i flashed the button remap (cant remember which one) it now gets stuck at the one x screen, i figured this wasnt a problem and i could just download another rom and flash it, but from recovery usb wont moun it get and error something like
something about the sdcard
checking partitions
E: cant mount sd card
E: failed to open lunfile (doesnt exist)
i might be messing up but i am unable to get it to appear in adb always says device not found
am i screwed? am i stuck with a broken rom that cant be fixed?
Please help, it will mean the world to me
Uh read up on ODIN. I used it to get my friends SGS out of a soft brick. I'm not sure if it's for the one x though. What it does is after you put your phone into recovery mode or force pushes a ROM to the SD card then flashes it. Also try googling a tool to force it into recovery. ODIN might I'm not too sure though.
Sent from my HTC One X using XDA
Can you load into the bootloader..?
<Hold power button for ~10 seconds until the buttons flash at the bottom>
<Once its off, hold the power button and the Volume Down [NOT UP = Very bad]>
That should load up the bootloader. Then you can attempt to go into the recovery again OR reinstall it through bootloader.
Now if that doesn't work, You can attempt running the 1.85 RUU from your computer. It <might> overwrite all existing partitions and create a solid and fresh foundation for re-rooting and all.
And to answer your question if you're screwed, in my experience it is almost never an issue to get your phone out of a soft brick as long as you can access some sort of recovery.
Sent from my HTC One X using XDA
heres the rundown
bootloader - yes
recovery - yes
adb - no
fastboot - yes
mount storage - no (makes recovery kinda useless)
i sure hope im not screwed, but since i cant find a way to get a clean rom on the phone i dont see a way to fix it, odin is strictly samsung sadly, and i know nothing about ruu, i dont care about root or anything anymore i just want my phone to work so whatever it takes
Ok, I wasnt sure about ODIN. Try an RUU. Basically an RUU is an .exe or executable file that is almost completely automated that flashes the complete package (Rom, radio, kernel). It might not work depending on what you have installed on windows (drivers and such). You might have to uninstall HTC drivers & sync and try again if that doesn't work install the drivers only then rerun the RUU. RUU is your best bet now. Download one and start the exe. Remember if you're on Mac OSX or linux you're going to have to use a Virtual machine or windows emulator to run the RUU
Sent from my HTC One X using XDA
Pm me if you need further help
Sent from my HTC One X using XDA
i have my mac dualbooted with windows 8 consumer preview, interestingly fastboot doesnt work on the windows end but it does on a mac, im gunna assume i did more than one thing wrong when i previously tried (failed to detect device) to ruu it, where do i get the ruu, where do i get the drivers, and if i use a virtual machine do i need the drivers?
your help is much appreciated
Mac OSX is not the right platform to be using nor is windows 8 (because it is unproven and still in beta). I would recommend using a fresh installation. If you have a windows 7 .ISO you can install it and use it for 30 days before they lock you out with out a key.
Here is a helpful tool to install it as fast as possible VIA USB (provided you have a >4GB drive) http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool
If you are running Mac OSX here is an XDA developers guide for linux (Mac OSX is based off of Free BSD a linux distribution) by Jeepfreak. The process will differ some but not a lot.
Here it is....
http://forum.xda-developers.com/showthread.php?t=1668156
I want to emphasize NOT using Windows 8... It is unproven Beta software....
i have a computer i can use, it has vista, but i would need to go where i can get wifi and know the exact files i need to download as i have a horribly slow connection off a mifi card an am pushing my cap as it is, if you could tell me exactly what to download and run i would be increadibly greatful
http://forum.xda-developers.com/showthread.php?t=1649658 This is still rootable
or
http://forum.xda-developers.com/showthread.php?t=1644338 This is the RUU the phone likely shipped with
Transfer the RUU's to your Vista comp using a USB drive.
Make sure you don't have HTC Sync or if you do it is not running in the background.
ok so i download the ruu, got that, i think i have the android sdk on that computer, will that cover any drivers i need? and for the ruu what to i have to do on the phone end?
i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?
Shouldn't make a difference.... And i would try running the RUU first then download the necessary drivers if that doesn't work...
Jtn.Siren said:
i ran "fastboot getvar version-main" and it returned "version-main: 1.73.502.1" will the difference between .502 vs .502.1 make a differnece?
Click to expand...
Click to collapse
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium
thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this
dkirchik said:
The .1 is for att. But you'll want to run the ruu in fast boot that's either the same version or a higher version like 1.85.502.1.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes but if he trys to root it all bets are off unless he did superCID. I would recommend the first RUU I posted
---------- Post added at 12:24 PM ---------- Previous post was at 12:22 PM ----------
Jtn.Siren said:
thank you so much thus far, as a matter a fact i already have the 502.1 downloaded, could you please explain to me any drivers, files, and commands i will need to execute this
Click to expand...
Click to collapse
The drivers you can get off of htc's website under ATT ONE X, or just search XDA for them...
You do not need any commands to run an RUU. Like I said it is completely automated...
and what mode on the phone off, bootloader, fastboot?
Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Try Bootloader then Recovery. It usually does it for you though if you were booted into a ROM.
Jtn.Siren said:
and what mode on the phone off, bootloader, fastboot?
Click to expand...
Click to collapse
Irish has it right and fastboot make sure the fasboot USB is there. Then open and run the RUU and you're golden.
Sent from my HTC One X using xda premium
This thread is just to direct all the noobs into the right direction, related to root and flash new roms in the Inspire 4G.
[*]Rooting and reverting to stock
Due to the retirement of the Hack Kit, rooting methods have been reduced to:
http://forum.xda-developers.com/showthread.php?t=2168500
or if you are skilled in using adb and fastboot commands:
http://tau.shadowchild.nl/attn1/?cat=6
If you are still stuck and want to revert your phone back to out of the box, then use Marsdta's Guide:
http://forum.xda-developers.com/showthread.php?t=1396229
or Gene Poole's Tool (that will revert also S-OFF):
http://forum.xda-developers.com/showthread.php?t=1208507
[*]Flashing a Custom Rom
To flash a custom rom you need to be rooted and S-OFF (if u used the Hack Kit) or have and unlocked bootloader using HTCDEV tool (wich I don't suggest)
Once u are S-OFF and have CWM or some other custom recovery installed (I personally prefer 4ext) you have to follow these steps (read the dev's thread about particularities. This is just a general guide on how to do it):
Download the custom rom .zip file and put it in your sdcard. Make sure that u check md5sum first just to avoid bootloops.
Reboot phone in recovery. There are many ways to do that, the first can be using Rom Manager (I don't suggest using it for anything else but that) and choosing reboot in recovery option. The second way is to boot in bootloader (press power down and reboot choosing hboot) or just turn phone off and power it up pressing power and volume down. And the last is to use adb commands. Plug the phone as charge only with usb debugging on, open a cmd as admin or terminal as root in your PC and then type adb reboot recovery.
Once in recovery, you need to do a full wipe (wipe data / factory reset and wipe cache + dalvik cache). You can also format some other partitions such as data and system, but the full wipe will work.
When full wipe is finished, go to flash zip from sdcard option, choose zip file and then flash that file.
Reboot the phone once it has finished flashing and wait for the device to fully reboot. The first boot will take a while (probably longer than usual) so don't get scared.
If you flashed a CM based rom, you need to flash google apps separately as well, so find the gapps file corresponding to your rom and flash it in the same manner as above described.
Trouble Shooting
Bootloops: If your phone repeats over and over the bootanimation, don't panic, you are not bricked. Something must have gotten wrong but you can reboot in recovery and re flash the rom as previously described. If bootloop is still there, then try downloading the zip again or choose a diffrent rom.
Factory Reset: If you factory reset the phone and you are not stock, then the phone won't have a rom...you will get stuck in the splash screen (white screen with the green HTC). Just do as described above, get a rom to the sdcard and then flash it. You are not bricked, you are just stuck
Well, this was just to try to point you in the right direction. If you think that I missed something, feel free to tell me and will add it to the OP.....Salud! :good:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Teichopsia said:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, let's hope that people find it usefull...
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Teichopsia said:
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Click to expand...
Click to collapse
hahaha...ummmm you shouldn't have problems. Just install SDK and apk multi tool in the SDK>tools folder or somewhere else. Then from command prompt you should be able to run the commands for the apk multi tool. I use the apktool and I have no problem at all. The main thing is to have adb installed...but there's no need to have the phone plugged to use the apk tool.
In the case of your device, make sure that u have the HTC drivers installed, if you have HTC Sync, you should have them...to try that just plug the phone as charge only, make sure that usb debugging is on and then open a cmd as admin and type adb devices...you should see your HTCserialnumber....
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Teichopsia said:
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Click to expand...
Click to collapse
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
glevitan said:
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
Click to expand...
Click to collapse
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Teichopsia said:
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Click to expand...
Click to collapse
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
glevitan said:
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
Click to expand...
Click to collapse
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Teichopsia said:
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Click to expand...
Click to collapse
AHH I was talking about Adamsoutler´s tutorial in XDA TV. He explains how to set SDK and develop APKs....it is awesome!..look at the XDA TV thread.
Bump.
Sent from a dream.
not able to go back to stock
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
krjkinan said:
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
Click to expand...
Click to collapse
RUUs can not be flashed with an unlocked bootloader. Relock it first, then run the RUU.
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
romanvaldezo said:
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This post is no longer timely. The tool it refers to has been retired. You can no longer get S-Off, but you can unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=2169515.
hey
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Hey, not being mean, but did you read the post right above yours...? Or anything in the Desire HD forums, which is the same phone and is more populated?
rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Then are not reading the OP. You have all the information neeeded in there...if your first post in here Is to whine, then you have not Read the rules or understand the spirit of xda.
Follow the instructions And You will be fine, if You don't Get them take time To learn. Nobody Is going To do your homework.
I just recently rooted my inspire it took some time reading and a few attempts to get it down. But after my homework and grasping the concept it was fairly easy.
Sent from my Desire HD using xda app-developers app
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
you are lucky to have white screen
You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium
xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.
vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...
xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.
can anyone please help
Where can I get stock recovery, stock boot for the phone?
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^
thanks for the reply, however ur link is broken.
And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??
Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though
xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up
I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app
Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.
Thanks to XDA Member noobfordroid we now have the original Boot.img and Recovery.img files that we can use to further our development for this great phone. I plan on taking a better look at them later today, but until then you all are free to check them out! noobfordroid would of posted himself but he doesn't have enough posts to post a link yet.
BOOT IMG
https://www.dropbox.com/s/gq3d442q8hendyp/boot.img
RECOVERY IMG
https://www.dropbox.com/s/k49ll0mjerj84xi/recovery.img
jSterling said:
Thanks to XDA Member noobfordroid we now have the original Boot.img and Recovery.img files that we can use to further our development for this great phone. I plan on taking a better look at them later today, but until then you all are free to check them out! noobfordroid would of posted himself but he doesn't have enough posts to post a link yet.
BOOT IMG
https://www.dropbox.com/s/gq3d442q8hendyp/boot.img
RECOVERY IMG
https://www.dropbox.com/s/k49ll0mjerj84xi/recovery.img
Click to expand...
Click to collapse
awesome i will work on a cwm port ! rite now! i should have it by the end of the week now it would be on the rest of the community on how to flash it as im a noob at recoveries
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
jSterling said:
Thanks to XDA Member noobfordroid we now have the original Boot.img and Recovery.img files that we can use to further our development for this great phone. I plan on taking a better look at them later today, but until then you all are free to check them out! noobfordroid would of posted himself but he doesn't have enough posts to post a link yet.
BOOT IMG
https://www.dropbox.com/s/gq3d442q8hendyp/boot.img
RECOVERY IMG
https://www.dropbox.com/s/k49ll0mjerj84xi/recovery.img
Click to expand...
Click to collapse
if im not mistaken cant we just do this ? http://android-dls.com/wiki/index.php?title=Build_a_custom_recovery_image now that we have the image
cwm recovery
atadres said:
awesome i will work on a cwm port ! rite now! i should have it by the end of the week now it would be on the rest of the community on how to flash it as im a noob at recoveries
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
if im not mistaken cant we just do this ? http://android-dls.com/wiki/index.php?title=Build_a_custom_recovery_image now that we have the image
Click to expand...
Click to collapse
I ported the cwm recovery and tried to push it to the phone but it is giving an error.
[email protected]:/home/shyamalapati/android/out/target/product/p8010# fastboot flash recovery recovery.img
sending 'recovery' (6904 KB)...
OKAY [ 1.707s]
writing 'recovery'...
FAILED (remote: Not Support !!)
finished. total time: 1.713s
fails to write smh have u tried to manualy write the recovery image using root explorer on the phone just replace the file in the directory ?
I'm going to have to take a look when I get to my mother in laws. Has anyone tried asking a developer for the Pantech Burst? There may be a simple solution to the issue that we are overlooking.
Sent from my PantechP8010 using Tapatalk 2
EDIT: Also, maybe the recovery partition has a type of lock? Similar to S-ON maybe? I'm going to ask some Pantech Burst developers to see what they have to say.
From doing a few searches with the error it seems to come up often in Pantech phones (other brands as well). It could be the version of CWM or it could just be a locked bootloader issue, or just a bootloader issue. I'm not sure myself but I'm getting my netbook set up with Mint and ditching the VM so I can find out myself.
Sent from my PantechP8010 using Tapatalk 2
EDIT: My VM is up and running now and I'm going to explore. From what I've gathered so far we need to unlock the bootloader to be able to flash anything to the partitions, this can be done with "fastboot oem unlock" I don't know if that command is going to be that easy but I'm going to check it out! If that fails then were going to need to tackle the bootloader first, also for the recovery, Rootzwiki has been a great source, and they have a tutorial for everything we are looking into, there is a command but I can't remember it right now in fastboot that allows us to boot partitions without them effecting the phone. We should try booting the recovery to see if it works, if it works we may need to flash something in the recovery to unlock the bootloader. I might be completely wrong but hopefully the unlock command works.
jSterling said:
From doing a few searches with the error it seems to come up often in Pantech phones (other brands as well). It could be the version of CWM or it could just be a locked bootloader issue, or just a bootloader issue. I'm not sure myself but I'm getting my netbook set up with Mint and ditching the VM so I can find out myself.
Sent from my PantechP8010 using Tapatalk 2
EDIT: My VM is up and running now and I'm going to explore. From what I've gathered so far we need to unlock the bootloader to be able to flash anything to the partitions, this can be done with "fastboot oem unlock" I don't know if that command is going to be that easy but I'm going to check it out! If that fails then were going to need to tackle the bootloader first, also for the recovery, Rootzwiki has been a great source, and they have a tutorial for everything we are looking into, there is a command but I can't remember it right now in fastboot that allows us to boot partitions without them effecting the phone. We should try booting the recovery to see if it works, if it works we may need to flash something in the recovery to unlock the bootloader. I might be completely wrong but hopefully the unlock command works.
Click to expand...
Click to collapse
yeah sounds right youve had an evo before idk when but if ur one of the early users of the froyo root method we had to unlock a bootloader using a certain comand in adb to be able to downgrade to an earlier 2.2 that was rootable before the one clicks came out ill try to find that old evo tutorial and find that command lol there was a video i belive with it and the rootz wiki is what my other link on the other page was supposed to send u to i guess i missed a couple of words in the URL on that other page lol good luck to you keep us updated im glad the flex has gotten a community like ours that can use examples to start from scratch
Command should be "fastboot boot recovery.img". User attn1 from the burst developers said if it boots the recovery we should be able to install it with the recovery. I can also use fastboot on Windows in case anyone is interested. Also can we get the custom CWM posted?
Sent from my PantechP8010 using Tapatalk 2
@noobfordroid could you please PM us a link to your cwm recovery ? wow @jsterrling someone from burst actually replied ive been trying for a while now lol hope we can get this up and going using the fastboot command and that the security measures on this boot loader are not insane like that of HTC
---------- Post added at 11:48 AM ---------- Previous post was at 11:40 AM ----------
Btw any of you heard about the pantech discover coming out soon specs are close to ours but with better hardware like camera and display
Yeah, I actually joined the IRC channel and left a message, he was nice enough to reply back right after I got off of work. I'm probably going to be pretty busy up until Friday with work, I took a lot of time off for other reasons but I'm going to try to work on unlocking the bootloader when I can. Fastboot can be used in Windows just installed the Google USB drivers that come with the SDK and all is well.
We just need a custom CWM which I guess I'm going to start working on unless noobfordroid can post his.
jSterling said:
Yeah, I actually joined the IRC channel and left a message, he was nice enough to reply back right after I got off of work. I'm probably going to be pretty busy up until Friday with work, I took a lot of time off for other reasons but I'm going to try to work on unlocking the bootloader when I can. Fastboot can be used in Windows just installed the Google USB drivers that come with the SDK and all is well.
We just need a custom CWM which I guess I'm going to start working on unless noobfordroid can post his.
Click to expand...
Click to collapse
at the risk of being fired ive been on here at work all day lol i was also at work when me and donovan01 were working on the root for the flex lol im captivated at starting from scratch feels like were all pioneers that our work would prbly help out future pantech users since it seems pantech is trying to become a top tier cell phone company now
atadres said:
at the risk of being fired ive been on here at work all day lol i was also at work when me and donovan01 were working on the root for the flex lol im captivated at starting from scratch feels like were all pioneers that our work would prbly help out future pantech users since it seems pantech is trying to become a top tier cell phone company now
Click to expand...
Click to collapse
Yeah they're showing some nice phones now and this has to be probably the best smartphone I've ever owned, camera aside. They just need to support developers but as soon as they do that ill be a pantech customer for life.
Sent from my PantechP8010 using Tapatalk 2
I will send the link a soon as i get home
Sent from my PantechP8010 using xda app-developers app
fast boot recovery
noobfordroid said:
I will send the link a soon as i get home
Sent from my PantechP8010 using xda app-developers app
Click to expand...
Click to collapse
I tried teh fastboot recovery but it is still booting to the phone. Will try to create the recovery again and try
---------- Post added 9th January 2013 at 12:16 AM ---------- Previous post was 8th January 2013 at 11:40 PM ----------
noobfordroid said:
I tried teh fastboot recovery but it is still booting to the phone. Will try to create the recovery again and try
Click to expand...
Click to collapse
boot.img - http:// db .tt/kKJM0n6z
recovery.img - http:// db .tt/SNmTapqg
cwm recovery - http:// db .tt/k6eVZagS
Awesome, I'll take a look tomorrow. Also boot.img and recovery.img are stock I'm assuming?
EDIT: Post #100!!!
Yes.they are stock
Sent from my PantechP8010 using xda app-developers app
[/COLOR]Ok guys boot into recovery with volume up plus power button! then tap volume up + DOWN at the same time it pulls up a menue with the words reboot system now apply update from external Storage wipe data factory reset apply update from cache and when your rooted a new button comes up that says rooted! lol ? ? and when u press on it it says this device was rooted lol seriously pantech tryinna thruw our warrinties under the bus or what!
cwm recovery
The cwm recovery i posted above is not working. I followed a guide online to port that recovery. Can someone post any tutorial for posting cwm?
Looks like we need to consult the burst.developers. did it just hang at fastboot?
Sent from my PantechP8010 using Tapatalk 2
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html here you go i think youd have to change the repo from gingerbread to ICS u know lol so we dont end up with abad port
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