Database Develop

Accidentally formatted sdcard prior to flashing

Hey guys, I need some help here
I accidentally formatted the sdcard when preparing a clean flash. I also formatted system ect. so now all I can do is boot into recovery but no files to flash.
Is there some way I can transfer files to the sdcard og another way to get the device working again?
Thanks in advance.

You are softbricked. Restore factory image using wugfresh
http://www.wugfresh.com/nrt/

Download the factory images, boot into bootloader (not recovery) by holding power+down, then flash the factory images.

I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done?

codemonkey85 said:
I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done?
Click to expand...
Click to collapse
Give the exact steps and exact messages, cut and paste is best, otherwise there is not enough info to go on.

I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.)
I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder.
I type: fastboot devices
I get: 015d25687443fe0f fastboot
I type: fastboot flash bootloader bootloader-grouper-4.13.img
I get: FAILED (command write failed (Unknown error))
I type: fastboot -w update image-nakasi-jop40c.zip
I get: FAILED (command write failed (Unknown error))

Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now.

Im unable to turn on USB debugging, cause i have no ROM. What to do?

codemonkey85 said:
I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.)
I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder.
I type: fastboot devices
I get: 015d25687443fe0f fastboot
I type: fastboot flash bootloader bootloader-grouper-4.13.img
I get: FAILED (command write failed (Unknown error))
I type: fastboot -w update image-nakasi-jop40c.zip
I get: FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
exactly the same error im getting.. how did you solve it?

Tried again on another USB port and now it worked.
Thanks for the help guys.

codemonkey85 said:
Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now.
Click to expand...
Click to collapse
Out of interest why didn't you just run the small script that comes with the factory image to wipe and reflash everything.
It's what I did to make sure I had a nice clean install.
Or were you trying to keep some data from /data for example.

tried to install JB, used Blackrose = can't get into recovery

Hello Folks,
I'm still stuck with my nexus one since I don't care that much about phones.
I've seen that jelly bean roms have made a significant progress. Thus I decided to give it a shot.
I started with installing adb and fastboot. :good: After that I rooted the nexus one :good: I've used this how to:
c2med blog, can't post links...
Next, I ran blackrose. :good: I saved the rom on the micro sd. Having done all the preperations I wanted to flash the JB rom.
I started the phone in bootloader mode but - unfortunately - couldn't access the recovery mode (ext4). I only get the Android figure and an exclamation mark.
In the how-to it sais i should use fastboot to flash the recovery made by ext 4.
Problem # 1: Ext4 generated a .zip, not a .img file
Problem # 2: I connect the device in fastboot mode, navigate to the adb/fastboot folder and use ./fastboot devices. The phone is recognized and I see the serial number. Next I try "flash recovery...." but I only get "command not found". Now, I basically have no idea what to do.
Which recovery should I flash? And how?
I'm so looking forward to your answers.

Androdicct said:
Hello Folks,
I only get the Android figure and an exclamation mark.
Which recovery should I flash? And how?
Click to expand...
Click to collapse
What you get is the stock recovery.
Flash 4Ext recovery or Amon RA recovery ( fastboot flash recovery recovery-RA-passion-v2.2.1.img)
Among the several guides to install JB, I suggest you to look at the following post:
http://forum.xda-developers.com/showthread.php?t=1804571
I just finished this morning the following process:
install RA recovery,
install Blackrose and resize partition,
install from SD card Evervolv-Perdo-3.2.0-Nightly-2013.01.13-passion.zip
install from SD card gapps-ev-jb-20120816.zip
I spent a lot of times reading and trying. I had an issue after installing Evervolv-perdo-3.1.0final-passion zip. That's why I switched to the Nightly (JB 4.2).
Once you are set install a2sd from within the terminal emulator on your N1.
In my opinion this is so far the best ROM I ever have had on my Nexus 1.:good:
I am impressed to the extend that I offer to my wife to do the same on her N1. She said no. No to unlock, no to root and of course no to custom ROM.
Good luck

Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...

Androdicct said:
Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...
Click to expand...
Click to collapse
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?

gunner1937 said:
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?
Click to expand...
Click to collapse
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!

Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=611829 : read posts #15 and #16.
In other words open your folder android-sdk-windows installed on the root of your C: hd. Click on the folder platform-tools and download Amon RA recovery in this folder. Left click anywhere on a blank area of this folder then press the key Shift (keyboard) and right click your mouse. In the drop down menu select Open command window. In the CMD, to be sure that the N1 is recognized by the pc (meaning the right drivers are installed) type ADB devices and press enter. You should see a string of numbers like HT9C......
Type adb reboot bootloader and press enter. You are in the fastboot mode ( and mood if I may say so) and the phone shows that it is in the bootloader. You can check again that N1 is recognized by the pc by typing fastboot devices. Same string appears.
Type fastboot flash recovery recovery-RA-passion-v2.2.1.img.
After the installation is completed boot in recovery, select Flash zip from sdcard, select the ROM you have dropped on the card. When the installation is completed go back to Flash zip from sdcard ( you are still in recovery mode) and select the gapps you have dropped on the sdcard.
Go back to Reboot system now. You are then out of the recovery and it takes some times for the N1 to boot to this beautiful JB
Edit:
http://forum.xda-developers.com/showthread.php?t=1804571 this is for posts #15 & #16

Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
As c2med posted in his guide, sometimes, people lose their recovery when they repartition using Black Rose. Hence, its always best to have Amon-RA or 4EXT flashable .img file in your PC so that incase you lose recovery, you can always flash it back.
Once you are in bootloader ( also called FASTBOOT mode) you can flash your recovery.
Then reboot into recovery from FASTBOOT (Shutdown and then restart using the recovery combination)
Once you are in recovery, follow the steps in c2med's guide (wipe cache/dalvik/etc - except sd-card ofcourse) and flash your ROM from sd card.
Then reboot into JayBee

In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img

jolinnard said:
In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img
Click to expand...
Click to collapse
Thank You! That's what I figuered out last night. Of course I also tried "fastboot flash" but forgot the "./". That was the key. Now the JB ROM works like a charm.
New Problem:
I can't install google apps. In fact I don't really need them. I only use a few apps and found the .apk files with google. Unfortunately the "official" Google apps like chrome don't work.
Plus, I wanted to install the camera (laggy in the evervolv - rom) and keyboard from here.
http://forum.xda-developers.com/showthread.php?t=1965290&page=38
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?

Androdicct said:
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?
Click to expand...
Click to collapse
When you're in recovery, select "Flash zip from SD card" and then select "Toggle signature verification" to disable signature verification, and then "Choose zip from SD card" and navigate to the zip file that you want to flash.

[TOOL] Sensation XL 'free me' tool

just a quick tool i put together that unlocks bootloader, flashes a recovery image, installs root, s-off and writes superCID!
simply install the exe file and run it off your desktop(sorry windows only)
FULL FEATURES:
Free Me (Unlock Bootloader, Flashes Recovery, Roots Device, S-OFF, Writes SuperCID)
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
S-Off
Enable root permissions
Force Update
Flash any .zip file
Flash a rom
Create a logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Flash custom radio
Fix sdcard errors
Fix low batter error
Reboot options
Advanced wipe Options
Pulls Files From Server
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
Click to expand...
Click to collapse
Download Here
REMEMBER! IF YOU LIKE MY TOOL HIT THE THANKS BUTTON OR EVEN BUY ME A KANGAROO!

Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm

anders3408 said:
Ehm..... Just wanted to add a reminder, only use fastboot when it is the only way out. Fastboot can be dangerous, but nice made.
Also here is my testresults:
i did use the function : INSTALL A DOWNLOADED ROM
but:
fastboot erase data -- should be userdata
fastboot erase dalvik -- does not exsist, dalvik-cache is either /cache/dalvik-cache or if i remeber correctly some cm roms uses /data partition to handle dalvik-cache.
and last:
fastboot flash zip --- does not allow you to flash a rom, it complains about it is not allowed to do it, and as i remeber it is our bootloader that are locked on that part.
i tried also with a kernel.zip
sendng "zip" (4029 KB)...
OKAY [ 2.571s]
writing "zip"...
FAILED (remote: not allowed) <----i am s-off and rooted and so on
Finished....
so try do it like a openrecovery scripts using recovery
and last:
the fix low battery error, can you explain how that works
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
ehm
Click to expand...
Click to collapse
i have flashed .zip files on other phones like nexus and desire hd, it was successful, but i have not tried it on sxl as do not have the device anymore but seeing as developers gave so much to me from this forum, i thought id give a little back before i move on to learning ios development, try manual adb and executing adb root then flashing your kernel or zip
i havent tested roms yet though
as of the flashing kernel.zip, i do not know why it did not flash, maybe also try the adb root command before flashing?
and on some devices your phone will not charge it bootloader or recovery and when you want to revert back to stock os, no root, no custom recovery etc. some peoples devices fail to restore after the phone wipes system, data and cache partitions while there battery is below i think 18 percent, and fastboot wont allow you to boot into recovery until battery is above that amount.
why dont they turn their phone off abd let it charge? because when they connect the charger the phone boot into bootloader
i found a guide on google the other week as a request of adding the feature and those commands worked
this is a beta, thanks for the bug reports, will update it and fix the bugs later tonight

our bootloader does not support flashing zip files, that part is locked even if s-off

anders3408 said:
our bootloader does not support flashing zip files, that part is locked even if s-off
Click to expand...
Click to collapse
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!

ricky310711 said:
well thanks for your advice great help, need more people who give great accurate feedback like you will fix most of these errors in the update!
Click to expand...
Click to collapse
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons

anders3408 said:
You can try something like this example:
make a OpenRecoveryScript called flash_rom
adb shell mkdir /cache/recovery/openrecoveryscript
adb push flash_rom /cache/recovery/openrecoveryscript
adb reboot bootloader
fastboot boot twrp-recovery.img
i dont know how to get it to start the script, perhaps it is enough to push the script to correct folder and then boot recovery up.
The reason for fastboot boot ..... is for all can use it also if they uses cwm or a outdated recovery
More info :
http://www.teamw.in/OpenRecoveryScript
https://github.com/JBirdVegas/andro...installer/OpenRecoveryScriptSupport.java#L265
and here is what i also found, that is being done via an app called tasker from android, but i guess it should give us an idear on how it works
1) Use the Secure Settings plugin to run the command as root:
date=`date +%Y.%m.%d-%H.%M`;echo -e "wipe cache\nwipe dalvik\nbackup SDBO $date" > /cache/recovery/openrecoveryscript
2) then choose task > wait and set it for 5 seconds (giving time for things to settle
3) Use Secure Settings plugin as root again to run the command:
echo 'boot-recovery' > /dev/block/mmcblk0p3; sync; reboot <--------mmcblk..... should ofc be changed so it fits runnymede.
i think that is the only way you can flash a rom automaticly on runnymede, but what you can do is, push the rom to zip and when done reboot to recovery and i guess people knows how to press a few buttons
Click to expand...
Click to collapse
i will look into that, as im sure you know i have only just started development, im still learning from people like, but am gonna give back as much as i have took

So this tool basicly roots the sxl for ya am I right going to give it a try today if it does
Sent from my GT-N7105 using xda premium

[HOW TO][Unlocked Bootloaders]Install Fastboots, CWM, Tips & Ticks, and More

Now that the bootloader is unlocked, everyone is asking "WTF do I do now?". Well, here's a bit of help to get you started. I'm assuming you already have adb and fastboot setup and working -- if not, quit reading and get that taken care of. Also, I only run Linux...so I'll try to be transparent and only list the fastboot commands.
I assume that you're not a complete moron and can Google what you don't understand.
Don't use the stock\SDK fastboot binary for flashing /system.
An updated fastboot binary for Lin\Win\Mac can be found here on the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory in your $PATH -- Ubuntu\Debian users can just add it to ~/bin (enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere handy...that's on you to decide.
ROOT\ADMINISTRATOR INFO
On Linux, you might have to run as root in order to run some of the fastboot commands. If your system uses sudo for root commands, typing "sudo -i" will bring up an interactive sudo shell so you don't have to type sudo over and over again. If your system uses su for root, well, you already know the command.
On Windows, you have to enable Administrator Privileges to be able to run some of the fastboot commands.
Linux Terminal Hints
~/ means your home directory -- example -- "gedit ~/Documents/file.txt" would open file.txt in gedit easier than /home/yourusername/Documents/file.txt
You can add a * to file names and directories to not type as much -- example -- "gedit ~/Doc*/file.txt" is the same as the command above, only shortened. If two files have similar names, like Documents and Downloads, then you have to type the name up until the firs different character then add *.
Use the command "../" to go up\back one directory. The command is stackable so "../../" would go back 2 directories and so forth and so on.
Use "cd" to change directories. Is an example really needed for this...
Proper Apps to Use
For zip file editing, use 7-zip on Windows and Archive Manager (file-roller) on Linux
For editing text files on Windows use Notepad++ or any text editor that has unix line breaks -- do not use default Notepad or Wordpad -- you've been warned. Use what ever you prefer on Linux. I prefer Gedit myself.
Basic Fastboot Command Syntax
fastboot flash "partition" "image" -- flashes partition image where partition is where to write to and image is the path to the image being written.
example -- fastboot flash system /path/to/system.img
fastboot -w -- does a factory reset; to expedite things, "-w" can be added to "fastboot flash system system.img -w"
fastboot continue -- continue with the boot process
fastboot devices -- list devices fastboot recoginzes
fastboot -s "device model number" -- set the device fastboot will write commands to; use "fastboot devices" to find model number
fastboot reboot bootloader -- reboot phone into fastboot mode (or restart fastboot mode while in fastboot); same as "adb reboot bootloader"
fastboot help -- list all of this & more
Command Info
Not all the fastboot commands work for us. Specifically, the "erase" commands. If a wipe command doesn't work, skip it. I'll mark them with a ! at the end if it might fail.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Install Stock Fastboots ICS
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img.ext4
fastboot erase cache !
fastboot -w
fastboot reboot
Install Alternate Radio
Reboot into fastboot
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
NON-HLOS.bin is found inside a fastboot zip.
Easy Kernel Install
Download kernel-flash.zip in the attachments[/URL]
Open the zip
Replace the zips current boot.img and device_tree.bin from the fastboot of your choice
Install the zip with CWM
By default, kernel-flash.zip comes with Mex Retail kernel and devtree
Easy CWM Install
Download recovery-flash.zip in the attachments[/URL]
Install the zip with CWM
Not sure if its SS compatible, but it is CWM compatible (for the lazy Photon Q users).
Obtain root after installing a Stock Firmware
There are two choices for obtaining root after a stock flash. the closed source SuperSu by Chainfire & and the open source Superuser by Koush.
Download SuperSu zip from Chainfire (Closed Source)
Download Superuser from Koush (Open Source)
Download the one of the root zips above.
Reboot into CWM/TWRP -- adb reboot recovery
Locate and flash the zip (see below for an alternative way)
Reboot, that's it. Nice not having to run exploits\hacks\Linux just for root
Install Rom/Zip file with ADB + CWM
CWM has the awesome ability to install zip files without having to manually copy them to the phone first. All's necessary is a PC with working adb.
Reboot into recovery
Select "install zip from sideload"
On PC, type "adb sideload /path/to/zip" and press enter
The zip will now be copied to the phone's cache & install
Once installed, do any requirements you'd normally do like wipe caches, etc

I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2

miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Unless you're not rooted with an unlocked BL, there's really no reason why it shouldn't work?
Sent from my N4'd Atrix HD

I was rooted before unlocking... shouldn't it still be rooted?
Sent from my MB886 using Tapatalk 2

miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Did you uninstall safestrap?

Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.

miketravis said:
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
Click to expand...
Click to collapse
Still did not work for me

Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2

miketravis said:
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.

tvd0405 said:
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
Click to expand...
Click to collapse
same here.

I have the same problem. I was able to flash cwm, uninstall the SS recovery, and uninstall the app. The first time I got the dead android symbol. I restored SS via Titanium Backup, reinstalled the SS recovery, and flashed cwm again. I tried rebooting into recovery and was able to get cwm working. As soon I uninstalled SS and rebooted, I got another dead android.

probably because were all on the XT926 if we were to revert back to XT925 then the recovery should work otherwise we will have to tweak the recovery to get it to work properly witht the XT926 software awesome thing is we can now free up the space that SS used for a rom slot however for noobs you might wana stick with SS once you hardbrick without anything to go back too it will be game over for your phone and then you have to con ATT for another

i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx

htchd2fix said:
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
Click to expand...
Click to collapse
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.

skeevy420 said:
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
Click to expand...
Click to collapse
What's MR?

yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?

Markyzz said:
What's MR?
Click to expand...
Click to collapse
Mexican Retail
Install instructions in OP

htchd2fix said:
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Click to expand...
Click to collapse
You won't lose root
And with an unlocked bootloader, all you gotta do is flash an updater zip with the su binary and app for Stock roms that don't have root
I'll link to a root zip in the op once I find one (or just make it; depends on how quick I find it in a search)

thanx again..
ahahahha...what a beautifullll day....

skeevy420 said:
Mexican Retail
Install instructions in OP
Click to expand...
Click to collapse
is there a point to flash a different firmware? is it required by any means?
I had SS and was backed up, I booted up the "stock ROM" and was successful in unlocking the BL and flashing CWM. I made a new backup of the stock ROM and restored it with success in CWM. In the video it show he has MR , but im confused as to why.
Also, I cant seem to get rid of safestrap....how in the hell do you uninstall it???

[GUIDE] Back to Stock ROM (the sure method)

Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:

TheTigerDeveloper said:
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
Click to expand...
Click to collapse
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:

shubham1120 said:
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
Click to expand...
Click to collapse
i know, but with this one any type of user can follow the guide (especially linux user)

my phone keep restarting, i have try this method, no works, helpppppppp
it stuck on honor logo

Hi Guys,
i got the same problem here with my H60-L12
After flashing Beta Lollipop 5.1.1 i tried to go back to 4.4.4.
Now it's stuck in bootloop and now it keeps flashing the honor logo.
Tried to unbrick it with Multi-Tool and different stock roms but i cant get into recovery or the 3 button install method, only thing working is fastboot mode.
Any suggestions?
Thank you!!

ok, now i'm desperate.
Got different Stock Roms (4.4 5.8.1;4.4 B119;4.4 B310; 4.4 B316, tried TWRP in different versions, even tried to reinstall fastboot drivers , same problem on Windows 10 and 7.
Only think working is Fastboot&Rescue Mode (White Screen, Phone UNLOCKED), but only when plugged in on PC with USB cable.
When plugged in charger, it just reboots and reboots i can't switch to Recovery or Fastboot mode and doesn't even charge the phone.
Maybe someone got any idea, did i use wrong stock roms? Do i have to use Rollback/Revert versions?

Any way to back to stock rom without unlock bootloader?

I've made a horrible mistake.
I was on 5.9.16, tried to downgrade by flashing system, recovery, cust and crc.
Unfortunately I've done it with B316, which is 4.4.4, so i got this annoying bootloop, in which i can't access recovery, bootloader or use the 3 buttons method.
It seems as if the phone tries to forcefully boot into system ignoring everything I do.
I tried draining the battery to turn it off, which worked, but when i charged it it tried to system boot as soon as there's enough battery.
Any ideas?

and where can I find update.app?

This worked for me! I switched from CM11 to the stable 5.1.1 release using your guide. Flashed B370 and then did a local update for the stable lollipop rom. Thanks a ton.

i need help
I extract listed file and open cmd.
I was able to reboot into bootloader.
I writing "fastboot.exe flash boot BOOT.img" and here is the result:
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
Whats now?
I have rooted H60-L04 with cyanogenmod 11-20150822 KitKat
Thanks
Michal

yeah, very easy guide
i did to my H60-L04 CM11
thanks for sharing

error
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s

i couldnot flash stock recovery because of the fail command not alowed,

i couldnot flash stock recovery because of the fail command not alowed,

Thank you so much! Now my phone is bricked... How about not sharing ur help when u don't know what could happen?

My phone shows Rescue Mode
Attention! Please update system again!
Error!
FuncNo (FUNC_BOOT_KERNEL)
Error NO: 2

i couldnot flash stock recovery because of the fail command not alowed,

i couldnot flash stock recovery because of the fail command not alowed,

thalaraj1992 said:
i couldnot flash stock recovery because of the fail command not alowed,
Click to expand...
Click to collapse
are you on a boot loop?
make sure your device is recognized by your computer.
download universal-adb-driver for windows and install