how to format partition on kf using fastboot? - Kindle Fire General

how to format partition on kf using fastboot?

fastboot OEM format.
then flash STOCK image, then redo recovery/bootloader/root.
Sent from my Nexus 7 using xda premium

Related

Cpw uk 2.1 rom

Hi guys
Could someone tell me where I can find a carphone warehouse UK V2OB rom with fastboot
I want to either flash it through kdz or through fastboot
Not recovery pls
Sent from my GT540 using XDA App
http://csmg.lgmobile.com:9002/swdata/WEBSW/GT540/AGBWBK/V20b_00/V20B_00.kdz
without fastboot ... but some people have kdz kitchen to insert fastboot into it.
pebe94 said:
http://csmg.lgmobile.com:9002/swdata/WEBSW/GT540/AGBWBK/V20b_00/V20B_00.kdz
without fastboot ... but some people have kdz kitchen to insert fastboot into it.
Click to expand...
Click to collapse
I don't know how to insert fastboot so I need a rom with fastboot
Sent from my GT540 using XDA App
I don't have good internet connection, so I can't do that.
pebe94 said:
I don't have good internet connection, so I can't do that.
Click to expand...
Click to collapse
If u can't do it, it doesn't matter I just want a link for CPW uk 2.1 rom with fastboot
V2ob or v2oa
Sent from my GT540 using XDA App
mohnim said:
If u can't do it, it doesn't matter I just want a link for CPW uk 2.1 rom with fastboot
V2ob or v2oa
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Remove fastboot + recovery using SwiftBootloaderBuilder, then flash regular KDZ.
First, put phone in fastboot and type:
Code:
fastboot -w
fastboot erase system
fastboot erase boot
fastboot erase recovery
Don't reboot phone,
Use the 'remove fastboot+recovery option in SwiftBootloaderBuilder
When phone is about to reboot hold VOL DOWN.
Then flash regular KDZ in Download Mode.
Should have everything sorted
effortless. said:
Remove fastboot + recovery using SwiftBootloaderBuilder, then flash regular KDZ.
First, put phone in fastboot and type:
Code:
fastboot -w
fastboot erase system
fastboot erase boot
fastboot erase recovery
Don't reboot phone,
Use the 'remove fastboot+recovery option in SwiftBootloaderBuilder
When phone is about to reboot hold VOL DOWN.
Then flash regular KDZ in Download Mode.
Should have everything sorted
Click to expand...
Click to collapse
Would I then have cpw uk 2.1 rom with fastboot
Sent from my GT540 using XDA App
Is there a fastboot version 2.1 rom instead so I can flash it through cmd and type command
It doesnt have to cpw uk rom just V20a or b version
Sent from my GT540 using XDA App
It would return you to 2.1 without fastboot, if you want fastboot, then flash this:
http://goo.gl/7aRTc (Carphone Warehouse, also some people have been unable to flash because of KDZ extract error.)
http://goo.gl/BOcYT (European Open)
I returned my phone with European Open on it before and they had no problems when I had to have a screen repair (on the old GT540 that I bricked)
But if you are returning to original ROM (for warranty repair, use my previous guide)
Thx
Sent from my GT540 using XDA App

Help!! Bricked!!

Alright first off, I can boot into recovery and bootloader. However, I have no CWM backups or any ROMs on my sd card.
I have no ROM currently installed so it will not get past the splash screen. I went into bootloader, but doing the command "adb devices" nothing is found.
I have tried using the Toolkits but it still doesn't recognize my device. It would just say "waiting for device" and nothing happens.
Any help would be appreciated.
kkl1993 said:
Alright first off, I can boot into recovery and bootloader. However, I have no CWM backups or any ROMs on my sd card.
I have no ROM currently installed so it will not get past the splash screen. I went into bootloader, but doing the command "adb devices" nothing is found.
I have tried using the Toolkits but it still doesn't recognize my device. It would just say "waiting for device" and nothing happens.
Any help would be appreciated.
Click to expand...
Click to collapse
the bootloader is for fastboot. i dont know about cwm, but twrp recovery has an adb sideload option. you connect to adb, press the button, type the command shown, and load the rom from your desktop to your device. you can fastboot the twrp recovery via your bootloader and fastboot.
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
demkantor said:
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I tried to do that but it seems like it wont communicate with my computer. all it says is fastboot: command not found
demkantor said:
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
also i do have an OTG cable and obviously a flash drive, how do i install a ROM through it
For fastboot you will either need to add a path for adb.exe and fastboot.exe in environmental variables or put files needed in same folder as fastboot.exe and of course have proper drivers
Haven't used clockwork for any android in years (not the biggest fan) but I believe when you choose to flash a zip it will allow you to choose where to, including an external SD.
if it doesn't use fastboot to flash twrp and that definitely does have the option. Of course you will need to get fastboot up and running
Sent from my Nexus 7 using xda premium

Nexus 4 4.3 Update

Hi Guys,
I've updated my Nexus 4 with 4.3 manually, as I cannot wait for the OTA I wonder if when I new updates arrives say Android 5, do I still get OTA update? I didnt root nor install a custom rom.
I downloaded the firmware and adb/skd from google developers site
- occam-jwr66v-factory-08d2b697.tgz
- adt-bundle-windows-x86_64-20130717
Here's what I did
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Here's the reference I followed : Scenario 2 [Scenario 1 didn't work for me as I encounter "Installation Aborted"]
Attached is the screenshot of my phone's firmware.
Thanks
Yes you would still get OTA since it is stock firmware.
Sent from my GT-N8013 using xda app-developers app
Thanks a lot really appreciate your input.
Sent from my Nexus 4 using xda app-developers app

[Q] What to do before give my phone to google?

Hi everyone !
My phone has recently shown a defect on the lower border of the touch screen. It's still less than one year so I will send it to google.
The thing is I have cyanogenmod installed, rooted etc. I am planning the restore the phone as it was brand-new: original rom, kernel...
I Have followed everything on the first comment of this post:http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Do you think that will be enough or I have to do something more in order to they won't realise i changed anything ?
Thank you all !
Last time I have sent my N4, I just restore the Stock Rom / Kernel, and lock the bootloader. Didn't have any issue.
Best advice would be to
Boot to recovery and make a full backup
Transfer this and anything else you want to PC
Reformat all in recovery (including SD data)
If you want to go overboard then format all with fastboot like such
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Then flash latest stock firmware through fastboot (run the flashall.bat)
Then lock bootloader
fastboot oem lock
Reboot , power off, send in for rma
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Best advice would be to
Boot to recovery and make a full backup
Transfer this and anything else you want to PC
Reformat all in recovery (including SD data)
If you want to go overboard then format all with fastboot like such
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Then flash latest stock firmware through fastboot (run the flashall.bat)
Then lock bootloader
fastboot oem lock
Reboot , power off, send in for rma
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man ! the only problem is that I don't know how to block my bootloader because I am not longer root user
"fastboot oem lock"
Don't need root, just connect the phone to your PC in fastboot mode and fire that command.
Sent from my Nexus 4 using XDA Free mobile app

[Tutorial] Restore Nexus 9 to Stock

I have a defective device and in preparing to return it, I locked the bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
I was afraid that the N9 was like the N5 & 7 with the "tamper" flag, but after some digging (and advice from others out here), I decided to restore the factory image to see if that would overwrite the image. Yes! No more big fat red "I unlocked my bootloader and may have voided my warranty" message.
I can't take credit for this, but I thought I would consolidate everything I was finding in the Q&A threads into one spot, so I put this little tutorial together. Thank you @Pilz, @jd1639 & @PhilDX for your various posts.
Step 1 - Prepare your system
[Windows]
Since your bootloader is unlocked, you probably already have ADB and fastboot, but if not, grab the SDK from here, unzip and add the "platform-tools" directory to your PATH statement
If your drivers are set up properly and your device has Android debugging enabled, connect USB and execute `adb devices` from a command prompt you should see your device listed
Download the factory image for "volantis" here
The image is double zipped, so unzip, untar, then unzip the image-volantis-lrx21q.zip file into the same directory that contains the bootloader*.img file
Step 2 - Unlock bootloader
If you locked your bootloader, unlock again:
Code:
adb reboot bootloader
fastboot oem unlock
Step 3 - Flash stock image
The flash-all.bat script is broken, so you have to do it by hand:
Open a command prompt
cd into the directory where you unzipped the factory image files
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Before rebooting, relock the bootloader:
Code:
fastboot oem lock
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Typo: fastboot oem unlock
hirndurst said:
Typo: fastboot oem unlock
Click to expand...
Click to collapse
Hahaha! Thanks.
always good to know! thanks!
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
DarthSudo said:
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
Click to expand...
Click to collapse
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Thanks for this thread. Great guide.
jd1639 said:
You could also use fastboot -w instead of the erases
Click to expand...
Click to collapse
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Thanks for this. I RMA'd my Nexus 9 and sending it back tomorrow
DarthSudo said:
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Click to expand...
Click to collapse
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
jd1639 said:
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You guys are all right. I looked back at some of my notes and I've flashed plenty of devices w/o formatting the other partitions first. Just userdata and cache. Thanks!
Hey guys, just wanted to thank you for the fixed "script". This is now my flash-stock.sh script I use whenever I need to flash a nexus device as the one delivered by google just doesn't work (reboot loop due to crashing apps on startup or "missing system.img").
Works perfect and I always like to not dirty but rather make a clean flash as it just reduces the number of possible faults .
Cheers
Creamy
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
bruce7373 said:
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
DarthSudo said:
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
Click to expand...
Click to collapse
Thx, that seems simple enough. But I made the initial system (stock) backup before I rooted. That's why I was thinking restoring that would work. I just wasn't sure about the recovery, whether the restore would put the stock recovery back or not.
Sent from my Nexus 6 using Tapatalk
DarthSudo said:
I have a defective device and in preparing to return it, I locked to bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Click to expand...
Click to collapse
Hi,
is there a way to get rid of that red message if your bootloader is locked and you cannot boot into OS?
Thanks!
EDIT* Nevermind
Hey. Sorry for reviving this thread.
I installed Remix OS on my N9 and (after discovering that performance is horrible, with ~80% RAM usage on idle) after a reboot, Remix OS won't get past it's boot splash. I am attempting to flash my device back to stock.
I never touched the bootloader (never did any 'fastboot flash bootloader ...' or anything), so it it still necessary to flash the bootloader image, or can I just flash the system.img, boot.img, vendor.img etc.?
The bootloader had never changed so there is no reason to flash it.
Sent from my Nexus 9 using XDA Free mobile app

Categories

Resources