[q] wiped everything - Kindle Fire General

I wiped everything in TWRP on accident. the only thing on the phone is TWRP, no backups, nothing. i was wondering if there was a way to get all the system files and such back?
it can not unzip files.
the only thing it can do is run twrp. that's it.

TWRP can only restore backups it's made. Unless you copied them off the device before you wiped it.. you are out of luck on doing a restore.
You should be able to reload a Rom though.

If he were to try and flash a stock.zip, how would he get it onto /sdcard?

Mount USB in TWRP

1. once you are in twrp click the mount button from the recovery
2. mount sdcard - it should show up on your computer
3. download http://www.mediafire.com/?gtxrohbc4gmu4m8
4. copy the downloaded file to sdcard
5. in twrp tap install, select the file, clear the small button with "X md5" or something like that(if you don't do this the kf will not install the rom) and install it - ignore failures about volume /misc - the kf don't have a volume /misc
6. on the screen where you return after installation tap clear dalvik/cache (in the lower left)
7. go to you command prompt and issue "adb shell idme bootmode 4000" and "adb reboot"
8. be patient - the first boot takes long time
9. enjoy !
you don't have to root it because this rom is a prerooted stock rom

What would this forum do without b63? Thank you.

Related

Nexus S Forgot Security PIN

Hey all,
Hopefuly someone can help me otherwise i'm going to have to take this phone back to the o2 shop where I got it from.
I have a Nexus S, was looking at custom roms the other night and decieded to unlock and root it and flash the CyW7 rom onto it.....after a couple hours of playing with the new software I decieded it wasn't for me so flashed the device back to stock 2.3.1 software.
2.3.1 loaded fine and I installed the 2.3.2 update before rooting it so I could install adblock.
Got it all working fine, setup a security PIN (8 digits) and went to bed.
Woke up this morning and found the phone was not accepting the PIN, ive tried rebooting, trying the PIN in different varations incase I setup a wrong PIN in the first place......still no luck
So, i've looked into reflashing the device with stock 2.3.1 software again but USB debug mode isn't on and I can't install the USB drivers in Fastboot mode (says no compatible driver found for my hardware error)
How do I move forward here? Is there anything I can do to fix it?
Thanks a billion for anyone who gives me advice....
Boot into recovery and factory reset.
Boot recovery took me to a error screen where I had to take battery out to reset it.
I've managed to get the USB drivers to work now, and flashed the clockwordmod recovery image, then reset the phone.
Can I just confirm;
Is this the correct proceedure for the Nexus S to stop the Clockwordmod recovery from been removed.
1. Download the custom recovery image and save it to your computer
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe)
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of each line:</p><p>fastboot flash recovery recovery.img
4. Once it is flashed, leave the phone in plugged in and in fastboot mode.
6. Root the Phone
7. In fastboot mode, select Recovery using the volume buttons and power button and wait for it to boot into recovery mode.
8. Download the Superuser flashable zip file and save it to your computer.
9. Once in recovery mode, select Mounts and Storage then select Mount USB Storage so we can transfer files to the sd while it is in recovery mode.
10. Copy the Superuser.zip file to the root of your internal storage (do NOT extract it, do NOT put it in any folders, just on the phones storage itself).
11. Select Unmount on the phone.
12. Select Mount System, then select Go Back to get back to the main menu.
13. Then scroll to flash zip from sdcard and then choose zip from sd card and select the superuser.zip file and wait for it to finish flashing.
14. Once it is done, select Go Back then Reboot System and wait for the phone to reboot.
15. Stop the Phone from Uninstalling the Custom Recovery Image
16. Once the phone is booted up, plug it in via USB cable and do NOT mount the storage.
17. Open a command prompt on the computer and type the following with hitting enter at the end of each line:
adb shell
cd etc
mount -o rw,remount /dev/block/mtdblock3 /system
mv install-recovery.sh install-recovery-no.sh.
18. Turn off the phone and turn it back on by holding down Volume Up and Power to get into fastboot mode.
19. Plug the phone in via USB cable while in fastboot mode and open the command prompt again and type the following with hitting enter at the end of each line:
cd c:\androidsdk\tools\
adb reboot bootloader
fastboot flash recovery recovery.img

Need Help, No OS

Hi,
The N4 of my wife has big problem.
I wiped in "custom recovery" (TWRP) some stuff for return all in factory settings (this was stupid, I know)
Now, when she reboots on recovery, there is a message "No OS installed !"
How fix this, please ?
Edit: I tried with a toolkit, everything seems good, but when I boot, I have only the google screen.
Edit 2: I send with adb: image-occam-jdq39.zip, but when it failed when I try to install it.
Thanks.
https://developers.google.com/android/nexus/images#instructions
^^ negroplasty has given you the link to download the latest factory image. You can flash that to your phone no problem as long as you can boot into the bootloader (from off state, hold power + vol down)
Connect phone to pc, go to bootloader
Throw the image you want to flash to the same folder where your adb tools are
Open terminal, change directory to that folder
Then write: ./adb push EXACTNAMEOFROM.zip /sdcard/
Example of me trying to adb push Xylon
Then go to "Install" on your phone, sdcard, select the image, swipe to flash and that's it, hope this clears it.

Erase all content and settings on custom rom

Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
When you are just trying to clear all apps and data for the ROM you are using, go to recovery and just wipe /data and that should be it. This leaves the /system alone so your ROM is still there when you boot. May have to flash gapps again though.
Sent from my Nexus 4 using Tapatalk 4 Beta
BugJuice said:
Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
Click to expand...
Click to collapse
You cant choose the sideload option under the recovery menu? Just do that then connect to a computer and type adb sideload /home/user/romofyourchoice.zip in Linux terminal or windows command prompt. That saved my ass a few times. If he can't do that go into your bootloader download a complete image of stock then use the fastboot command and reflash every partition one by one then once that boots up you can continue from there.
Nexus 4 CyanogenMod 10.1.0
ryaniskira said:
You cant choose the sideload option under the recovery menu? Just do that then connect to a computer and type adb sideload /home/user/romofyourchoice.zip in Linux terminal or windows command prompt.
Nexus 4 CyanogenMod 10.1.0
Click to expand...
Click to collapse
I dumped the rom in the sideload folder and typed adb sideload romname.zip and it says adb devices not found.
BugJuice said:
I dumped the rom in the sideload folder and typed adb sideload romname.zip and it says adb devices not found.
Click to expand...
Click to collapse
I modified my previous post refer to it hopefully you can still do the fastboot flash command. You should be able to find a stock image somewhere unzip the zip file and flash the images with the fastboot flash command (example fastboot flash recovery recoveryfilename.img) just make sure you flash the img files to the right partitions
Nexus 4 CyanogenMod 10.1.0
BugJuice said:
Hi im confused on how to erase everything on my phone. I was on paranoid android rom and wanted to try out cyanogen. i wanted to erase everything first because i was running low on storage unfortunately. So i backed up pictures and sms to my PC. I try to erase all through my custom recovery (clockwork) with no success then i go to settings and erase all content and settings and the files are still there. I tried this about 4 times with no luck. What am i doing wrong?
Edit: I might be in bigger trouble. I formated everything under clockwork settings and rebooted and I am stuck at the google logo. I can go back to recovery though. I cant sideload any roms though to start up
Click to expand...
Click to collapse
What you did in clockwordmod was erase the contents of system, data, cache, and Dalvik cache. If you already have downloaded and copied the ROM you want to the "sdcard", all you need to do is boot into recovery again, select Install, select the zip file that contains the new ROM, and press the power button to install the ROM.
If you have the ROM downloaded but have not copied it to the phone, move the ROM file to the folder on your computer where you installed adb and fastboot. Boot your phone into recovery and select Mounts and Storage then connect the USB cable from the computer to the phone. Confirm that phone shows "Unmount /sdcard/" and "Unmount /system/" or press toggle button to change status as necessary. Open a command prompt on your computer by clicking Start -> Run, typing cmd, and pressing <ENTER>. At the command prompt type cd C:/Android/ replacing "/Android/" with the path name to the folder where adb is installed and press <ENTER>. At the command prompt type adb push ROM.zip /sdcard/ROM.zip replacing "ROM.zip" with the actual filename of the ROM you downloaded and moved to this folder. Now disconnect your phone from the computer and close the command prompt. From the clockwordmod main screen select Factory Reset, then Wipe Cache Partition, and Wipe Dalvik Cache then repeat full wipe twice. Finally, from the clockwordmod main screen select Install ZIP from SD Card followed by Choose file from SD Card, select the ROM.zip file you pushed to the phone's sdcard, and.press the power button to install the ROM.
When clockworkmod reports "Install from SD Card Complete.", return to the main screen and select Reboot system now. The first boot following a fresh installation of a new ROM can take several minutes, just be patient while the ROM initializes the system, applies customizations or updates, and boots to the phone's setup screen.

[How-To] Revert from OtterX Project back to Stock Amazon Partitions

Watch My Video
[How-To] Revert from OtterX Project to Stock Kindle Fire Partitions
and
Flashing TWRP in FFF bootloader For Kindle Fire 1
Recommend using update-kindle-prerooted.6.3.3.v1.zip rather than update-kindle-6.3.3_D01E_4112920.bin
Install kindle Fire DriversDownload Kindle Fire Utility extract file from zip, run install.drivers.bat
Download Files Links in 2nd post
TWRP 2.2.2.1: for Stock Rom, custom Gindgerbread(CM7), ICS(CM9), and Jellybean (CM10) roms
TWRP 2.2.2.1 - 2.6.1.0: ICS(CM9), and Jellybean (CM10) roms
TWRP 2.6.3.0 or better: For KitKat(CM11) Roms
Bootloader: Otter X Bootloader 2.05 seems to work fine with Otter/Blaze TWRP 2.7.x.x, Doesn't work well with TWRP 2.2.2.1, use FFF 1.4a/1.5
ADB Files
Rom: Stock or Custom/GApps
Change Partitions from Otter X[ to Amazon
Reboot Kindle Fire, When you see bootloader, press power button once to open boot menu, select Advanced
Open the bootloader menu by pressing [POWER]
Use 1-2 SHORT presses of [POWER] to highlight "ADVANCED -->"
Use a LONG press of [POWER] to select ADVANCED MENU
Use 5 SHORT presses of [POWER] to highlight "PARTITION MODE: OTTERX" (if this is Amazon you can skip step 3)
LONG press [POWER] to open "PARTITION MODE MENU"
Use 4 SHORT presses of [POWER] to highlight "[CONFIRM] SET MODE: Amazon"
WARNING THIS WILL ERASE THE CONTENTS OF YOUR "SDCARD" and USERDATA!!!! Before doing this step you should have backed up ANYTHING IMPORTANT and pulled it off of your Kindle!
LONG press will select this option and your system, cache, userdata will be changed to the Amazon layout (and ERASED)
Now use short [POWER] presses to navigate BACK and then to "RECOVERY"
STEP 4: WIPE PARTITIONS IN RECOVERY
[Main Menu] Wipe -> Advanced -> check "Cache" and Swipe
[Main Menu] Reboot -> Recovery (wait for it to come back into TWRP)
[Main Menu] Wipe -> "Format Data", type "yes" and hit enter
[Main Menu] Wipe -> Advanced -> check "System" and Swipe
Custom Bootloader and Recovery for Amazon Partitions
Two options Push/ Install in TWRP, or Flash in Bootloader
a. Push/Install
Code:
adb push fff-u-boot_v1.4a.zip /sdcard
Code:
adb pushzip-openrecovery-twrp-2.7.1.0-otter.zip /sdcard
and select install fff-u-boot_v1.4a.zip, when install is finished reboot, select recovery in bootmenu
install zip-openrecovery-twrp-2.7.1.0-otter.zip, when install is finished reboot, select recovery in bootmenu
then install zip-otter-twrp-2.2.2.1-blaze.zip if you are installing CM7 or stock rom
if you can't enter recovery after a reboot, you will need to flash recovery in Bootloader/Fastboot Mode
b. Flash in Bootloader
power off kindle, open command prompt on PC, enter a command, press enter, and Power on Kindle
for Bootloader
Code:
fastboot flash bootloader fff-u-boot_v1.5.bin
For Recovery
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-blaze.img
For Reboot
Code:
fastboot reboot
if you get a
device needs formatted
Click to expand...
Click to collapse
or unable to select SD Card in mount options see
Mounting SD Card and Formating SD Card
Files - Links
Verify md5 checksum for all Files see Using Hash Checksums
.
Recovery
Flash in Bootloader:openrecovery-twrp-2.2.2.1-blaze.img
Install in TWRP: Flashable TWRP zips XDA--​
Bootloader
Flash in Bootloader:fff-u-boot_v1.4a.bin
Install in TWRP: fff-u-boot_v1.4a.zip​
Stock Rom
update-kindle-6.3.3_D01E_4112920.bin
204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554
Official--DevHost--Mega--XDA​
Prerooted 6.3.3 stock--update-kindle-prerooted.6.3.3.v1.zip
ADB and Fastboot
ADB-Fastboot.zip--XDA--
Troubleshooting and Links
I recommend using my update-kindle-prerooted.6.3.3.v1.zip first Even if you want pure stock
The Full stock will flash the stock Bootloader, and stock recovery, even if the partitions are not right.
If the Pre-rooted zip boots fine, then you can try the update-kindle-6.3.3_D01E_4112920.zip
if the Pre-root does not boot, you still have TWRP/FFF, and it is easier to fix.
Links
Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
Kindle Fire Flashable Recoveries/FFF TWRP/COTR/CWM[2014]​
Stock Amazon Partitions
When Amazon partitions are selected.
Verify that Partition Sizes and File Systems are correct
System: Size: 503 mb | File System: ext4 | Screenshot
Data: Size: 5119 MB | File System: vfat | screenshot
Cache: Size:251 MB | File System: ext4 | Screenshot
Note: Other File system may work, depends on the rom installed.
Required: an OtterX Twrp like otterx-twrp-2.7.1.0-recovery
In TWRP Select Wipe> Advanced Wipe>
Check Data Partition Box>Repair or Change File System> compared details Circled in Red
repeat with Cache and System Partitions
if Size is different try repair option, if File System is different use change File System.
Note: After using Repair Option or Changing File System, reboot and verify that Partitions are correct
If those option do not fix the partitions try change to OtterX Partitions with OtterX 2.04 or 2.05 Bootloader.
Wipe>Advanced Wipe>check Cache>reboot
Wipe>Advanced Wipe>check Cache, System, Data>Swipe to Wipe>reboot
In bootloader> select Amazon partitions
in Twrp>Wipe>Advanced>check Cache>swipe to Wipe>Reboot
Wipe>Advanced>Check Cache, System, Data>Swipe to Wipe>reboot
if you get any errors on any steps, go back a step or 2 and try again.
Note: Do not worry about Not rooted or no system install errors, at this time, just select an option and continue
Once Partitions are correct, retry installing the Twrp required for the Rom you want, Reboot, install rom.
In TWRP 2.7.1.0, I am unable to flash TWRP 2.2.2.1 or TWRP 2.6.1 ... Error message is: "This package is for blaze/otter devices; this is a "otterx".
Is there a workaround?
Mounting SD Card in Twrp and Formating SD Card from PC
In Twrp
Select Mount
Check SD Card box
Select Mount USB Storage
When you are done Eject SD Card in Windows.
Then select Unmount in Twrp
If you are unable to select SD Card in Mount options,
check System box,
Select Mount USB Storage
Formating SD Card from PC
Your computer will probably respond that the volume/device needs formatted before using it. This will erase everything left on the sdcard, as will anything else you attempt in this thread.
* Choose a quick format (if possible) and format it as "fat32", block size "4096".
If you don't get the "volume/device needs formatted before using it" warning
you can format by, selecting SD Card in Computer Folder>right click>select Format...>
Choose a quick format (if possible) and format it as "fat32", block size "4096".
also TWRP 2.2.2.1 does not work with oterx 2.05 bootloader, so you need to flash FFF 1.4 or 1.5 first.
sd_shadow said:
also TWRP 2.2.2.1 does not work with oterx 2.05 bootloader, so you need to flash FFF 1.4 or 1.5 first.
Click to expand...
Click to collapse
I was already on v1.04a bootloader so flashing TWRP 2.8 turned out not to work as it could not mount storage. So I went back to OtterX and will try again tomorrow. Thanks for your help; I will post here my results.
ttakacs said:
I was already on v1.04a bootloader so flashing TWRP 2.8 turned out not to work as it could not mount storage. So I went back to OtterX and will try again tomorrow. Thanks for your help; I will post here my results.
Click to expand...
Click to collapse
you used zip-openrecovery-twrp-2.8.0.1-blaze.zip ?
sd_shadow said:
you used zip-openrecovery-twrp-2.8.0.1-blaze.zip ?
Click to expand...
Click to collapse
I did. I was not able to flash anything in TWRP 2.8.0.1. To reinstall OtterX, I used fastboot to install FFF2.05 and TWRP 2.7.1.
Do you recommend I flash 2.8.0.1 before attempting to revert to Amazon partition mode? I don't want to revert to stock but want to go back to CM10.2, which gives me significantly better battery life.
ttakacs said:
I did. I was not able to flash anything in TWRP 2.8.0.1. To reinstall OtterX, I used fastboot to install FFF2.05 and TWRP 2.7.1.
Do you recommend I flash 2.8.0.1 before attempting to revert to Amazon partition mode? I don't want to revert to stock but want to go back to CM10.2, which gives me significantly better battery life.
Click to expand...
Click to collapse
Just flash 2.2.2.1 IMG in bootloader
Sent from my DROIDX using Tapatalk
Did you watch my Video?
sd_shadow said:
Just flash 2.2.2.1 IMG in bootloader
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
I'm stuck.
Here are the steps I took:
1. Rebooted to v2.05 bootloader and changed the partition mode from OtterX to Amazon.
2. Powered the Kindle off.
3. In fastboot, flashed the v1.5 bootloader and 2.2.2.1 TWRP.
4. Rebooted into TWRP 2.2.2.1 recovery.
5. Wipe > Cache = Success. Reboot to recovery.
6. Wipe > Factory Reset (there is no "Format Data" menu item in 2.2.2.1) = Success.
7. Wipe > System = Success.
8. Pushed CM10.2 and JB gapps to the Kindle's sdcard folder.
9. Attempted to flash.
"E:failed to mount /sdcard
"E:Can't mount /sdcard/CM-10.2.zip...."
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
sd_shadow said:
Did you watch my Video?
Click to expand...
Click to collapse
I will have, two minutes from now.
ttakacs said:
I'm stuck.
Here are the steps I took:
1. Rebooted to v2.05 bootloader and changed the partition mode from OtterX to Amazon.
2. Powered the Kindle off.
3. In fastboot, flashed the v1.5 bootloader and 2.2.2.1 TWRP.
4. Rebooted into TWRP 2.2.2.1 recovery.
5. Wipe > Cache = Success. Reboot to recovery.
6. Wipe > Factory Reset (there is no "Format Data" menu item in 2.2.2.1) = Success.
7. Wipe > System = Success.
8. Pushed CM10.2 and JB gapps to the Kindle's sdcard folder.
9. Attempted to flash.
"E:failed to mount /sdcard
"E:Can't mount /sdcard/CM-10.2.zip...."
Click to expand...
Click to collapse
may need to reformat sd card
reboot twrp, mount>check sd card> if you get a" need to format" popup in window
in Windows Choose a quick format (if possible) and format it as "fat32", block size "4096".
sd_shadow said:
may need to reformat sd card
reboot twrp, mount>check sd card> if you get a" need to format" popup in window
in Windows Choose a quick format (if possible) and format it as "fat32", block size "4096".
Click to expand...
Click to collapse
Reformatting successful, pushing ROM and gapps now to the Kindle....
... TWRP installing ROM and gapps now....
... Rebooting into CM10.2....
.... Success!
Thanks so much!
ttakacs said:
Reformatting successful, pushing ROM and gapps now to the Kindle....
Click to expand...
Click to collapse
I can't remember if I said in video, files may not be in sd card, but in system folder, and may need to reboot kindle before you can see the files.
check the sd card first though
Thank you for the guide, sd_shadow. I was really looking forward to Project OtterX but with Hashcode gone, I will revert back to stock Amazon.
@sd_shadow, thanks for this guide. I tested some OtterX roms but the Kindle is with my wife most of the time and for the sake of simplicity and battery consumption I'm gonna go back to non-otterx roms.
Instead of flashing the stock Rom, is there any way to revert to one of the non-otterx CM11 roms?
Thanks in advance!
inarush said:
@sd_shadow, thanks for this guide. I tested some OtterX roms but the Kindle is with my wife most of the time and for the sake of simplicity and battery consumption I'm gonna go back to non-otterx roms.
Instead of flashing the stock Rom, is there any way to revert to one of the non-otterx CM11 roms?
Thanks in advance!
Click to expand...
Click to collapse
yes instead of installing twrp 2.2.2.1 use 2.7.1.0 and flash cm7
sd_shadow said:
yes instead of installing twrp 2.2.2.1 use 2.7.1.0 and flash cm7
Click to expand...
Click to collapse
Thanks a lot, I have it running otter CM11 already!
I guess I speak for everyone in this community when I say that I love you!

recovery disappeared

I accidently formatted my sd card, so i had to flash a stock 4.4.4 image, root, and recovery via adb and command prompt. The problem i have is the recovery is not installed, yet, i can get into recovery once by flashing the customrecovery.img but upon reboot- no more recovery? I have no idea what's going on and could use a little help. Also i am now on 5.0.
Thanx for your time.
Get one of the toolkits available like WugFresh's and use it to push a recovery image to the phone. I believe the device needs a pathway renaming to keep the recovery image from flash to flash. The tool kits sort all that out. I'm running modified stock lollipop with multirom and no disappearing recovery image here.
You can also simply press the volume up button and then the power button to get into recovery (twrp recovery) after flashing the twrp img in bootloader, go to the mount menu and mount system, press the home button, press Advanced -> File Manager. Now navigate to /system and rename the file named recovery-from-boot.p to recovery-from-boot.bak. This will stop stock recovery from overwriting twrp on reboot.

Categories

Resources