Related
Okay, I tried to root a friend's phone with the new fresh kitchen and when the phone rebooted, I'm stuck on a screen with a phone and an exclaimation point in a triangle.
Any help here would be appreciated.
I've tried to mount the phone through sdk, but nothing..... HELP!
Turn off the phone, pull the battery if it won't turn off.
Hold the volume down key when you power it on. This should bring you into the factory bootloader.
Push menu to factory reset, this will erase all the phone's data. Then try to reboot.
While in fastboot...volume down and power button... You can try and flash the custom recovery via fastboot and adb from here
danknee said:
Turn off the phone, pull the battery if it won't turn off.
Hold the volume down key when you power it on. This should bring you into the factory bootloader.
Push menu to factory reset, this will erase all the phone's data. Then try to reboot.
Click to expand...
Click to collapse
Okay, holding the volume key down during boot brought me to the menu and I selected fastboot mode and it loaded back like nothing happened. But it appears that either the phone's not rooted or I can't get into recovery.
When I press home from that menu I just get the exclaimation point error again?
Any ideas?
jmoch2 said:
Okay, holding the volume key down during boot brought me to the menu and I selected fastboot mode and it loaded back like nothing happened. But it appears that either the phone's not rooted or I can't get into recovery.
When I press home from that menu I just get the exclaimation point error again?
Any ideas?
Click to expand...
Click to collapse
&RoidRage said:
While in fastboot...volume down and power button... You can try and flash the custom recovery via fastboot and adb from here
Click to expand...
Click to collapse
+1
Follow the instructions in RoidRage's link.
Or root your phone and install recovery .....http://forum.xda-developers.com/showthread.php?t=583291.
Are you able to send it adb commands from fastboot?
Try
Code:
adb devices
&RoidRage said:
While in fastboot...volume down and power button... You can try and flash the custom recovery via fastboot and adb from here
Click to expand...
Click to collapse
The recovery image is on the SD card but when I type the commands, I keep getting kicked back to android-skd-windows\tools command prompt.
danknee said:
Are you able to send it adb commands from fastboot?
Try
Code:
adb devices
Click to expand...
Click to collapse
yes, and I get the device name.
Image is on the SD card, can seem to get the recovery image to flash.
Edit: I'm thinking the rooting didn't go through.... I get permission denied
jmoch2 said:
yes, and I get the device name.
Image is on the SD card, can seem to get the recovery image to flash.
Click to expand...
Click to collapse
Phone may not be rooted? Follow the guide RR posted to the T. This will root the phone and flash the recovery image.
http://forum.xda-developers.com/showthread.php?t=583291
danknee said:
Phone may not be rooted? Follow the guide RR posted to the T. This will root the phone and flash the recovery image.
http://forum.xda-developers.com/showthread.php?t=583291
Click to expand...
Click to collapse
Okay, got it done with the above instructions, however now when in recovery if I try to do a nan backup I get the following error:
Error : Run 'nadriod-mobile.sh' via adb!
Also, if i'm at the command prompt, I can use adb devices to see the device, however when I type adb remount... I get "remount failed: Operation not permitted"
My phone is rooted and an adb shell command gives me #
But my friends phone which I've tried to root using fresh kitchen and manual gives me a $
What am I doing wrong?
jmoch2 said:
Okay, got it done with the above instructions, however now when in recovery if I try to do a nan backup I get the following error:
Error : Run 'nadriod-mobile.sh' via adb!
Click to expand...
Click to collapse
I remember seeing this error before and it has something to do with the SD card. The fix was something like backing up the card then formatting it. How much free space do u have on the card?
Edit: Run nandroid-mobile.sh via adb! error > http://forum.xda-developers.com/showthread.php?t=621940
jmoch2 said:
Also, if i'm at the command prompt, I can use adb devices to see the device, however when I type adb remount... I get "remount failed: Operation not permitted"
Click to expand...
Click to collapse
Are you in recovery when you try the "adb remount" command? And u went thru the rooting process w/out any errors running the "adb push" and "adb shell" commands?
Edit: you can get su(#) by typing "su" after in shell ($)
kyouko said:
I remember seeing this error before and it has something to do with the SD card. The fix was something like backing up the card then formatting it. How much free space do u have on the card?
Edit: Run nandroid-mobile.sh via adb! error > http://forum.xda-developers.com/showthread.php?t=621940
Are you in recovery when you try the "adb remount" command? And u went thru the rooting process w/out any errors running the "adb push" and "adb shell" commands?
Edit: you can get su(#) by typing "su" after in shell ($)
Click to expand...
Click to collapse
That did it! Thank you Kyouko and Danknee!
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
juckeyy said:
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
Click to expand...
Click to collapse
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
gee2012 said:
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
Click to expand...
Click to collapse
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
gee2012 said:
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
Click to expand...
Click to collapse
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
gee2012 said:
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
Click to expand...
Click to collapse
Hmm, couldnt find my adapter. Is there no way to flash in the stock rom with odin?
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Hmm wow seems like a long process but i'll try it.
Thanks!
samersh72 said:
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
Click to expand...
Click to collapse
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
gee2012 said:
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
Click to expand...
Click to collapse
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
thank you my friend
Click to expand...
Click to collapse
Wait one minute bro.
samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
Click to expand...
Click to collapse
Hey when I type in adb devies it says mine is unauthorized :/
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
-Edit- also with usb debugging disabled the serialnumber is shown.in recovery.
juckeyy said:
Hey when I type in adb devies it says mine is unauthorized :/
Click to expand...
Click to collapse
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
gee2012 said:
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
Click to expand...
Click to collapse
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
samersh72 said:
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
Click to expand...
Click to collapse
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
juckeyy said:
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
Click to expand...
Click to collapse
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
samersh72 said:
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
Click to expand...
Click to collapse
I did still didnt work. Now I managed to get a ROM into my SD-card so now i'll boot custom recovery and try to install.
lets hope for the best!
Hey again!
Just wanna thank everybody for the help. I solved everything with flashing in stock ROM with odin.
I'll try again tomorrow with other ROM:s
Thanks, Joakim.
had same problem
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
fezz64 said:
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
Click to expand...
Click to collapse
Is it the same with other roms?
Make sure the download is not corrupted.
Wipe data, cache and dalvic after flashing the rom, reboot
sent from my Galaxy
I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler
What's up now ?
Sorted it out or still issues there ?
I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"
I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"
I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...
Hi everybody, 2 months ago I tried to encrypt my nexus using the security settings. When my n4 rebooted the touch stopped working. I couldn't use the recovery becouse the data partition was encrypted, so I used this tutorial (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060) to reset my phone. Now windows (neither ubuntu) do not recognize the n4. I tried to follow any kind of guide or tutorial i found but uselessly. I'm desperate, the recovery doesn't work, if i try ,it stop on android logo saying "no command". Entering in windows device manager (after i formatted my pc) the nexus is seen as "full jellybean on mako", i tested this driver (http://forum.xda-developers.com/nexus-4/help/phone-detected-jellybean-mako-install-t2411201) but the situation has not changed. I hope someone can help me.
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
PsyGik said:
Does your phone boot?
BTW, if you need only driver download from this thread: http://forum.xda-developers.com/nexus-4/general/drivers-nexus-4-driver-windows-t1992345
Click to expand...
Click to collapse
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
werba59 said:
It works perfectly, but I can't copy files on or change rom (now is running stock android 4.2)
Click to expand...
Click to collapse
Boot into bootloader and flash stock rom from here :https://developers.google.com/android/nexus/images
BTW, did you enable developer options?
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
werba59 said:
Sorry, I misread your answer. "It works perfectly" means that i can use it to call or whatever. Using the key combo (vol up+vol dw+power) it doesn't boot in download mode. I think it isn't a driver problem, something in my n4 went wrong. It boot only in fastboot mode and the recovery doesn't work.
Click to expand...
Click to collapse
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
Then open the downloaded image from here https://developers.google.com/android/nexus/images and Execute the flash-all script. This script installs the necessary bootloader, firmware,and system. Wait for a couple of minutes and then phone will reboot itself. After phone boots enable developer options in the phone and enable USB debugging.
If you are still not able to mount the storage in Ubuntu, you can install the mtpfs tool for Ubuntu.
Code:
sudo apt-get install mtp-tools mtpfs
sudo gedit /etc/udev/rules.d/51-android.rules
and in the 51-android.rules write the following:
Code:
#LG – Nexus 4
SUBSYSTEM==”usb”, ATTR{idVendor}==”1004?, MODE=”0666?
Then do:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
sudo service udev restart
sudo mkdir /media/nexus4
chmod 755 /media/nexus4
sudo mtpfs -o allow_other /media/nexus4
This should get it working. This thread tells everything in much more detail if you still didn't get it to work.
http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
werba59 said:
PsyGik said:
If it boots into Fast-boot/boot-loader then problem is solved right. Does your PC recognise your phone when it boots into fastboot mode? If yes then open up terminal and type:
Code:
fastboot oem unlock
My PC do not recognise my phone when it boots into fastboot mode, that's the problem, any pc and any kind of so i tested do not recognise my n4.
Click to expand...
Click to collapse
If no pc will recognize it it's probably your pc port on the device. Have you tried different cables too? It's pretty easy to replace or have replaced.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Seems like something going wrong with drivers, open the device manager on windows, plug in your phone (in fastboot) and uninstall the driver. Then use this http://www.koushikdutta.com/post/universal-adb-driver
Dunno what that full JB driver is about but it doesn't seem right.
You might have to repeat this process when phone is booted normally too if it won't connect via MTP
Hi, just get here after look in several forums.
my laptop can't recognize my n4, also tried in other two computers. i already updated the drivers, used a toolkit. what should i do next? the phone works good, just can't connect it to any pc. "USB device is not recognized"
as i said, already updated the drivers.
Anything else i can do?
Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory