I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Hi, have you installed adb succesfully in your pc previously?
If yes then the next thing you need is fastboot.exe file, if not then start with that first then fastboot.
You can find what you need here, also if you search in my threads (link in my signature) you can find a tutorial about how to install and use ADB.
~ Veronica
Acclaim
I have the same challenge. I have ADB working successfully (and have used Veronica's guide to repartition my NT - thanks again). Yet when I use Cyanoboot and start Fastboot my device shows up in Other Devices as Acclaim and none of the USB drivers I have pointed to get installed. It isn't mission critical that I solve this but it would be nice from a knowledge base to understand what I am missing in case I ever need to use Fastboot. It seems to be a much easier tool to change the installed Recovery image than ADB. Any help would be appreciated.
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
ShinnAsuka said:
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
Click to expand...
Click to collapse
+1
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
bingoz said:
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
Click to expand...
Click to collapse
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
bingoz said:
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
Click to expand...
Click to collapse
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Can you explain more or upload the file already edit for me? Thank you
bingoz said:
Can you explain more or upload the file already edit for me? Thank you
Click to expand...
Click to collapse
each product id is different so uploading the file isn't going to do you much good. sorey
Sent from my Nook Tablet CM7 BETA using xda premium app
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
I don't have windows so I won't comment on that. There is one thing that I never see mentioned when talking of adb access problems.
On custom roms (your case cm9 0.05.1) in settings, developer options, Android debugging should be checked to allow adb access. If not checked that may be your issue.
If I'm having adb issues and it was working previously I'll boot to cwm (5.5.0.4 version not 5.0.2 or whatever) and go from there.
You should get adb working properly, but to flash recovery you can use one of the flashable zip files while in cwm. They work for me!
Got a few minutes on a windows 7 pc (people should take their breaks at their desk). If you are using Veronicas thread http://forum.xda-developers.com/showpost.php?p=22049356&postcount=1 you will find a file runmefirst.bat if you run it and follow instructions about unplugging and replugging nook it will create and setup the previously mentioned file. Do not run zergy as suggested. When it pulls device manager your exclamation should say nook. Right click it, update driver software, browse my computer, let me pick, and then choose the directory with your usbdrivers, tell it yes to use them. Do not worry about anything else from runmefirst.bat including anything else to run. You just want it to set the codes for your nt and then it is of on use.
I had adb working for my nt quickly on that windows 7 pc. It had no previous adb or usb drivers installed.
Good Luck
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
nba1341 said:
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
Click to expand...
Click to collapse
like i said in a previous post, right click the acclaim item under other devices and look for the product id and edit the android_winusb.inf accordingly.
after that right click acclaim, update driver software, and browse for the drivers yourself. if all goes well fastboot should work. this is how i did it. not that i ever really use fastboot but its good to have just in case.
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
Check your android_winusb.inf to see if you have the right entry for the NT -- see http://forum.xda-developers.com/showpost.php?p=35971559&postcount=13.
---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------
Penguin101 said:
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
Click to expand...
Click to collapse
Why not flash your NT using SD-based CWM Recovery (e.g., see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31)?
The easiest way under windows, is just choose the driver on your own, use the driver from the Android SDK (sdk\extras\google), and you will be presented with a couple of options, choose Android Composite ADB Interface.
Related
So I am running Onecosmics RC3.1 with eugenes kernel.
I have installed the USB drivers from Samsung for 64bit, but device won't show up under adb devices nor can I browse my phone although I can see the mounted partitions under My Computer. Under Device Manager, I do see a GT-I9000 under Other Devices, but can't get a driver to install?
Any suggestions?
install nexus s drivers? http://developer.android.com/sdk/win-usb.html
if you did try putting phone in recovery then adb
Cool thanks for the info, will try this when I get home
Sent from my GT-I9000 using XDA App
trailblazerz11 said:
install nexus s drivers? http://developer.android.com/sdk/win-usb.html
if you did try putting phone in recovery then adb
Click to expand...
Click to collapse
Nope, still no device in recovery either. I have already installed the drivers that come with the SDK. I would really like to connect to adb for that is the only possible way to transfer files at this point.
jzero88 said:
Nope, still no device in recovery either. I have already installed the drivers that come with the SDK. I would really like to connect to adb for that is the only possible way to transfer files at this point.
Click to expand...
Click to collapse
Did you try and find the phone in the Windows Device manager and force a change to the different drivers? Just installing them may not be enough.
I currently have a tf201 stuck in a CWM recovery boot loop.
Multiple computers will not recognize the usb drivers so, I can't use the adb methods listed in the thread.
I tried downloading the firm from asus and unzipping it and placing it on the root of my external micro-sd card. The tablet does not attempt to read to external-microsd on boot and CWM only shows the internal 32g.
Short of sending it back to asus for repair I think I'm screwed.
Any ideas?
snapplex said:
I currently have a tf201 stuck in a CWM recovery boot loop.
Multiple computers will not recognize the usb drivers so, I can't use the adb methods listed in the thread.
I tried downloading the firm from asus and unzipping it and placing it on the root of my external micro-sd card. The tablet does not attempt to read to external-microsd on boot and CWM only shows the internal 32g.
Short of sending it back to asus for repair I think I'm screwed.
Any ideas?
Click to expand...
Click to collapse
First off, wrong forum.
Second, learn how to use search.
http://forum.xda-developers.com/showthread.php?t=1601942
http://forum.xda-developers.com/showthread.php?t=1599991
pandaball said:
First off, wrong forum.
Second, learn how to use search.
http://forum.xda-developers.com/showthread.php?t=1601942
http://forum.xda-developers.com/showthread.php?t=1599991
Click to expand...
Click to collapse
Sorry about posting in the wrong forum, but I created this topic after exhausting the posted recovery methods. Both links look promising but if my PC can't see the tablet then adb is rendered useless along with the possible recovery methods. :\
Secondly if you have unlocked BLer and CWM then you DO NOT FLASH Asus firmware... Becomes a possible brick... You need to install the naked ADB drivers... Do a search in the prime forums for "Naked ADB drivers", that's what I had to do to get my prime out of a CWMLOOP
Sent from my ROOTED HTC One X using xda premium
LNKNPRKFN said:
Secondly if you have unlocked BLer and CWM then you DO NOT FLASH Asus firmware... Becomes a possible brick... You need to install the naked ADB drivers... Do a search in the prime forums for "Naked ADB drivers", that's what I had to do to get my prime out of a CWMLOOP
Sent from my ROOTED HTC One X using xda premium
Click to expand...
Click to collapse
I'm still trying my hand with the drivers but I've been unable to get the tablet to show up in device manager so I can install the drivers. Whenever I try to right click and force the install it i get this error message..."The inf file you selected does not support this method of installation."
Man, i'm almost 100% sure that this is os behaving like it shouldnt. Really, just install linux on dualboot, android sdk, and adb/fastboot binaries, make sure you have the correct device usb id on android udev rules, both for adb and fastboot, and just execute adb through sudo.
It's a lot more reliable than windows for this kind of stuff, and these days the learning curve isnt steep at all.
sent from my i9250
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium app
So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
IceAzures said:
So not sure exactly what happened while running the lastest paranoid build. Everything was fine until a random reboot happened, said proccess stopped working and rebooted once more except for im on white screen. went to wipe data and reflash the rom but sd card has been wiped. I am s-on and cant get adb to recognize my device. Any advice please.
Click to expand...
Click to collapse
go into recovery and try turning adb sideload on then off and see if adb recognizes your device after that.
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
IceAzures said:
failed to open driver control: no such file or directory
when i start adb, it zooms really fast through codes and then exits.
Click to expand...
Click to collapse
Then you didn't set adb up correctly
Edit: now that I think of it you may be typing in the command incorrectly.
Sent from my HTC6435LVW using xda app-developers app
Ill reinstall the sdk and drivers and ill report back.
This is the correct way right?
http://forum.xda-developers.com/showthread.php?t=2131284
edit1: so to use adb im using the windows vista cmd promt correct?
edit 2: okay so we are somewhere. Adb now works. I just need to get the dna to be able to be detected. Any way i can do this?
(double post accident)
IceAzures said:
(double post accident)
Click to expand...
Click to collapse
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Get into twrp
Find to sideload option.
Select it.
Plug your phone into your computer, make sure to use usb 2.0 not 3.0.
Open up a command prompt where the rom is located.
Type adb sideload rom.zip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
IceAzures said:
So i was getting help from another member and I feel like he is getting frustrated as I am. Im running CWM 6.0.2.1 and this is what im dealing with
Device is not recognized even though i have the drivers for it. I heard USB debugging is enabled regardless in recovery I just don't know why I cant push or sideload anything even if im on install zip from sideload.
Click to expand...
Click to collapse
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
beaups said:
CWR has some issues with adb. flash latest version of twrp here:
http://techerrata.com/browse/twrp2/dlx
Click to expand...
Click to collapse
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
IceAzures said:
Do you think vista might be an interference? Im currently on waiting on device while trying to flash the recovery in fastboot
Click to expand...
Click to collapse
nope. Vista sucks and all, but it isn't the problem here.
IceAzures said:
Do you think vista might be an interference?
Click to expand...
Click to collapse
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
beaups said:
nope. Vista sucks and all, but it isn't the problem here.
Click to expand...
Click to collapse
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
AGoogleUser said:
There's your problem. "Vista"
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah and unfortunately its all i got
IceAzures said:
So what would you recommend at this point? Because at this rate im surprised my phone is not dead yet. Although i do see the led light in recovery mode
Yeah and unfortunately its all i got
Click to expand...
Click to collapse
I'd recommend you flash twrp then adb push your rom, then flash it
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
IceAzures said:
Okay im going to post the steps and maybe this will be easier for all of us.
1- Flashed Paranoid
2- Flashed crpalmers boot.img in flashgui
3- Phone was good for a solid day, then rebooted.
4- After reboot phone said a lot of the services are force closing and then rebooted into the white htc screen
5- http://forum.xda-developers.com/showthread.php?t=2131284 and followed it to the T
6- phone is not being recognized in adb
7- went to flash the recovery but its waiting on device even though its in fastboot usb
Maybe im missing a driver or a step I am not sure about but hopefully that helps a bit more than posting little by little.
Click to expand...
Click to collapse
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
reaverclan said:
Do you htc's adb drivers installed? Not just the sdk.
Sent from my VIPER DNA
Click to expand...
Click to collapse
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
When in device manager , how is the unit listed? Does the listing have an yellow exclamation point in front of it?
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot but still having issues pushing or flashing rom
Click to expand...
Click to collapse
Might want to unplug from the net when installing them so it doesn't look for others which driver version you installing? EDIT: also if you have a otg cable then you can put the rom on a flash drive and flash it from that.
Sent from my VIPER DNA
IceAzures said:
I believe i have them installed, but everytime i try to install the drivers via device manager I have windows telling me its already and its latest driver installed.
Good thing though is now my device is being recognized in adb and fastboot <devices> but still having issues pushing or flashing rom
Click to expand...
Click to collapse
What error is it giving you when you try to push a rom.
Sent from my HTC6435LVW using xda app-developers app
Hello everyone,
I have been searching in vain for a while now to find a solution to my problem and I fear that I may have done something daft to my phone.
I am using a HTC One X+ that was unlocked, s-off and rooted for about a year, i had TWRP and stock android 4.1.1. For ages I have been getting an update alert saying a software update is ready and i think it was some Vodafone update (1.17.161.7). Whenever i accepted and tried to install this it would obviously reboot into TWRP and then the update would fail. This was fine until last night when I decided to install it through TWRP, it said it failed again and i rebooted to find that WiFi wouldnt turn on, my phone was no longer rooted or s-off and that I get no signal. I tried to re-root it but command prompt on the computer or HTC Sync wouldnt recognise my device however it was appearing as HTC One X+ in My Computer and i could access the internal storage.
I restarted into recovery and managed to flash a new root using twrp and the root file using the unlockr.com - how to root the htc one x
Then thinking it was a ROM issue i downloaded and installed InsertCoin Evolution ONE X+ 5.0-6 Sense 5 Android 4.2.2.
This all went through ok however when i reboot from this install it just sticks at the HTC Quietly Brilliant screen. I wiped everything using twrp beforehand.
When i restart into bootloader, it says unlocked, S-On and HBOOT -1.30.0000
Not sure what else to do as now i have no ROM, i read that you have to partition the SD card for InsertCoin to work but the option to partition SD card isnt there in my TWRP (ver. 2.3.3.0)
Any help to even reset my phone back to basic stock everything would be amazing, i have a Titanium Backup of most of my stuff saved btw.
Thanks to anyone who can help.
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
EDIT - Now seen the instruction to flash the boot.img - what a fool i am. Now i need to get it recognised by USB again so i can transfer the zip file to it and go again.
maxwell689 said:
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
Click to expand...
Click to collapse
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Without a rom installed you're not able to acces the internal memory of your phone directly. You have to use "adb sideload" command to transfer a rom onto your phone. Look in the General and/or Q&A forum of this device, there are enough guides or topics on how to solve this "problem".
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Optimus said:
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Click to expand...
Click to collapse
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
maxwell689 said:
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
Click to expand...
Click to collapse
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Ghand0ur said:
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Click to expand...
Click to collapse
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
maxwell689 said:
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
Click to expand...
Click to collapse
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Lol.. Well, as i said try to run the Toolkit/cmd as administrator and try different usb ports.. It took me 5 minutes on windows 8 for the adb to properly read the device , had to try different usb ports, unplug , replug, and so on..
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Optimus said:
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
maxwell689 said:
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
Click to expand...
Click to collapse
Thats great news that all is well now..feel free to post.. and dont forget to press the Thanks button