Related
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Have you reviewed the jmztaylor method?
Have you reviewed this method?
http://forum.xda-developers.com/showthread.php?t=1905674
Worked for me after I grabbed the drivers from PDAnet.
I have one issue of Android is Updating stuck in loop that some others in that thread have sorted out but I can't quite get working yet!
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
same problem.
I am having the same exact problem. I have reviewed the jmz method and keep getting stuck in cmd saying path not specified. Any solutions. All steps have been followed to the letter.
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
cruise350 said:
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
This thread goes through doing it manually, it is written for Ubuntu(linux) but it can be used in windows as well, you just don't use sudo for the commands. Also the package in the following thread already has the updated gapps package that does away with the "android upgrading" on every boot.
http://forum.xda-developers.com/showthread.php?t=2016463
fast boot won't install
Had ''path not specified'' it gets to the if stuck here drivers aren't installed. A window pops up saying ''installing fast boot'' but then says it failed. Thats where im stuck.
4.1.1 OS
2.4 product version
Thinking the 2.4 update is a problem.
Any suggestions?
I know i'm years late here but I really HATE adb and esp. BAT files that are just suppose to do their thing........I'm hitting a wall with this Nabi 2 Bat file for TWRP / ROOT. I've used PDAnet plenty in the past for internet but never for the purpose of just getting drivers so I have no idea I hate that program too. ANYWHO , I'm getting "cannot find specified path" which I probably could fix if I ****ing knew which ****ing path it was looking for. SO if anyone could please enlighten me here , I've installed and uninstalled PDA net some 10 times now , with Samsung selected , with LG selected with OTHER selected , I cannot get this to work. I can do FASTBOOT devices , and poof it shows up , adb works fine all that , show the device but I cannot get this ****ing BAT all in one installion to work. I'm really just about to flash it all manually through ADB but I'd rather use the installer to make sure I get the random WINGS files removed or whatever. Any help would be great , thanks.
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
GoRiLaz301 said:
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
GoRiLaz301 said:
Hi Everyone / Anyone,
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
[email protected] said:
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
Click to expand...
Click to collapse
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
In CUSTOM Recovery the USB debugging is enabled by default...so that step of booting into phone and enabling the USB debugging doesn't matter...
the device won't get recognized if u had not installed the HTC drivers...
try installing the latest drivers from here
Install this and try
Code:
adb devices
And what are u planning on do install a custom ROM or Flash the Stock Nandroid backup from the thread I provided.....????
I can only help u knowing what u are trying to do.....
GoRiLaz301 said:
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
Click to expand...
Click to collapse
GoRiLaz301 said:
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
Click to expand...
Click to collapse
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
GoRiLaz301 said:
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
Click to expand...
Click to collapse
Fine and clear..
have u tried the drivers I have put in the previous post.........????
Try different USB ports to on ur PC too.......that will work sometimes.......:fingers-crossed:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
GoRiLaz301 said:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
Click to expand...
Click to collapse
These are the latest HTC drivers can u try this and report whether ur device is recognized in adb recovery mode......
Please try by uninstalling the previous driver u had.........
BTW is it Windows 8.......????????
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it. it will be recognized as HTC MP DEVICE or something similar but with unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognized as HTC device without USB driver device installation problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Earlier before your help, have found and load TWRP version 2.6.3.0 whereas now the version is 2.4.4.0, will earlier or this 2.4xx version be any difference and affect the connection with adb?
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
GoRiLaz301 said:
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it.
it will be recognised as HTC MP DEVICE or something similar but will unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognised as HTC device without USB driver problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
Click to expand...
Click to collapse
From the control panel OFC
If u had installed HTC drivers u must be able to see it like this uninstall that...
O Haa haa )
Blunder me ! That's right ! Think bit exhaust after a few sleepless nights figuring out why and hows on this phone....
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
GoRiLaz301 said:
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
SDK Manager wont show up on Control panel AFAIK....
it will be a zip file which u have to extract.....
in the extracted folder u will be able to see android-sdk-windows\platform-tools from where u have to open the cmd to execute the abd/fastboot commands
I have the setup of android-sdk-windows and the HTC drivers I pointed to....
It works flawlessly so i recommend to uninstall Universal Adb driver since that isn't helping ur phone recognized anyways.....
Install the Drivers I pointed to and try wether ur phone is getting recognized....:fingers-crossed:
Note : Alternately u can try this installer also which is a small package with the necessary adb and fastboot files......
---------- Post added at 06:43 PM ---------- Previous post was at 06:32 PM ----------
GoRiLaz301 said:
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
these drivers can be there ...they are or the installation of bluetooth drivers for our phones I guess....
Just uninstall the Universal USB driver .....
If you have HTC Sync I beleive u must be having the HTC driver as I showed on the Screen shot.....
Anyways if u dont see that in the control panel install the one I gave.....U must be fine
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
GoRiLaz301 said:
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
Click to expand...
Click to collapse
FIne....
From bootloader boot into recovery.....
try whether u r device is recognized.......
If recognized PROFIT for the hectic work done......
then u can push a rom to ur SDCARD using adb push command......
then install as usual from the recovery........
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
JACK POT !!!!
ADB DEVICES listed my device s/n. in recovery mode.!
GoRiLaz301 said:
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
Click to expand...
Click to collapse
Absolutely Fine........
What I meant in While in TWRP connect ur phone to PC
double click on your Start SDK shortcut and in the CMD type
Code:
adb devices
Ur result must be like this
YES, it did show the device listed with serial no.
Now i into the [Recovery Installation] section and at the BACKUP part (pt. 15), now should i also tick Recovery + Cache to perform full backup of actual ROM? (this seem not applicable to me, is it?)
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying: