hello
I have NTT DoCoMo P-07C
My phone just show NTT docomo logo when I try to trun on!
I need android rom for my foma P-07C panasonic phone
I am not in japan
please help me
thanks
msamessi said:
hello
I have NTT DoCoMo P-07C
My phone just show NTT docomo logo when I try to trun on!
I need android rom for my foma P-07C panasonic phone
I am not in japan
please help me
thanks
Click to expand...
Click to collapse
First try to connect it to pc via fastboot
Here are some drivers: View attachment P-07C_ADBdriver_v1.0.zip
thanks you
but how can I do this???what you mean by fastboot???
when I connect to pc nothing else to show!!!
I need rom to install android
what I can do with ADB!!!
fastboot is a small tool that comes with the Android SDK (software developer kit) that can be used to re-flash partitions on your device. It is an alternative to the recovery mode for doing installations and updates.
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode. In fact, it's frequently the preferred way to initially install the recovery image on many devices. Fastboot can also be used for developer operations like unlocking the bootloader of Google's Nexus devices.
Not all devices support fastboot, but many do.
There are two "sides" to using fastboot-- the computer side and the device side. Typically your device first is connected to your computer via a USB cable. Then you boot to the "fastboot mode" on the device. On your computer, you then run the fastboot tool to issue commands. Please note that fastboot commands will ONLY work while the device is in fastboot mode.
ADB ("adb"), or the Android Debug Bridge, is a development tool included with the Android SDK (Software Developer Kit), which allows for communication from an Android device (such as a phone or tablet) to a personal computer, and vice-versa. This communication can be made over a wifi connection. However more commonly, it is made via a USB cable. adb can also be used by developers for communicating from a computer to a virtual android machine that is also running on the computer.
adb is the "Swiss-army knife" of Android development. It provides numerous functions that can be accessed in detail via the command: adb --help
[SOURCE]
Using fast boot or adb you will be able in theory to fix the existing rom on your device.
The only rom that i have for you device is:
[FOTA rom update for NTT DoCoMo P-07C]
How to enter in Fcuking FASTBOOT .. is search the whole INTERNET
hello how to flash this set???????
Related
I have a Sony Xperia Z3 model D6653 with Android 4.4.4 build 23.0.1.A.1.49, I tried to unlock the boot loader at the Sony website, It went al right till the part when I need to run cmd at the platform-tools folder (from sdk bundle), when I write "fastboot devices" the cmd don't respond me with anything, it just appears another line to enter a command again
- Installed the Google USB Driver, Android 4.4W.2 and Android 4.4.2 SDKs (don't know why there is not for 4.4.4)
- USB Debugging Mode: ON
- Fastboot mode (blue led at the phone corner) successful
I think that this normally happens when the PC dont detect the device
I'm stuck at this phase, please someone help me, thanks!
docs.google
.com/file/d/0B31eiZiEHpNFMGgwVnBMWXBQVjQ/edit?pli=1
xda didn't allow me for posting a photo url so I put it separated
Use the minimal adb and fastboot set up, that's a lot easier
http://d-h.st/zwu
If nothing here works, get the flashtool drivers for the z3. Works like a charm. Also, you should probably TA backup, if you haven't already.
I think it didn't worked for me,the thing is that I need to unlock bootloader to put root in the device
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
https://drive.google.com/open?id=0B31eiZiEHpNFSnhzdGs1TU5pc00&authuser=0
dan_729 said:
I think it didn't worked for me,the thing is that I need to unlock bootloader to put root in the device
http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
https://drive.google.com/open?id=0B31eiZiEHpNFSnhzdGs1TU5pc00&authuser=0
Click to expand...
Click to collapse
You can root without unlocking.
Search XDA.
Hi. This is the original HTC EVO 4G that I got from Sprint.
Model PC36100
Android 2.3.5 with, I think, HTC Sense, though it doesn't say that.
Baseband version 2.15.00.01.15
Kernel version 2.6.36.10-g8b16b68 [email protected] #1 (9/4/12)
Build number 5.07.651.6 71ORD
My goal is to install basic stock Android on it. Whatever version will work, be stable, and run smoothly, support basic wifi, social media, email, camera.
It runs pretty nicely as is, really. But I imagine it'd be cleaner with basic android and not all the Sprint and HTC stuff on it.
I'm trying to unlock the bootloader using a Windows 10 PC.
I have tried various sources for the drivers. Currently trying HTC Sync for the drivers but have tried all the others.
What I'm observing currently is this: In DEVICE MANAGER, the phone when running in its normal Android mode, it shows up as ANDROID USB DEVICES > MY HTC. and it's running cleanly (no yellow exclamation point). IN that mode, I can open my COMMAND prompt and use ADB DEVICES and ADB finds the device HT06MHL01565.
In order to do the UNLOCK BOOTLOADER, you have to connect the phone to the PC in Fastboot mode. When the phone is on the Fastboot screen, Windows Device Manager, adds a yellow exclamation point to "MY HTC" device. At that point using the command ADB DEVICES yields no devices found. So I cannot proceed to FASTBOOT OEM GET_IDENTIFIER_TOKEN. Windows isn't seeing the device when it's in Fastboot mode.
I do have USB Debugging enabled and have tried it with Fastboot both checked and unchecked in the Settings >> Apps page of Android on the phone.
So, to recap, when the phone is in Fastboot, the PC doesn't correctly identify it and the ADB DEVICES command yields nothing.
Hi,
XDA Assist is here to help navigate the site, not for support... And see you found your way already... http://forum.xda-developers.com/showthread.php?p=63479581#post63479581
:good: So I will close this thread.
Good luck!
Power + Vol Down pressed together gets you access to the F1's limited recovery mode.
Power + Vol up does not get you into the bootloader.
When you connect the phone to your PC it automatically loads its USB drivers to the PC with your consent.
ADB can see the phone once the USB drivers are installed and the phone is connected via USB cable.
ADB DEVICES provides the serial number of your phone.
ADB REBOOT RECOVERY gets you into the recovery mode mentioned above.
ADB REBOOT BOOTLOADER simply reboots the phone.
FASTBOOT can't see anything.
FASTBOOT DEVICES doesn't yield serial number.
Other FASTBOOT commands sit "waiting for device".
So FASTBOOT just does nothing useful. A google search shows that this behavior is known and people think that using different drivers overcome the problem, but I tried a number of driver solutions with no success. I just think that they've closed the Oppo F1 up rather tightly.
-----
ETA: Just heard elsewhere from a semi-official source that FASTBOOT has been disabled on the F1.
I just saw this "Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016" from here > http://forum.xda-developers.com/r7-plus/help/decision-oppo-bootloader-fastboot-t3348114
If this is true, the F1f will be our last oppo. It's not a big issue for the F1f as it's my wife's phone but I will avoid locked phones on principle now. Even Huawei are making it hard to unlock bootloader so my Mate 7 could be our last Huawei.
Guys anybody tell how to flash 'magictricks' zip to unlock boot loader and to flash twrp recovery safely...
I'm week in commanding adb devices and fastboot so I need steps,help will be thankful.
Sent from my F1f using XDA-Developers mobile app
friends. I want to flash myphone (flash tool) windows 7 but do not see it. even I reinstalled windows 7, but did not see. last driver installed on the MTK what to do - I do not understand
agreed. another computer, another cable, another driver (for flash tool)
Hi,
I'm looking for some assistance to unbrick an Allview Viva P8 Pro tablet.
All this mess started from looking after some disk space to install more apps on on the default second partition.
First I've tried some tools like app2sd with no luck and finally decided to try adb/fastboot way, using a linux machine, to root the device.
Before starting the root procedure i was able to boot into recovery mode and while being into recovery mode I could see the tablet as a google device with the proper vendor id 0x18d1. Also "adb devices" command could find the device as expected. Right after issuing "adb restart bootloader", i cannot enter into recovery mode and it hangs with the logo displayed on the screen, i think it's a boot phase before entering into recovery mode.
I can still see it as usb attached device, not with google vendor id but identified as "Onda unverified", with vendor id 0x1f3a. Windows OS finds it as Android Bootloader Interface USB Developer and that's it. I've tried to install some drivers to establish communication but with no luck so far.
Thank you in advance.
iulian.popa said:
Hi,
I'm looking for some assistance to unbrick an Allview Viva P8 Pro tablet.
All this mess started from looking after some disk space to install more apps on on the default second partition.
First I've tried some tools like app2sd with no luck and finally decided to try adb/fastboot way, using a linux machine, to root the device.
Before starting the root procedure i was able to boot into recovery mode and while being into recovery mode I could see the tablet as a google device with the proper vendor id 0x18d1. Also "adb devices" command could find the device as expected. Right after issuing "adb restart bootloader", i cannot enter into recovery mode and it hangs with the logo displayed on the screen, i think it's a boot phase before entering into recovery mode.
I can still see it as usb attached device, not with google vendor id but identified as "Onda unverified", with vendor id 0x1f3a. Windows OS finds it as Android Bootloader Interface USB Developer and that's it. I've tried to install some drivers to establish communication but with no luck so far.
Thank you in advance.
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
Please consider posting your question here:
http://forum.xda-developers.com/android/help
You'll receive expert advice there.
Good luck!
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.