Related
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
omni_angel7 said:
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
Click to expand...
Click to collapse
If your on linux it's "./moto-fastboot" not just fastboot.
Windows 7 64 bit. sorry, should have specified.
Nobody with win 7 knowledge/advice?
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Diviance said:
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Click to expand...
Click to collapse
Thanks SO much for the quick response and all the effort I'd actually updating OTA from 1.26 because I flashed back, thinking no one was gonna help! Well, when I feel up to it another night. I'll give this another shot. Thanks for the custom fastboot, too!
i get < waiting for device >
did i do something wrong?
Me too. ^^^^^^^
I figured it out, i forgot to put it into fastboot mode!
did not work for me
when I do what you told the other guy it says system cant find the path specified couls you please help I have spent a couple of days trying different things and also when I try to erase the recovery installer file it want let me
OK so I put the BAMF Cubed Kernel on my phone and now I can't flash other kernels.
Many of us are having this problem, and I am having trouble installing new kernels when I try new ROMs.
Would someone please tell me step by step how to do this?
My understanding is that the boot.img file should be placed in the same folder on my PC as adb.exe, Fastboot, etc...
Is this correct? If so, what is the command line I should use to push the kernel to the phone?
Example: I want to try the new RezROM ICS from lllboredlll.
I downloaded the ROM, and have the zip on my phone's SD card. I also have it on my PC.
When I open it, I see a folder called Kernel. In that folder, there is a boot image. Also in that folder is a PH98IMG file containing a second boot image.
Which one is the correct kernel file to push via PC?
The way I understand it and have been doing it. Open up the zipped rom and you will see a boot image , extract or copy it to the folder that you have fastboot in . Then in Hboot..pull up a CMD box.. and either change location or if you have abd in your path.. the instructions are fastboot flash boot boot.img
then that should flash the kernel .. then boot to recovery ..wipe data/factory reset and then flash the rom .
BBEgo said:
OK so I put the BAMF Cubed Kernel on my phone and now I can't flash other kernels.
Many of us are having this problem, and I am having trouble installing new kernels when I try new ROMs.
Would someone please tell me step by step how to do this?
My understanding is that the boot.img file should be placed in the same folder on my PC as adb.exe, Fastboot, etc...
Is this correct? If so, what is the command line I should use to push the kernel to the phone?
Click to expand...
Click to collapse
Boot the phone into fastboot. Plug in the USB cable, open a CMD window on your computer. Set the current directory to the folder with adb.exe, fastboot.exe, and your new boot.img file.
enter the command:
fastboot flash boot boot.img
How come no one sets up their path to include the android-SDK folder with adv, fastboot...etc? I did and makes life so much easier since you never have to cd to anything to run those commands.
Sent from my ADR6425LVW using Tapatalk
Facts:
Laptop connected to my phone uses Ubuntu linux
Unlocked my Amaze successfully
I have the RecoveryInstallerForNoobs2.0
I have chmod'ed all the pertient files to be executable
With phone in fastboot mode, doing 'sudo ./fastboot devices' returns the serial number
Problem:
'sudo ./Flash.sh' returns the following output:
./Flash.sh: 1: adb: not found
: not found 2:
Additional facts:
I am a n00b and I am aware my life's output at age 32 is dismal
I have read the "read first for linux..." thread, "how to root" thread and the "faq before posting" thread
I have searched the site but possibly not hard enough, ergo my own impudent thread
What to do??
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Double0EK said:
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Click to expand...
Click to collapse
what he said turn on debugging on your phone. also make sure the zip file is unzipped into a folder
Debugging is on in the settings and the recovery for noobs zip is unzipped.
I flashed mine manually using the fastboot command...
But I only know how to do it with a windows machine.
Put the recovery.img in your AndroidSDK/tools folder , open cmd , cd to the tools folder and type "fastboot flash recovery recovery.img" being if you renamed it to recovery.img..(if it wasn't renamed then you need to type the name of the recovery img.)
Sent by accident from my Amaze using Tapatalk
ryurage said:
Debugging is on in the settings and the recovery for noobs zip is unzipped.
Click to expand...
Click to collapse
don't go to fastboot, the script should automatically kill and restart the adb shell...just turn on your phone and run flash.sh... if that doesn't work Rename the shellscript from flash.sh to flash.command, then associate it with Terminal.app
let me know if those work, if not, I've got some other tricks but it's a little bit more complicated.
@seansk, I renamed the file and tried it with the same resulted output:
./flash.command: 1: adb: not found
: not foundmand: 2:
Btw, I run the flash script one of two ways, 1. sudo ./flash.command or 2. bash flash.command
I could be wrong but I think the issue possibly lies in the script:
adb kill-serveradb reboot bootloaderfastboot flash recovery recovery-cwm-ruby-5.0.2.7.imgfastboot rebootexit
Perhaps adb has to be in my PATH? I'm open to other suggestions too.
One more thought, assuming the adb daemon is shut down, maybe this command would do it: 'sudo ./fastboot flash recovery recovery-cwm-ruby-5.0.2.7.img'?
hmm that thing has been up for months...I've only had two people having trouble and havn't heard back from the other guy...so I hope there's nothing wrong with the scrip...I will look into it again...unfortuantely my vitual machine for mac is down right now, don't know when I'll get it back up and running...
try these
1)To start the shell-script 'file.sh':
sh file.sh
bash file.sh
2)Another option is set executable permission using chmod command:
chmod +x file.sh
Now run .sh file as follows:
./file.sh
ultimately if you have a windows computer it would be much easier...or if you can also here's the new recovery from xboarder I havn't updated this zip file yet... you can edit the recovery script to change the name to this file name: recovery-cwm-ruby-5.5.0.4.img
if all else fails follow the second method here from xboarder (you need an sd card): http://forum.xda-developers.com/showthread.php?t=1316855
Download file to your computer
2. make sure its named PH85IMG.zip
3. Copy to sdcard (external one) then restart your phone in fastboot, by holding down the volume down and power.
4. Wait for it to say do you want to update (press volume up)
5. Press power button to reboot
6. Reboot Phone into recovery as normal and enjoy clockworkmod recovery with fixed charging and sdcard
Please Help!
I did something very stupid today.
Unlocked my RMX2170, got into fastboot.
Tried to flash PBRP as recovery, and some vbmeta.img image as vbmeta of my phone.
Disaster! My phone got stuck in a bootloop of just repeatedly booting into fastboot.
No recovery, nothing.
From there, I installed SHRP using the fasboot flash recovery command, and now I have SHRP.
SHRP, however, cannot flash ANYTHING as a result of an error that it "failed to mount /system_root and /vendor"
The phone can effectively boot into Qualcomm EDL and fastboot.
I've tried countless tools and software to get back to stock. Nothing works. MSM requires a login to function, so it won't work.
Anyone at all, please, can you tell me how to get back to FULL stock?
Through sheer trial and error,
Procedure:
1. Downloaded A37 ofp file from www.gsmmafia.com/realme-7-pro-rmx2170-flash-file/ (or mediafire download)
2. Extracted it using bkerler/oppo_decrypt's ofp_qc_extract.py into a folder:
Code:
py -3 -m pip install -r requirements.txt
py -3 ofp_qc_extract.py a37_ofp_file.ofp .\extracted
3. Rebooted the phone into fastboot, ready for flashing (Power + Volume Down for me)
5. Ran:
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
(keep in mind these .img files came from the extracted ofp's folder!)
6. Rebooted into system using the fastboot menu (START)
7. I'm pretty sure my phone ran A41 before today... so I gave the phone an update from inside Android, that seemed to work fine.
As a bonus, my bootloader seems to have remained unlocked? Nice!
Also interesting: holding volume up does not boot into recovery. This is an issue for another day lads.
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Domac5 said:
Can you explain me step 2? I have bootloped phone and I don't understand how to use oppo decrypt
Click to expand...
Click to collapse
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Codian said:
1. Download and install Python on your computer.
2. Press Windows + R, then type cmd, hit enter to access a terminal.
3. Make sure Python works by trying py -3 in the terminal. (Type exit() to exit the Python shell)
4. Download oppo_decrypt's repository zip and extract it in a folder anywhere.
5. Use cd in the terminal to navigate to the extracted folder.
6. Run this command to install the dependencies of oppo_decrypt:
Bash:
py -3 -m pip install -r requirements.txt
7. You should have already downloaded the ofp file for the phone. If not, get it from here.
8. You need to run the Python script in order to extract the images you need, so, you should copy it to the folder where your ofp file is.
Bash:
cp ofp_qc_decrypt.py /where/the/ofp/file/is/ofp_qc_decrypt.py
9. Go into the directory with the script and ofp file, and extract it.
Bash:
py -3 ofp_qc_extract.py the_ofp_file.ofp .\extracted
The extracted images you need, if you were on Android 10, should be in the extracted folder in the terminal's working directory.
Best of luck, although I can't really help you step-by-step for everything, so I suggest you visit r/realme's Discord.
Go to the Discord for more help!
Click to expand...
Click to collapse
Step 8 not working for me
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Domac5 said:
Step 8 not working for me
Click to expand...
Click to collapse
Sorry, instead of "cp" the command is "copy", my mistake.
Domac5 said:
Do you have original recovery.img file,please send me? I just can't extract it from ofp file, 2 days trying and just can't
Click to expand...
Click to collapse
You can't flash recovery.img. It won't work, I tried. You need to re-flash all of the system partitions like in my post.
I don't have the files anymore, as I did this a while ago. Sorry.
Codian said:
Sorry, instead of "cp" the command is "copy", my mistake.
Click to expand...
Click to collapse
Still doesnt work
I did it, problem was in python3 comand, that one should be typed without number 3 because that doesn't work in windows. Now it's extracting
did you had these problem?