Related
Hi! I was trying to backup my Orange Monte Carlo following a Portuguese tutorial but I'm stuck in the middle and I've got no help! Hope you can provide some! These are the steps I followed (translated)
1 - Install ADB Made Easy;
2 - Open cmd;
3 - Activate cellphone debug mode;
4 - Connect via usb (without mass storage) and install drivers if request [it was requested and i installed];
5 - Run adb devices, it should show your device [it did];
6 - Run adb reboot bootloader, your cellphone will boot in Fastboot, wich is an Android image without menus [correct until here];
7 - Run fastboot devices, your device yor a question mark(?) should show up (advance to next step), else you miss drivers [step not completed];
cmd says 'fastboot' is not recognized as a command. Now my phone is stuck connected to the computer with an adriod pick and I have no clue on what to do next!
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
shanman-2 said:
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
Click to expand...
Click to collapse
Thank you! Do you have any idea why the last command doesn't work? I believe it has something to do with file location... I'm trying to backup my Monte Carlo. Next steps were to "fastboot boot recovery.img" and then backup.
It should be in the platform-tools directory of the android-sdk. Verify that it's there...if so cd to that directory and it should work
I already fixed it for myself, thanks! Now I can't seem to be able to install clockwork!
Doing <<fastboot boot "C:\Users\R&J\Downloads\recovery.img">> reboots the device but doesn't enter recovery.
Doing <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> , <<fastboot reboot>> and <<adb wait-for-device reboot recovery>> results the phone entering android's default recovery (no acess to backup feature).
Any way to help? Thank you!
The first command <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> is trying to write the recovery.img you downloaded to a recovery partition on your device. It may not be overwriting the original recovery.
try changing permissions by doing
adb shell
su
chmod 777 /recovery
then try to flash again
Lol it seems like I have been luck enough to solve my own problems, I have sucessfully installed ClockworkMod Recovery 4.0.1.4 unofficial MoDaCo Edition using a bat file . Now I can't seem to find a way to flash recovery back to stock. I though this was an option inside the modded recovery. Any tips? Thanks again!
EDIT: I have the stock recovery file . God... this tutorials I'm folowing aren't that noob friendly...
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.
So if I got this right if I have busybox already I only have to do is step 7.
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Step 4, a quicker way: adb shell su , get you into shell as root right away
AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.
Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.
Updated with a link to another good tutorial about pushing ROMs to the phone
Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!
AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps
Dude add S3 stock recovery please.
Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.
Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?
vI Ragnarok Iv said:
Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?
Click to expand...
Click to collapse
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.
simms22 said:
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.
Click to expand...
Click to collapse
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!
vI Ragnarok Iv said:
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!
Click to expand...
Click to collapse
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.
exb0 said:
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.
Click to expand...
Click to collapse
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/
vI Ragnarok Iv said:
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/
Click to expand...
Click to collapse
Oh, that was probably a driver issue. No worries, you can always get into android, transfer the custom rom into your SD card, boot into recovery, wipe and flash if you want to try out a custom rom.
Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon
Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a
I accidentally formatted all partition and now only have a TWRP. The TWRP only shows the start screen when i go to recovery.
Adb devices show me the device detected. I did a adb push and moved the stock rom 5.1.11 and my twrp recovery to the sdcard using the command adb push. I am struck here because i cannot get to the twrp screen which gives you option to install/wipe etc.
Can somebody please guide me if there is a way to recover or install the .zip files I have copied to sdcard. Thanks in advance
You need to fastboot flash the default stock rom, and then re root/install TWRP etc etc
Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.
SachinGopal said:
Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.
Click to expand...
Click to collapse
You need to go to this thread... https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Download the version of OOS you want (5.1.11) and unzip the contents in to a folder and run the flash-all.bat file and let it install to all partitions. Just follow this instructions in the thread and you will be fine.
Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
Thank you so much it worked when I tried. Grateful . Will donate the Dev for that bat script.
SachinGopal said:
Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
Click to expand...
Click to collapse
You need to be in fastboot mode.
Either adb reboot bootloader from inside android or from a powered off phone, hold Volume Up and power on.