Related
please help me I got in my phone custom recovery 1.2.1 but when I go to the backup/restore and select nand restore it asks me : Create Nandroid backup? ... and when i confirm it: it says: Performing backup............... and after some minutes: Error : Run "nandroid-mobile.sh" via adb!. help me! and one more thing when i try to connect my phone to pc via adb shell it cannot "find device"
xperiment914 said:
please help me I got in my phone custom recovery 1.2.1 but when I go to the backup/restore and select nand restore it asks me : Create Nandroid backup? ... and when i confirm it: it says: Performing backup............... and after some minutes: Error : Run "nandroid-mobile.sh" via adb!. help me! and one more thing when i try to connect my phone to pc via adb shell it cannot "find device"
Click to expand...
Click to collapse
the problem lies in the recovery itself 1.2.1 has backup prob so try 1.2 or earlier which works smooth for backup or rather clockwork just chk this thread http://forum.xda-developers.com/showthread.php?t=1038338
all files provided in 1 link easy to find just download and off you go
xperiment914 said:
please help me I got in my phone custom recovery 1.2.1 but when I go to the backup/restore and select nand restore it asks me : Create Nandroid backup? ... and when i confirm it: it says: Performing backup............... and after some minutes: Error : Run "nandroid-mobile.sh" via adb!. help me! and one more thing when i try to connect my phone to pc via adb shell it cannot "find device"
Click to expand...
Click to collapse
hi there.
what's happening is that you probably need to "re-wipe" your phone. that happened to me yesterday. The 'recovery menu' doesn't clean things very well on P500, so usually i don't rely on it and prefer to use ADB
So, connect the phone to the PC and follow the usual procedure to manually clean the /system folder. If you don't know exactly how it's done, search for "adb clean" or something like that.
On (very) short terms:
- get Android SDK (browse for it on google)
- boot your phone into recovery mode
- connect usb
- run 'adb start-server' or 'adb devices' (usually the 2nd does the start server automatically)
- run 'adb shell'
- run the command 'rm -rf /system/*
- run 'exit'
You can also clean your dalvik cache. I would strongly advise you, if you use the EXT4 partition, to clean it up too.
Since I use Linux, i'm not very aware of how it's done in Windows, but mainly, I backup the EXT4 partition into a folder in my computer, then i clean it up - i think you can clean it with adb too, by mounting it with 'mount -a' - it requires some linux basic commands and i guess you will find a better tutorial around.
Thank you clockwork mode Works perfectly
Sent from my LG-P500 using XDA App
Ok so I was trying to install a custom recovery on my P500 and when it turned on it gave me this message
fast boot mode started
udc_start
Click to expand...
Click to collapse
I plug it in it gives me
fast boot mode started
--suspend--
--reset--
--port/change--
--reset--
--port/change--
Click to expand...
Click to collapse
I tried out this method: http://forum.xda-developers.com/showthread.php?t=1088046
After keying the fastboot commands in it says <waiting for device>. Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
I'm still on my stock ROM (untouched), phone is rooted (duh) and this is my first attempt to install a custom recovery.
Not allowed to post on that thread ofc, my first post here. All help greatly appreciated. Thanks
Here is the Simple way ..try it
this link for latest working Rom >>
http://forum.xda-developers.com/showthread.php?t=946354
how to root >>
Enable USB debugging on your phone by going to Settings –> Applications –> Development. Check the ‘USB Debugging’ option.
Make sure you have a SD card inserted and mounted in your phone (Don’t know if it’s necessary but before proceeding further I formatted my SD card after taking a backup of the data in it. Why take a risk? Smile)
Download the GingerBreak APK from XDA Developers and get it onto your phone.
Install it by browsing to the GingerBreak APK in any file manager.
Open GingerBreak from your app drawer and press the root button.
Wait for a few minutes. If there are no problems, the device will reboot itself. (The reboot will take quite some time.)
You will see a SuperUser app in your app drawer after the reboot. Open it and see if it is working.
You now have a rooted Optimus One P500 phone.
Now install custom recovery
Follow the below steps to install custom recovery on your LG Optimus One P500.
Install Android Terminal Emulator from Android Market.
Download the file "amon_ra_recovery_installer.zip" from here or here.
Check the MD5 hash value of the downloaded ‘zip’ file. You can use HashTab to do this. Right click on the downloaded file and ensure the MD5 matches 86db8a52b01f049cadb8f097a4c5bd9e.
Extract the contents of the ‘zip’ file to the root of the SD card (Don’t extract inside any folder. For example if your SD Card is mounted on J: in Microsoft Windows then the four extracted files should be right under J:/ like J:/flash_image)
Open the terminal emulator app on your phone and type ‘su’ without the quotes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions for the terminal emulator app. Click ‘Allow’ and proceed. The shell prompt will change from the previous user shell ‘$’ to root shell ‘#’ in the emulator.
Now type in the following command and press Enter. The custom recovery will be flashed on to your phone and it will reboot into Custom Recovery.
sh /sdcard/rf.sh
Shut down your phone and boot into Recovery using the Volume Down, Home and Power switch keys. You can move through the options using the volume up/down keys. Use the Menu button to select the option.
In the recovery menu, select Backup/Restore, then select Nand backup. What this will do is backup your current ROM on your SD card, if something goes wrong while flashing the new ROM you can simply boot into recovery and restore your previous ROM.
Connect the phone to your computer and inside Recovery main menu click the option ‘USB-MS toggle’ and then ‘USB-MS Toggle SDCard’. This will unmount the SD card so that you can see it in your computer. Backup everything from your SD Card. Eject from computer and toggle USB again from recovery to mount the SD card back in phone.
Though it is not a necessity for this ROM, I would suggest partitioning your SD card to create swap and ext partitions. The ext partition will come in use if you want to install apps onto your SD card later. This is different from what you see in Froyo versions of Move to SD option. Partitioning will format your SD card, so make sure you backup your SD card as mentioned in Step 3.
Go back to the recovery menu again and select ‘Partition sdcard’. Then select ‘Partition SD’. Create a swap partition of size 0 and ext partition of size 512. Once done hit Back to go again to the ‘Partition sdcard’ menu. Convert the partition you just created to ext 3 and then ext4 using the options ‘SD:ext2 to ext3’ and ‘SD:ext3 to ext4’.
Toggle USB from recovery again. Inside the SDcard create a folder AAA and copy the ROM you downloaded in Step 1 into the folder ‘AAA’ on your SDCard. Once done, eject the SD card and toggle USB again to mount the SD Card in the phone again.
Go to the Wipe option in the recovery menu and wipe userdata, /data, /sd-ext, /sdcard/.android_secure, /cache, ‘Dalvik-cache’
Then go to the Flash Zip option in the recovery menu and select the zip file you copied in Step 6.
Sit back and relax while the zip is flashed. Once recovery shows that flashing is complete, reboot phone from recovery. The first boot will take quite some time.
Enjoy Gingerbread 2.3 on your LG Optimus One P500.
@ above completely unrelated to his problem.
Sent from my LG Optimus One P500 using XDA App
Appreciate your post but it has nothing to do with query sadly.
I was doing what you've mentioned in the installing recovery section when things went wrong.
I run Win7 x64 btw.
istoner said:
Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
Click to expand...
Click to collapse
That is correct - drivers issue.
1/ Add DEVMGR_SHOW_NONPRESENT_DEVICES to your environment on Windows and set the value to 1. (In Advanced system settings, Google if you do not know how.) Log off and log back on.
2/ Run devmgmt.msc
3/ There, View - Show hidden devices
4/ Go thru it and uninstall everything Android-related (for starters, ADB Interface and stuff under it, Disk drives, Modems, Ports (COM and LPT), USB controllers - might not be complete list above)
5/ Reboot the PC.
6/ Install the latest drivers for your phone.
7/ If it worked, once you have plugged in the phone stuck in fastboot mode, in device manager you should see Fastboot interface (Google USB ID) in ADB Interface section.
Thanks, trying that out now.
doktornator,
Thanks a bunch. It was an issue with the drivers, I tried your method a few times with little success. Then I let Windows find the drivers (out of all the things), and that worked. Relieved and slightly embarrassed that Windows could what I couldn't
Good that it works now. Fingers crossed to unbrick your phone soon.
Oh it's unbricked and ready to go again lol.
Hi, I am on Windows XP with the exact same problem.
Have tried the B2CApp for driver updates with no luck. Tried windows automatic driver installation,again no luck.
Anything else that I could try on a Win XP machine?
UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
droidao said:
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
Click to expand...
Click to collapse
is the name of the .img file recovery.img?
the command is really fastboot flash recovery (name of file).img
Yes it is...Actually I tried both ways (renaming and keeping the original name)! But I've finally figured it out!!! Here was the problem: when I installed android sdk I added the paths of the required directories (tools and platform-tools) to the system variable section so I could launch tools without writing the path all the time...However, because desperate times call for desperate (and often silly) measures, I decided to type the command cd "name-of-directory" anyway and that...made the trick.
This community is indeed great...I'm going to distribute some "thankyous" now!
I had the same problem with Win7, Updating the drivers from the device manager of w7 worked for me. Hope it helps.
Ps: will take around 15 mins updating.
Hi,
I do have one Android 4.4.4 device, rooted, with custom apps, I now want to clone to another 20+ devices.
I found lots of instructions, but all require at least adb support on each target device to upload the backup files which then can be flashed using CWM/TWRP. This requires me to complete the setup wizard on each device and enable developer options, which I don't wanna do, if not necessary.
Isn't there a way to create a system.img / data.img (instead of tar-files generated by CWM/TWRP) I can just flash to each device using fastboot?
HowTo and Problems with TWRP:
1.1) boot device into bootloader
1.2) boot TWRP temporary from fastboot (e.g. using NRT)
1.3) create backup
1.4) reboot device normally
1.5) copy /TWRP from media (Windows Explorer)
2.1) boot new device normally (Setup Wizzard)
2.2) copy /TWRP to media (Windows Explorer)
2.3) power off device
2.4) boot into bootloader
2.5) boot TWRP temporary from fastboot (e.g. using NRT)
2.6) create backup (just bootloader, backup is just to create valid backup path)
2.7) use TWRP filemanager to move /data/media/0/TWRP/serial_master_device/backup_name to /data/media/0/TWRP/serial_current_device
2.8) restore backup with TWRP
Steps 2.6 and 2.7 are total waste of time but necessary because of TWRP limiting the valid backup path to the devices serial number... why?!
HowTo and Problems with CWM:
1.1) boot device into bootloader
1.2) boot CWM temporary from fastboot (e.g. using NRT)
1.3) create backup
1.4) reboot device normally
1.5) copy /data/media/clockworkmod from device using "adb pull /data/media/clockworkmod" because backups won't show up in Windows Explorer (because that is /data/media/0/clockworkmod)
2.1) boot new device normally (Setup Wizzard)
2.2) copy /clockworkmod to media (Windows Explorer)
2.3) power off device
2.4) boot into bootloader
2.5) boot CWM temporary from fastboot (e.g. using NRT)
2.6) get stuck here because CWM will not recognize any backup in /data/media/0/clockworkmod
So... I'll keep using TWRP, which is pain in the ass, but at least, it does work...
Any ideas how to speed up the process?
Hey xda members,
My name is Pierre, from France and new owner of X820 version 6GB 64GB (from Aliexpress).
I made a big mistake yesterday, wiping from TWRP all data (Sytem, applications etc.)
Now if I put "ON" again, it is just showing "EUI" logo, without end
I have still access to TWRP but no backup, not .img loaded in the phone.
I can't connect and load from USB the ROM, so I am honestly lost.
If you have just any idea,how to solve it! Please let me know
Thank you very much, and good evening,
TWRP has a backup solution for you. I did this same misstake like you.
In Advanced settings you can run ADB SIDELOAD.
I hope you have proper ADB drivers in your PC and command prompt in Windows is your friend.
With ADB SIDELOAD you can install ROM from your PC via USB to your bricked phone. ADB uses whole base of commands to control what you can do.
Follow this steps:
https://forum.xda-developers.com/showthread.php?t=2318497
Twrp also supports MTP so you should also be able to copy a rom on the sdcard when in twrp.
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Thank you Razor, mikey and cr3pt !
If I am not mistaken, you provide me: 2 different solutions (ADB Sileload or abd push ROM).
It does mean, if I select the "one more easy" :
1. I boot in TWRP my phone
2. connect by USB (ADB drivers must be installed). Usually it is written MTP or "Android" but I can't see the external drive in Win10.
3 Then adb push rom_file.zip /sdcard in the Wincommand
4. wait and after disconnect USB
Then I will find the ROM to install in my phone.
Is it correct?
Yes
If you have TWRP, connect the phone to your computer, mount storage in TWRP, copy the rom of your choice, and install it. That simple
Sent from my Le X821 using Tapatalk
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
kanagawaben said:
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
Click to expand...
Click to collapse
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
install ADB, all necessary drivers. without that you can only dream about correct fix'a
piyerre said:
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
Click to expand...
Click to collapse
I'd try to start again clean. First completely remove adb and android device drivers from your computer. Then boot your phone into TWRP and connect it by usb to your computer and see if it auto installs the right drivers. If not, I guess you have to find where to download them from to install manually.
cr3pt said:
install ADB, all necessary drivers. without that you can only dream about correct fix'a
Click to expand...
Click to collapse
Can you give me please a link with the correct ADB and the correct drivers.?
I can't see the external drive even if adb devices gives me OK result.
Thank you,
you don't need external drive - correct is adb device. just push file when is visible in device manager
Hello !
It does work perfect, I finally use the "adb push" function!
Thank you very much all
cr3pt said:
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Click to expand...
Click to collapse
It works! Thank you very very much!
Bro Its is new security added in windows 10... U can only install official and signed drivers in windows 10.. U should turn it off.. only then u can access adb and fastboot...
One more thing bro...
If u have lost every thing, but u r able to boot in twrp, then follow me:
1. Download any rom for le max 2 U want to
2. After downloading,copy it in ur pendrive
3.Boot in twrp
4.connect the pendrive to ur device using OTG adapter
5.Mount USB storage
6.wipe every thing again.
7.After installation,reboot
8.first boot may take time and then wgwghrussuwgskaaiiawg (U know the rest??)
I have tried to revert back my Oneplus from Nougat based ROM and custom kernel to the last Oxygen OS. I am using TWRP 3.1.1-0. I have downloaded and transferred the zip file containing Oxygen OS to the Downloads section and I have wiped, the cache and the system partition without making a backup and when I have tried to install the Oxygen OS it reports that: "Updater process ended with ERROR:7. Error installing zip file" . I have connected the phone to an USB cable but it doesn't appear as an external drive in My Computer so I am unable to transfer some old backup I have on my PC. I have tried to boot into bootloader and execute adb devices, but it is not recognized there as well. As a matter of fact when I have booted into the bootloader my PC installed some drivers and now the phone appears in Devices and Printers and is listed as Android as Unspecified category, but not present again under My Computer. Is this normal? What can I do to recover my device? How can I transfer some files between my PC and the phone?