A buddy of mine has a Nexus S. He's been having issues with his phone. He was having issues with screen locking, none responsive, etc. Now his phone won't boot. It stays stuck in recovery. Anything can be done? Phone is not rooted.
For sure. Is it a custom recovery or stock?
Sent from my Nexus S using XDA Premium App
For sure. Is he running a custom recovery or stock?
Sent from my Nexus S using XDA Premium App
He's running stock.
It's weird that it's degraded like this. I've only had a Captivate and now I have the Atrix and I've never seen this happen unless trying to flash a custom rom. But I know he doesn't know how to do that.
To get specific he's got:
OS: 2.3.3
Baseband: I9020XXKb1
Kernel: 2.6.35.7-g1d030a7
Build Number: GRI40.
My friend, you must do the following:
1- flash cwm recovery via sdk on bootloader mode.
2- download any rom from the development forum (stock, cm7, and so on)
3- mount USB storage via cwm recovery
4- put the mod zip file on the root of the sdcard via usb
5- flash the rom(install zip)
6- reboot your device
Sent from my Nexus S using XDA Premium App
thanks! it's gonna be a bit of a task since i have to walk him through it all remotely.
razorbladex401 said:
thanks! it's gonna be a bit of a task since i have to walk him through it all remotely.
Click to expand...
Click to collapse
NP
If you have any issues please post here so that i can help you
Having an issue installing the drivers. When we connect the phone it shows up as an unknown device. I try to use the google drivers and it doesn't install them. I install kies and it was able to install some drivers but i need to get adb access which I can't. The phone is in the bootloader but nothing i can do to it. Any ideas?
razorbladex401 said:
Having an issue installing the drivers. When we connect the phone it shows up as an unknown device. I try to use the google drivers and it doesn't install them. I install kies and it was able to install some drivers but i need to get adb access which I can't. The phone is in the bootloader but nothing i can do to it. Any ideas?
Click to expand...
Click to collapse
Try pdanet. It installs the drivers for any phone. Install it on his computer and his phone.
Sent from my Nexus S using XDA App
Rafael Cadina said:
My friend, you must do the following:
1- flash cwm recovery via sdk on bootloader mode.
2- download any rom from the development forum (stock, cm7, and so on)
3- mount USB storage via cwm recovery
4- put the mod zip file on the root of the sdcard via usb
5- flash the rom(install zip)
6- reboot your device
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
He's gonna need to root before being able to flash a custom recovery.
Sent from my Nexus S using XDA App
I spent 6 hours fixing this guys problem because he was a amateur.
Read this http://forum.xda-developers.com/showthread.php?t=1000722 It'll go through the process. It's pretty much the same as your problem.
tl;dr.
1. Get USB Drivers
2. Setup SDK tools
(Links for these are in my thread).
3. Unlock the phone if it isn't already (fastboot oem unlock)
4. Download CWR IMG (its in my thread)
5. fastboot flash recovery recovery.img (rename crespo-clockwork..... to recovery.img; it has to be in /sdk/tools/ .. show extensions).
6. boot into CWR
7. mount USB
8. download a ROM (or do this before you start -- or nandroid backup)
9. wipe dalvik,cache,factory (if you're flashing a ROM)
10. flash or nandroid restore
11. phones back to normal
zephiK said:
I spent 6 hours fixing this guys problem because he was a amateur.
Read this http://forum.xda-developers.com/showthread.php?t=1000722 It'll go through the process. It's pretty much the same as your problem.
tl;dr.
1. Get USB Drivers
2. Setup SDK tools
(Links for these are in my thread).
3. Unlock the phone if it isn't already (fastboot oem unlock)
4. Download CWR IMG (its in my thread)
5. fastboot flash recovery recovery.img (rename crespo-clockwork..... to recovery.img; it has to be in /sdk/tools/ .. show extensions).
6. boot into CWR
7. mount USB
8. download a ROM (or do this before you start -- or nandroid backup)
9. wipe dalvik,cache,factory (if you're flashing a ROM)
10. flash or nandroid restore
11. phones back to normal
Click to expand...
Click to collapse
Zephiks got you covered. I was gonna walk you throught it but had to go to class. Hope you get it working.
Sent from my Nexus S using XDA App
I can't get the phone to show up as an adb device. I had installed the drivers using PDAnet which worked for a few minutes. I went to unlock the bootloader but it just froze. It didn't do anything after about an hour we powered the phone off. now after you start it up it doesn't show up as an adb device.......
razorbladex401 said:
I can't get the phone to show up as an adb device. I had installed the drivers using PDAnet which worked for a few minutes. I went to unlock the bootloader but it just froze. It didn't do anything after about an hour we powered the phone off. now after you start it up it doesn't show up as an adb device.......
Click to expand...
Click to collapse
What OS do you run in your PC?
You must first download de sdk .zip, extract it into a folder.
Then, install USB package from the SDK.
Then, enter devmgmt.msc on Run... (Windows). Select the driver that is missing (Android 1.0) > Left click > Update driver > Browse my computer > Let me pick from a list > have disk > choose the folder you installed google usb drivers (inside C:\ SDK folder\extra).
Rafael Cadina said:
What OS do you run in your PC?
You must first download de sdk .zip, extract it into a folder.
Then, install USB package from the SDK.
Then, enter devmgmt.msc on Run... (Windows). Select the driver that is missing (Android 1.0) > Left click > Update driver > Browse my computer > Let me pick from a list > have disk > choose the folder you installed google usb drivers (inside C:\ SDK folder\extra).
Click to expand...
Click to collapse
Yea i've tried that to load the driver. It's running Windows 7 Home Premium 64bit. The only drivers that seem to work are from PDAnet. I finally got it to show up again so i've issued the fastboot oem unlock, my buddy confirms it but the phone does nothing.....
Related
i have already checked xda for a solution but couldnt find one i even checked google and youtube and still found nothing i am in need help bad. i will even pay someone paypal if they can help me with my phone
i downloaded the matrix rom and i liked it but i wanted to go back to ice cream sandwhich for the day so when i tried to go to recovery it froze on the google screen while trying to get to recovery i kept trying and trying but my recovery wasnt working i couldnt get to it. so i went to titanium back up and clicked un-install all system and data because i thought it was when i restored all system and data from ICS but after i did the uninstall i kept getting a force close alot of things and i got all the way down to one and it was process.android i think and everytime i clicked force close it popped right bacj up instently. so i took out the battery and put it back in and now i cant power on my phone it gets stuck on the matrix screen. can you please help me i can only acces the volume up power button menu.
*solved*
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
it wont let me do any of that it keeps saying waiting for device then gets stuck on that ive installed pdanet but it keeps giving me a htc sync error =1 and my bootloader and everything was already unlocked i dont know what to do i cant turn my phone on or get to recovery. thats why im paying 100 dollars to anyone who can help me restore my phone and make sure its up and running ive been trying for 2 days now and thats my work phone and everything im stressed
Serious_Beans said:
Fastboot OEM lock. Fastboot OEM unlock and start the process all over again. Also wipe everything 3 times.
Including system and boot.
Also double check you're installing all the compatible zips.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
when i turn on the phone and it keeps trying to load the matrix animation the phone still connects with my computer and says removable disk f but when i try and click on it. it says please insert a disk into removable disk f
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Serious_Beans said:
Hmm uninstall all the USB drivers and reinstall them
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
at the bottom of my phone screen it says fastboot statud - FAILInvalid command
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Make sure you are using the most up to date drivers and then use ADB to install recovery again. If I'm understanding it right I think that's what you need to try.
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
can someone help me threw team viewer and just access my computer threw that and help me that way
Envynet said:
If you have the SDK installed on your computer. Here is what you need to do in order to get back into recovery.
#1 Boot your phone into bootloader, Vol up and power
-Plug into computer using usb while in fastboot(bootloader) and see if it recognizes it. Type adb devices it should list a serial number for your device.
( My SDK is installed in c:\android\) so you would type something like cd c:\android\tools and hit enter and then type adb devices )
#2 If you have installed sdk and pdanet drivers and your computer still does not see your phone in fastboot is this. Go to the folder where sdk is installed and copy everything excluding the folders that is in the Platform-tools folder into the tools folder. After that download Stock Phone files unzip it into a folder on desktop.
Dont run the script yet, what you have to do is after you unzip the stock look in the folder you just unzipped them in and you should see a file called fastboot, adb, and some other .dll's AdbWinApi.dll and etc move only these 4 files to your sdk tools folder.
#3 Now re open a cmd prompt and go back to c:\android\tools (enter) then type in adb devices and your computer should recognize it this time around.
Then all there is left to do is download the recovery of your choice here's mine Recovery and after you download it rename it recovery. After you rename it move it to sdk tools folder and while still in fastboot(bootloader) type in fastboot flash recovery recovery.img
You should now be able to enter recovery and flash roms again
EDIT #1
If you havent setup SDK here is a wiki guide on how to do so http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Click to expand...
Click to collapse
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Maybe you should just try Odin.
http://forum.xda-developers.com/showthread.php?t=1022481
DL: http://droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html
Greetz
OP... check your PM inbox.
Why on earth have you posted this thread 6 times? Lol
Sent from my Nexus S using XDA App
scottypeterson said:
Dang you must have put this up like 2 second before I posted mine lol
Sent from my Supercharged MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
mathkid95 said:
Ok I don't know if you tried this already but do this:
1. download the recovery img from here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and put it somewhere on ur computer
2. plug phone into comp
3. boot the phone into the fastboot mode with the android guy
4. fastboot erase recovery
5. fastboot flash recovery ____.img
and if you can boot into recovery now, just wipe data, cache, and dalvik cache and flash the ics rom
see if that helps
Click to expand...
Click to collapse
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
Da_Reaper said:
after i type adb it says adb isnt recognized as a internel or external cammand operable program or batch file
Click to expand...
Click to collapse
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Yes thank you guys i love u all
check your mp , excepted if you found the solution.
$100? Lol
Sent from my Nexus S using XDA App
crump84 said:
I suggested this about 7 hours and 3 threads ago.. I think the problem is either he doesn't have the proper drivers or SDK setup properly.
This leads me to believe that SDK isn't set up properly. If it's set up correct you should be able to access adb without the phone even connected.
Click to expand...
Click to collapse
Yeah excuse me for not reading all 6 threads
Sent from my Nexus S using XDA App
Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.
Pinoy_Ako said:
Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.
Click to expand...
Click to collapse
1) Download the Android SDK (if you haven't already).
2) Run Android Debug Bridge using Command Prompt or Terminal (Depending if you are Windows or Mac)
3) Use ADB to pull the build.prop file to your computer.
4) Alter the LCD Density back to normal. Make sure the permissions are 644.
Alternative 3) Download the stock build.prop for your device.
5) Push either the build.prop (with normal LCD density) back to /System/ in ADB
Tell me how it goes
williamguy said:
1) Download the Android SDK (if you haven't already).
2) Run Android Debug Bridge using Command Prompt or Terminal (Depending if you are Windows or Mac)
3) Use ADB to pull the build.prop file to your computer.
4) Alter the LCD Density back to normal. Make sure the permissions are 644.
Alternative 3) Download the stock build.prop for your device.
5) Push either the build.prop (with normal LCD density) back to /System/ in ADB
Tell me how it goes
Click to expand...
Click to collapse
I already downloaded the Android SDK and installed it. I run the ADB by using the command prompt but it only gives me the commands ( like -d, -e, -s, -p). How do you use this thing? Can you please elaborate on how use this thing and how ADB can pull the build.prop since I can't seem to connect my device to computer?
Pinoy_Ako said:
I already downloaded the Android SDK and installed it. I run the ADB by using the command prompt but it only gives me the commands ( like -d, -e, -s, -p). How do you use this thing? Can you please elaborate on how use this thing and how ADB can pull the build.prop since I can't seem to connect my device to computer?
Click to expand...
Click to collapse
I'm not to familiar with ADB.
To pull files: adb pull /mnt/sdcard/path/to/file /path/to/local/file
To push files: adb push /path/to/local/file /mnt/sdcard/path/to/file
I manage to study the adb thing. The problem I face now is how to connect my phone to pc.My computer doesn't recognize my phone when I connected it. I tried to search for the device driver but I can't find any. Even the pc suite is missing for this phone.
Here is CWM recovery for A30. flash it using ANDROID AIO FLASHER in fastboot mode. using cwm you can easily fix your phone
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s
karan128 said:
Here is CWM recovery for A30. flash it using ANDROID AIO FLASHER in fastboot mode. using cwm you can easily fix your phone
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s
Click to expand...
Click to collapse
I dont know what fastboot mode means but I will try to see this ANDROID AIO FLASHER. Sounds that I will have to connect my phone to my pc. I just hope that it can help me to connect my phone easily.
Pinoy_Ako said:
Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.
Click to expand...
Click to collapse
install cwm . then flash it.. download cwm backup.. and just restore it ..
pree:good:
rajit said:
install cwm . then flash it.. download cwm backup.. and just restore it ..
pree:good:
Click to expand...
Click to collapse
If only it allows me to flash zip then it would be easy. the problem is i cant toggle off the signature verification.
Pinoy_Ako said:
If only it allows me to flash zip then it would be easy. the problem is i cant toggle off the signature verification.
Click to expand...
Click to collapse
You cannot toggle signature verification. You need to flash CWM first.
CWM is a custom recovery for android phones that provides many functions like system backup, restore, flashing zips, etc.
Flash cwm by going into fastboot mode
karan128 said:
You cannot toggle signature verification. You need to flash CWM first.
CWM is a custom recovery for android phones that provides many functions like system backup, restore, flashing zips, etc.
Flash cwm by going into fastboot mode
Click to expand...
Click to collapse
I already have this CWM before I rooted my phone. I just didn't flash it after I rooted it (silly on me ). Now my only hope is to have a fastboot but my problem now is how to get the drivers for my phone since I can't connect and my pc didn't recognize.
Can anyone give me a link where I can get the device drivers for this phone (windows user here)?
Install PDAnet on pc for drivers.
Sent from my A9 using xda app-developers app
I still can't connect my pc after installing the PDAnet. (Maybe it's time for me to get rid of this phone.)
Pinoy_Ako said:
I still can't connect my pc after installing the PDAnet. (Maybe it's time for me to get rid of this phone.)
Click to expand...
Click to collapse
h tt p: //adbdriver. com/ downloads /
download the 'adb driver installer'
run it
it will automatically detect the driver needed for u r device
and click install
This is TWRP recovery and Stock rooted roms for the ICS firmware on the tablet.
These will only work if you currently have ICS running on your tablet. If you still have honeycomb then do the upgrade first.
Nothing was added or removed from the stock roms besides root and busybox.
Only bug with TWRP is that you can't mount sdcard in recovery. Just use adb push.
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Thanks:
attn1 - gave me some help since I am new to pantech devices
Dees_troy - for TWRP code obviously
Tassadar - for his rotation code for twrp. Without this it wouldn't have been possible
Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
Downloads
just in case i need another
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
mavblues said:
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
Click to expand...
Click to collapse
On the computer. your command prompt should be at wherever you put twrprecovery.img file is. So for example you put twrprecovery.img at the root of c:, your command prompt should read c:/ .....
Sent from my M7 using xda premium
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
mavblues said:
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
Click to expand...
Click to collapse
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
jmztaylor said:
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Got it - working great!
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Did you check "USB debugging" on the tablet?
Also, I had to set USB connection on the tablet to the last choice "PC Data Mode".
Hope it helps.
jmztaylor said:
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
dagadu said:
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
Click to expand...
Click to collapse
Anytime when the tablet is not plugged in. This will make the computer automatically install anything needed for the tablet and you won't have issues with fastboot or adb anymore
Sent from my M7 using xda premium
jmztaylor said:
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Click to expand...
Click to collapse
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
1806 said:
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
Click to expand...
Click to collapse
Actually it's similar steps; however, yours is more like 1-click root
Anyway, I tried everything all above, but it didn't solve my problem, then I found the solution from other website
I just want to share in case others are stuck in fastboot mode like me:
1. When your tablet screen is on fastboot mode (white), go to device manager on your pc
2. Right click on Android > Update driver
3. Click on Browse driver
4. Choose Let me pick manually from my pc list
5. Choose Android phone and pick the first list there. It should be "Android ADB..."
6. Install and fastboot continued
if you can't find Android ADB from your pc list, then you should unplug device then install PC Suite.
here's the old tuts: youtube com/watch?v=UHRonVzBMsI
Hopefully it helps others and thank you very much for all your help!
Delete!
Finally! and a question
Finally a recovery for the element! Rhanks to the OP. Now I am less afraid to tinker with my tablet.
Question: The most important thing right now that I'd like to do is move the folder /data/data from the internal storage, to the internal SD card. This is stopping me from using Google Magazines and Google music, since their data is being stored there, and it shares space with actual applications. 1GB is not that much space for APPS, Dalvik Cache and APPs' data when you add magazines, and when google starts caching Music and Chrome data there. I currently only have 300MB left before I install Music and magazines. And that is AFTER I've used app2sd on all apps that can be moved. How do I do this?
I have tried simply creating a Link using "ln - s /mnt/sdcard/data /data/data" once I copied/moved the contents of the directory, which sort of works initially, but it will not work after a reboot. It actually stops my tablet from booting. (again, thanks to the OP for the recovery).
right now, I am just doing an "ln" on the specific folder inside the /data/data folder, but it acts weird when I use Titanium Backup to restore data
-> Android noob <-
Installing TWRP went smooth as silk. With twrprecovery.zip on you micro sdcard and Element connected with usb cable and USB debuuging checked 1.Just copy twrprecovery.img into your sdk folder/ platform-tools and also have a copy of cmd.exe from windows in the platform-tools folder. 2. Start cmd.exe and type or copy & paste command reboot bootloader 3. Then on white screen(fastboot) type or paste command fastboot boot twrprecovery.img 4. When you boot into TWRP install twrprecovery.zip.....As you rebbot system TWRP should ask if you want Supersu installed and swipe to install. Once rebooted install supersu from the Play store and open Supersu to update SU file all should be good
Thanks for the info and files. I know I'm a little late on this Tablet but picked it up cheap and with ATT 4G it goes along with my devices. The orginial owner hadn't even installed ICS and she wasn't even aware of an update. She now owns an Apple :laugh::laugh:device LOL
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
marcustaz said:
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
Click to expand...
Click to collapse
Yes good deal, got mine last month on Craigslist for $70.00 and works really well. The owner hadn't even updated to 4.0 or even knew how. It is a good tablet and have rooted it. I think its development is pretty well dead as not many sold. Only thing bad about it is the Element reads 2nd partition instead of 1st as most android devices do, so harder to use link2sd or folder mount as they both use 2nd partition.
Sent from my PantechP4100 using XDA Premium 4 mobile app
How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!
Euskadi said:
How can I flash a stock ROM considering I cannot boot the phone up normally in order to put the file onto the phone? The Moto G has no external storage so I can't use an SD card.
I get get into the bootloader, and I have managed to install Team Win Recovery Project but don't know what else to do!
Click to expand...
Click to collapse
Disclaimer : I have not used TWRP recovery on Moto G. So may have errors in my post
You have 2 options.
1. On some versions of TWRP, under advanced you have an option to mount USB. You can the access the phone as a drive from a computer.
2. Use ADB to push file to the phone. Install drivers and ADB works in recovery,
Thanks I actually found out about the adb push thing just after making this thread. I was able to push Beanstalk onto the device and install it through TWRP, however it's just stuck on the Beanstalk bootscreen forever. I tried installing it again and the same thing is happening. This also happened earlier when I tried to install Cyanogenmod
Once when i wanted to flash Stock 4.3 i got also stuck in bootanimation.
To restore Stock i had to execute flashall.bat /eu. The option /eu erases userdata. Once i did this my phone booted without any issues.
So what you can try is to erase userdata via fastboot or cwm
fastboot erase userdata
Click to expand...
Click to collapse
onyinly made
I tried one final Hail Mary before going to be last night, erased all data and installed Cyanogenmod again and I'm pleased to say it worked!
Only downside is I've lost all my apps & data. Now I did back these up using Titanium, and stored them on Google Drive, however the reason I got into this mess in the first place is because I manually flashed the 4.4.2 update, which worked ok, but then when I restored my apps/data with Titanium my soft buttons (back button etc) disappeared!
I guess I'll just play it safe and not try to restore the back up this time.
M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Sent from my HTC Desire C using XDA Premium 4 mobile app
the sarge said:
M8 u couldn't give a walk through guide how u pushed ROM to phone pls
Click to expand...
Click to collapse
Not exactly an expert myself but look for a download of 'Fastboot', it should have a program called adb.exe or abd-windows.exe. Turn on your phone while holding the Volume Down button and it should start into the bootloader screen, plug in the USB and it will say it's connected.
Then you go to the folder (on your PC) that has adb.exe - put your ROM .zip into this folder - then hold shift and right-click somewhere inside the folder (not on a file) and choose "Open command window here".
Then you just type "adb push ROM.zip /sdcard" where ROM.zip is the name of the zip file. note: you might have to type adb-windows instead, depends what .exe you have
Then just wait until it finishes transferring. Will take 30 secs or so for a 200mb ROM.
I'm sure if you google "adb push" you'll get some better instructions, with downloads etc
While reverting to stock it's important to use mfastboot(moto-fastboot) instead of normal fastboot. Download mfastboot.exe and place in adb folder, and replace 'fastboot' commands with 'mfastboot'
Sent from my XT1032 using XDA Premium 4 mobile app
Or try supertool on root junkies download site worked for me to get o t a kit kat
Sent from my Moto G using XDA Premium 4 mobile app
(my phone is rooted)I recently installed the android l on my nexus 5 using Nexus root tool kit.It was glitching so i installed 4.4.4.Then whenever i put my nexus 5 on it started saying google search stopped working and also gmail.So i did some other stuff.And now t is stuck on the google logo when i try and put it on.I held the three buttons and went into recover mod.I cleared the cache partition and also wiped my phone.Still it is stuck in the google logo please please please help im really scared.
Simple tutorial -
1. Download a ROM for your Nexus 5, any stable one is fine.
2. Make sure you have downloaded all the needed files for the ROM you are going to flash.
3. Boot your N5 into recovery mode and plug in your USB cable.
4. Make sure you have adb tools on your PC. If not, download the adb tools from Google. Or you can get it when you download the SDK.
5. Move the ROM you have just downloaded to your desktop. And the extra files if there is any.
6. Open cmd and link it to your adb folder. ie - cd c:/path/to/adb/folder
7. Inside the cmd window, push the rom.zip file to your device like this. adb push /path/to/desktop/rom.zip /sdcard
8. Do the same thing with the extra files you have downloaded, if there is any.
9. Once transfered, in recovery mode. Simply wipe data and cache. Then flash the rom. Reboot your device.
10. Have some hot cocoa because you just fixed your Nexus 5.
TheArc said:
Simple tutorial -
1. Download a ROM for your Nexus 5, any stable one is fine.
2. Make sure you have downloaded all the needed files for the ROM you are going to flash.
3. Boot your N5 into recovery mode and plug in your USB cable.
4. Make sure you have adb tools on your PC. If not, download the adb tools from Google. Or you can get it when you download the SDK.
5. Move the ROM you have just downloaded to your desktop. And the extra files if there is any.
6. Open cmd and link it to your adb folder. ie - cd c:/path/to/adb/folder
7. Inside the cmd window, push the rom.zip file to your device like this. adb push /path/to/desktop/rom.zip /sdcard
8. Do the same thing with the extra files you have downloaded, if there is any.
9. Once transfered, in recovery mode. Simply wipe data and cache. Then flash the rom. Reboot your device.
10. Have some hot cocoa because you just fixed your Nexus 5.
Click to expand...
Click to collapse
Thats pretty complicaed but il give it a go.anks
if thres an easier way please say so.
th
Let me know how it works out for you