Database Info

Can you erase the sdcard (external storage) using fastboot?

Does anyone know a way of erasing the sdcard (external storage) on the Nexus S using fastboot commands? i ask because i'm creating a cmd file that will return my phone back to stock using factory images and then relock the bootloader, the only problem is that the sdcard doesn't get erased when relocking the bootloader, so is there a fastboot command to erase the sdcard?

You can lock and unlock bootloader again. Then relock.
So lock->unlock->relock
Sent from my Nexus S using Tapatalk

Thanks for the quick reply, i had thought of that but i would prefer to just erase the sdcard (also for future reference), or, perform a relock that gives the same results as the unlock, eg: wipe sdcard, which would be better, my cmd entries are below.
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
The only thing missing is a command to erase the sdcard.

d.chatten said:
Thanks for the quick reply, i had thought of that but i would prefer to just erase the sdcard (also for future reference), or, perform a relock that gives the same results as the unlock, eg: wipe sdcard, which would be better, my cmd entries are below.
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
The only thing missing is a command to erase the sdcard.
Click to expand...
Click to collapse
Try fastboot erase sdcard?
Sent from my ice cream powered Nexus S

DarkhShadow said:
Try fastboot erase sdcard?
Click to expand...
Click to collapse
Thanks for the suggestion, but i have tried this and it doesn't seem to work with the Nexus S.

Anyone...?

d.chatten said:
Thanks for the suggestion, but i have tried this and it doesn't seem to work with the Nexus S.
Click to expand...
Click to collapse
You could try fastboot erase /dev/block/vold/179:3
Or boot it up and delete it via android
If they don't work don't lame me I'm a noob xD
Sent from my ARCHOS 80G9 using XDA Premium HD app

I think i'll just use the lock>unlock>lock method till i find something a bit more concrete, thanks for the suggestions though, much appreciated.

where can i find all this files?
d.chatten said:
Thanks for the quick reply, i had thought of that but i would prefer to just erase the sdcard (also for future reference), or, perform a relock that gives the same results as the unlock, eg: wipe sdcard, which would be better, my cmd entries are below.
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
timeout /t 5 > nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
The only thing missing is a command to erase the sdcard.
Click to expand...
Click to collapse
where can i find all this files?

You can download the factory images from here > https://developers.google.com/android/nexus/images, you'll need WinRAR, 7zip or similar installed to enable you to extract the files.

if i recall correctly, the command is "fastboot erase media"

TheMachoMidget said:
if i recall correctly, the command is "fastboot erase media"
Click to expand...
Click to collapse
Found this
Delete existing apps on Android SD
adb shell rm -r /system/sd/app
adb shell rm -r /system/sd/appprivate
Through Terminal Partition SD card
It will erase everything on your SD card
$ su
# cd /data
# wget http://64.105.21.209/bin/lib/droid/sdsplit4
# chmod 555 sdsplit
# /data/sdsplit -fs *size* (add -nc to the end for JFv1.5ADP)

Semi-bricked sensation (corrupt IMEI?)

Just over half a year ago (January 2012) I have unlocked my sensation with rev. h-boot, installed 4 ext recovery and flashed Android Revolution. I've been using the phone in a number of countries since, with no problems. A couple of days (9/08) back, when I returned to the UK my sensation started behaving as if it had been IMEI blocked, and after fiddling around for a while I discovered that the IMEI android reports is different that the one printed under the battery/on the box. Given it doesn't seem I have any backup (bear in mind it worked like a charm for past half a year) is there any way of repairing that corrupt IMEI? Is it (so naive) stored in more than one place on the phone so I could access the factory IMEI or anything of that sort? I've tried using the fastboot oem writeimei command, as well as the root terminal emulator command that have been posted on these forums a number of times but neither of them worked.

Go to shop where you get it
Sent from my HTC Sensation using xda premium

From the dialler which one does *#06# report ?

Your fastboot might be neutered (can't issue write commands properly) if you upgraded the HBOOT using the universal firmware packages posted in the Dev section, even though it is still s-off.
When you boot into the bootloader, does it say *** LOCKED *** or Revolutionary in the very top left? If it's *** LOCKED ***, you need to reinstall the Revolutionary HBOOT.
If it says Revolutionary, issue the following commands from Windows to fix your IMEI:
Code:
fastboot getvar imei
[shows old imei]
fastboot oem writeimei 123456789012345
fastboot reboot-bootloader
fastboot getvar imei
[shows new imei]

krazykipa said:
Your fastboot might be neutered (can't issue write commands properly) if you upgraded the HBOOT using the universal firmware packages posted in the Dev section, even though it is still s-off.
When you boot into the bootloader, does it say *** LOCKED *** or Revolutionary in the very top left? If it's *** LOCKED ***, you need to reinstall the Revolutionary HBOOT.
If it says Revolutionary, issue the following commands from Windows to fix your IMEI:
Code:
fastboot getvar imei
[shows old imei]
fastboot oem writeimei 123456789012345
fastboot reboot-bootloader
fastboot getvar imei
[shows new imei]
Click to expand...
Click to collapse
Is this not a little illegal ?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app

*shrugs* just suggesting a solution, maybe using the phone as he has it right now is illegal... !

This works it is ilegal, kinda.
Sent from my HTC Sensation Z710e using xda premium

not really
I dont believe its illegal if he's repairing/restoring IMEI back to original, if he/she's "changing" a valid IMEI then yes.

My fastboot doesn't give the option of the command ' writeimei' .
Only:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048

freelanc45 said:
My fastboot doesn't give the option of the command ' writeimei' .
Only:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
Click to expand...
Click to collapse
It needs a custom fastboot binary (Revolutionary) and you are (technically) legally limited to restoring a damaged IMEI on your own consent. As explained, creating a false IMEI is illegal. Just a heads-up.

My OPO died after trying to flash factory image

Hi everybody.
I'm new here, in OPO forum.
I got my OPO 6 months ago and I first get a big issue now.
My OPO can't boot even to bootloader or recovery.
Before that, I'm running the latest Bliss Rom with TWRP recovery.
Everything's running fine till I decide to flash back to CM-12.0-YNG1TAS17L.
I downloaded the file "cm-12.0-YNG1TAS17L-bacon-signed-fastboot_64GB.zip" from Oneplus.net forum.
After extracted the zip file, I used batch file call "flash-all.bat" which look like normal script that we use to flash the rom.
fastboot flash modem NON-HLOS.bin
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash sbl1 sbl1.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash dbi sdi.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash rpm rpm.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash tz tz.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash LOGO logo.bin
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash oppostanvbk static_nvbk.bin
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update cm-12.0-YNG1TAS17L-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
I let it runs... but unfortunately after flashing rpm.mbn... my OPO doesn't boot anymore.
Anybody has seen this before?
Much appreciated for your help.

Who wrote that script? It's the "fastboot reboot bootloader" command between each flash that has caused your problem. It's completely unnecessary and has been known to cause bricks. I'd like to know who the author is please. Anyway, your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732

THNX
Heisenberg said:
Who wrote that script? It's the "fastboot reboot bootloader" command between each flash that has caused your problem. It's completely unnecessary and has been known to cause bricks. I'd like to know who the author is please. Anyway, your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Thank you Heisenberg.
The script comes with the zip file, so I'm not sure who made it.
But I tried to look for many sources about restoring back to stock image.
Then I followed this http://webtrickz.com/how-to-flash-cm12-lollipop-factory-image-on-oneplus-one-using-fastboot/.
Anyway, I'll try your recommendation.
Thanks a lot.

Work like CHARM!
I followed the link above and now my OPO's alive!
Thanks a lot #Heisenberg.

Installing factory image Android 6.0

Iv'e tried to install the android 6.0 factory image on nexus 5
I unlocked the bootloader and ran “flash-all.bat” and after few minutes I got this error:
What shuold I do?

Try flashing them individually !

code3h said:
Try flashing them individually !
Click to expand...
Click to collapse
Iv'e just tried to power on the phone as it is and it started up and everything seems to work fine.
but I wonder if that error can cause problems in the future..
should I reinstall or leave it like that?

i had a problem with the bat file as well
it said it couldnt find boot.img ... but the rom.zip was of coure in the same dictionary
after flashing everything individually it worked fine
N5 cm12.1n twrp
win10

Don't like the included bat
I made my own bat file, I hated the one that's included and I mostly only flash minor version updates so I'd just dirty flash because it's okay to and I'd keep all my stuff.
Anyway if you want to use my bat, in the platform-tools folder, create a folder called "images" and extract the zip in there, then extract the images zip into the same folder so you should have all the files there boot.img, userdata.img etc... Open notepad and paste the bat script below, save as "WhateverYouWant.bat" in the platform-tools folder and then run it, for me it works without running as admin so you shouldn't need to do that.
Bat script (This will delete all user data since its a major version update, so backup before!)
Code:
@echo off
color 0A
echo This will dirty flash the device. Place all images in the folder named "images".
pause
cls
adb start-server
cls
echo Booting to bootloader
color 0F
adb reboot-bootloader
cls
color 0E
echo Waiting for device
color 0C
echo If your device has booted and you can still see "waiting for device", then your device is NOT being detected by Fastboot. Check your drivers.
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
cls
color 0A
echo Flashing bootloader
fastboot flash bootloader ./images/bootloader-hammerhead-hhz12h.img
cls
color 0E
echo Waiting for device
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
cls
color 0A
echo Flashing radio
fastboot flash radio ./images/radio-hammerhead-m8974a-2.0.50.2.27.img
cls
color 0E
echo Waiting for device
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
cls
color 0A
echo Flashing boot partition
fastboot flash boot ./images/boot.img
cls
echo Flashing cache partition
fastboot flash cache ./images/cache.img
cls
echo Flashing recovery partition
fastboot flash recovery ./images/recovery.img
cls
echo Flashing system partition
fastboot flash system ./images/system.img
cls
echo Flashing userdata partition
fastboot flash userdata ./images/userdata.img
cls
color 0E
echo Rebooting
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
cls
echo Waiting for device
fastboot continue
cls
color 0A
echo Finished
pause

Tlazipex said:
Iv'e just tried to power on the phone as it is and it started up and everything seems to work fine.
but I wonder if that error can cause problems in the future..
should I reinstall or leave it like that?
Click to expand...
Click to collapse
* If your phone is up and running, nothing to worry about (All good)
* It must not cause any error, even if it does, you know where to post
* Its completely up to you. Since you asked, I would recommend to use it for couple of days, if your notice any thing unusual then you can reinstall any how.
Note : "Nexus Root Tool-kit" is worth trying to flash (Comes very handy)

How To Guide Guide to flash images in Linux

as we known, there's a famous tool called Tiny Script Tool to flash our custom systems. but i hate windows, is there a way to flash images in linux? at lease in linux there's no driver needs to all adb devices, thats perfect!
this guid will led you to do it in linux.
as Moto edge s is a dynamic partition device, these options suite to all devices with super block.
maybe YOU HAVE TO USE ROOT OR SUDO TO ACCESS YOUR DEVICE. change to root user if you can't access your device in linux.
# automatic tool:
i've wrote it as a script tool, see https://github.com/superiums/TrinyFlashScript
# manually steps:
## 刷机步骤
1. 备份app
Bash:
#!/bin/bash
backdirs='/dev/shm/app_backup/'
if [ ! -d "$backdirs" ]; then
mkdir $backdirs
fi
# user 0
backdir='/dev/shm/app_backup/0/'
if [ ! -d "$backdir" ]; then
mkdir $backdir
fi
adb shell pm list packages --user 0 -3 -f |awk '{ORS="\n";sub(/package:/,"adb pull ");sub(/apk=/,"apk '$backdir'");print($0".apk;");print("")}' >$backdir'dolist.sh'
sh $backdir'dolist.sh'
# ----------back app for user 10, if you have insular installed in your phone, this is needed!!! ********otherwise, skip.*******
backdir='/dev/shm/app_backup/10/'
if [ ! -d "$backdir" ]; then
mkdir $backdir
fi
adb shell pm list packages --user 10 -3 -f |awk '{ORS="\n";sub(/package:/,"adb pull ");sub(/apk=/,"apk '$backdir'");print($0".apk;");print("")}' >$backdir'dolist.sh'
sh $backdir'dolist.sh'
# ---------------------------------------------------------------------------------------------------------------------
2. 备份数据
Bash:
adb pull /sdcard/Downlad .
3. 重启到fastboot模式,刷写非动态分区
> **非动态分区包括**:
>
> - vbmeta
> - vbmeta_system
> - boot
> - vendor_boot
> - dtbo
Bash:
adb reboot bootloader
# 或 volumne- & power 开机
# 验证是否fastbootd模式
fastboot getvar is-userspace
# 应返回 no
fastboot flash [partition][_slot] [image]
# clear userdata and meta
fastboot -w
4. 重启到fastbootd模式,刷新动态分区
> **super分区包括**:
>
> - system
> - system_ext
> - vendor
> - product
Bash:
fastboot reboot fastboot
# 验证是否fastbootd模式
fastboot getvar is-userspace
# 应返回 yes
fastboot flash [partition][_slot] [image]
6. 双清
Bash:
fastboot erase userdata
#或
fastboot -w
#完成,重启到新系统
fastboot reboot
7. 设置系统
Bash:
#-------------for chinese users only, because they are blocked by the GFW and not able to connect to google.--------------
#Android 7及之后的版本输入如下两个命令,设置网络检测地址:
adb shell settings put global captive_portal_http_url http://www.google.cn/generate_204
adb shell settings put global captive_portal_https_url https://www.google.cn/generate_204
#可以输入如下命令, 禁止检测网络连接状态.
adb shell settings put global captive_portal_detection_enabled 0
#---------------------------------
#---------- if you are concern to your private data, this is usefull.
#强制开启分区存储
adb shell sm set-isolated-storage on
9. 恢复软件及数据
Bash:
cd 0
ls -1 *.apk | xargs -ti -n 1 adb install --user 0 {}
#------------- after install insular--------------------
cd 10
ls -1 *.apk | xargs -ti -n 1 adb install --user 10 {}
adb push ./Downloads/* /sdcard/Downloads/
hopes this help.

the insular mentioned above is this package: com.oasisfeng.island.fdroid.apk
which will create sperate user space for your storage , called "work profile".
if you bricked your device, try these options:
(Every flash lover should backup a stock image for future!)
RSA solution, flash back to stock firmware. follow Skip to content for windows, follow these commands for Linux:
Bash:
command
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Blank Flash, both windows and linux tools and image contained.
download stock firmware for motorola edge s (nio, XT2125) here: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
download blankFlash tool here:
https://mirrors.lolinet.com/firmware/motorola/nio/blankflash/blankflash_nio_RRTS31.Q1-84-24-3-6.zip

MSM Xextend is very powerfull, so many custom settings, love and great appreciate !

I've wrote a automatic script tool for this, see
https://github.com/superiums/TrinyFlashScript