Hello guys. I am learning developmental things, i am experimenting with my phone to learn new things. I am learning a lot from searching but certain things i think i dont know the proper keyword to use. I ve been stuck without the answer for a long time. So i thought i would ask here
I had motorola defy before my xperia z. Defy had something called bootmenu which let me switch on adb while booting a ROM. Now i have xperia z, its bootloader unlocked, a rom cooked by my own which is in bootloop. It doesnt have bootmenu to do like i did for defy. How do i switch on adb from the phone's side? I have setup adb perfectly on my computer.
My ROM goes into bootanimation but adb doesnt seem to be switched on in the phone' side.
when i type "adb logcat log" it is stuck at "waiting for device " while the bootanimation goes on into bootloop
i will answer this myself
1. There is always no problem with your phone if the device has got past the bootlogo and entered the boot animation
2. If adb doesnt detect the device,use latest adb from sdk tools
3.If it says unauthorized/offline then enable access to the computer or disable adb secure
Related
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.
I'm trying my hand at porting a ROM to my device (S4 HTC One X/XL, Evita) and I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point. I've made sure drivers are installed and used multiple USB ports. ADB works in recovery and fastboot works in fastboot, but adb returns Offline when I run adb devices while the phone is sitting at the bootscreen.
Found this on StackExchange: http://android.stackexchange.com/que...-for-debugging
According to some of the replies, it's possible to use adb at boot, so I'm not sure why adb returns offline. I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Power on the phone then cross your fingers if all goes well you should capture the logcat to bootlog.txt file in your temp directory.
Code:
adb -d logcat>c:\temp\bootlog.txt
Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
AuSSiELaMbChOpS said:
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Click to expand...
Click to collapse
Protogon said:
I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Click to expand...
Click to collapse
The ROM is 4.2.1-based, so if the USB Debug Whitelist was implemented in that version, that might be the problem. Running adb logcat from power off with a ROM that boots fine reveals that adb starts pretty much as soon as the bootscreen comes on and logcat should start spitting out data just as quickly.
If it's not a whitelist issue, something is preventing even adb from starting on the phone.
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
RickyGoldsmith said:
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
Click to expand...
Click to collapse
Replying to self.
You need to modify the init shipped on your OS and instruct it to start adbd asap.
Protogon said:
I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point.
Click to expand...
Click to collapse
You can try to reboot into a working system right after (e.g. the recovery) and retrieve the last kernel boot messages by:
adb shell cat /proc/last_kmsg > last_kmsg
and then see whether you can figure out what happens by reading this log file
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
Welcome dear xda_dev user,
Model:Prestigio Multiphone 5451 DUO
My device in the past months stuck in a boot-loop, and.. I googled for loads of threads to read,but they don't really help.
This is what the phone do, and not do:
Can/Works:
ADB sideload (PC see the device!)
Stock Recovery Menu
Can turn off/on the device,screen vibration,etc. works.
No/Not Works:
Can't listen to ADB while booting.
NO TWRP and other Recovery menus installed, only the stock android one.
NO official ROMs available from this company.
Click to expand...
Click to collapse
This is what I tried:
Tried to load 1-5Mb "firmware" updates via ADB Sideload /throwing permission problems/
Tried to Wipe data/cache /didn't boot after this/
Tried to unplug battery <- make it 0% (uncharge)
Tried to load non-company driven ROMs via ADB /permission problems/
Click to expand...
Click to collapse
NO official ROMs available from this company, I asked them to share, but they said I need to go a city (200km) away from me who have "authorized access"..
I kept this thread as simple as possible, BTW I have bought a new device, I still need this mobile because it still worth $50 I think..
Thank you if you can help, and ignore the grammar problems.
Not sure if these are legit firmware files for the duo but seeing you are in this fix it is worth a look i think
https://androidmm6.com/deviceinfo_1701.html
http://www.needrom.com/download/prestigio-pap-5451-duo/
Probably Scam/fake.
The file (rar) is locked via password and it's nowhere published, and it's only 1.65Mb so not really a ROM.
Anyways, I star you up for first and probably last replyer.
If you are able to sideload , then i think you can recover your phone in no time.
First I need you need to know that this procedure is complicated but You can recover your device.
go to mtkroms.com and Download any rom from there as per your wish.
-Remove boot.img from zip file and save it else where
-Sideload the rom
-After sideloading ,reboot device into fastboot by pressing power and both volume keys together until Boot Menu appears where you have the choice to Normal Boot , Boot into Fastboot(Bootloader) and Boot into recovery.
-Use Volume Down to navigate to Fastboot and press Volume Up (or Power button in some devices)
-After booting into fastboot , extract boot.img from .zip file to C:
-type in , fastboot flash boot "C:\boot.img"
-type fastboot reboot
If you are lucky , your device might boot (very slight chance to actually boot)
If it doesnt , no issues , this is where you show your skills as rom porter xD
You wont have access to Android OS , but after dalvik cache has been build , access to adb will be granted.
In the same above mentioned website , there is a tool which can port cwm for any mediatek device.
Download it in your PC , PC should not be windows 10 , Compatibility mode wont work.
Make sure you have Drivers necessary to proceed.
Use the tool and Click automatic porting and follow on screen option to Complete Porting recovery , once the recovery has been ported , reboot into recovery.
Now you will have complete access to adb without any problem.
Once you have a proper working recovery , with adb shell , do the following,
Code:
-adb shell
-df
-cat /proc/partitions
Once you have access to the mount points , you can start DeCompiling kernel and do the necessary changes in fstab
To decompile kernel , there are many tools for Windows and Linux
Google it , if you have any problem , PM me or reply back , I'll be happy to assist you
Hi,
I got update for my htc nexus 9(7.1 Update). It automatically updated and when i woke up the phone was bricked.Its in welcome screen and touch isnt working at all. volume,Power keys are working.
So i tried to unlock the bootloader and flash a new rom.
Note: device isnt rooted.Oem is not unlocked and usb debugging not enabled in developer option.
contacted htc service centre but its of no use.they wont service tabs and they dont even touch usa products.
Tried different videos.Downloaded rom,recovery and installed fastboot and adb drivers in my pc.
when i try using the command prompt, its showing under fastboot devices but it isnt showing under adb devices.
adb is showing the commands,but no adb command is working for the device.
Need help in unlocking bootloader and installing custom rom.
Am not a pro or a coder. I just root for fun. dont have any knowledge about these things.
So someone please guide me in solving the issue.
Hello sir. Sorry to hear about your device.
First adb doesn't work in fastboot. Everything is well fastboot
My advice to you is Dw about any of that. Run over to a really helpful guy, called wugfresh. He has a hole tool kit. I use it all the time it's excellent. It should sort you out no problem . If it doesn't give me a shout and I'll see if I can be of assistance
braga94 said:
Hi,
I got update for my htc nexus 9(7.1 Update). It automatically updated and when i woke up the phone was bricked.Its in welcome screen and touch isnt working at all. volume,Power keys are working.
So i tried to unlock the bootloader and flash a new rom.
Note: device isnt rooted.Oem is not unlocked and usb debugging not enabled in developer option.
contacted htc service centre but its of no use.they wont service tabs and they dont even touch usa products.
Tried different videos.Downloaded rom,recovery and installed fastboot and adb drivers in my pc.
when i try using the command prompt, its showing under fastboot devices but it isnt showing under adb devices.
adb is showing the commands,but no adb command is working for the device.
Need help in unlocking bootloader and installing custom rom.
Am not a pro or a coder. I just root for fun. dont have any knowledge about these things.
So someone please guide me in solving the issue.
Click to expand...
Click to collapse
you can try flashing the full OTA update
then do a factory reset.
https://developers.google.com/android/ota
1. boot into recovery
2. adb sideload "location of the OTA"
3. reboot into recovery
4. factory reset