Fairly new at android, so go easy on me.
Created a backup (apparently incorrectly), and decided to restore the backup. Once it was completed and I rebooted the KF booted into TWRP and no backups exist. The only folder is the TWRP, but boot, cache, data, etc. exist when you move up a level. Any way to force a ROM re-installation at this point? I can mount the drive via TWRP and can access the TWRP folder via windows explorer, but it appears that the entire system has been wiped. I can also use ADB to look at teh status and its saying that its online, rooted, and in recovery mode (5001). Any help would be appreciated.
There are numerous roms in the forum. Look around and find the one that is right for you. There is the stock rom if you want the original kf experience. I reccommend cm7 if you want a fully functional android tablet. Downlad any rom to your pc and copy to the fire using usb mount in twrp. I recommend wiping system, data and dalvik before flashing a new rom to avoid complications. I would add links but that is kinda hard from the fire. Lol
Sent from my Kindle Fire using Tapatalk
Awesome... I was stuck here for 4 hours at work today. LOL
Thank you very much.
Related
Will running the Kindle Fire utility wipe my data such as email settings, books, music and movies?
Last and related question, if I want to run the utility on my new Kindle, which is updated with the latest firmware from Amazon, how do I back up my stock version or data first?
Thanks a lot. Loving my Fire here in Toronto. Don't know why it's not sold here.
Harry
It does not wipe your data.
Anyone know the answer to the second question?
Without root or a recovery, there is no real way.
You can backup your data using Titianium Backup which requires Root.
Or you can back up your system using TWRP recovery, but you would already need to have root and the recovery to do that.
As for the System itself, 6.2.1 or 6.2, there are images that you can use to reload that using TWRP if/when you load that.
You could connect your device to your computer and access your SDCARD memory and save that, but other sections of the system like /data would not be accessible.
Hy there I love xda and im a new user to xda nexus forum
With excelent guides I learnt how to root unlock and install custom rom (quite easy let it down into your internal storage and install from zip)
but I have few questions..
When I tried to wipe data and cache I accidentally did factory reset which ended up in no installed rom, internal storage empty and I was in custom recovery and I couldn't connect to computer, so I had to start from 0... last times I've been selecting wipe data and cache.. but I seen that in my nexus 7 some old files are still there (under a folder called 0) What should I do to make a clean install? which option of the new recovery should I choose? thankyou
mariosanoguera said:
Hy there I love xda and im a new user to xda nexus forum
With excelent guides I learnt how to root unlock and install custom rom (quite easy let it down into your internal storage and install from zip)
but I have few questions..
When I tried to wipe data and cache I accidentally did factory reset which ended up in no installed rom, internal storage empty and I was in custom recovery and I couldn't connect to computer, so I had to start from 0... last times I've been selecting wipe data and cache.. but I seen that in my nexus 7 some old files are still there (under a folder called 0) What should I do to make a clean install? which option of the new recovery should I choose? thankyou
Click to expand...
Click to collapse
Use TWRP for recovery and to do a clean install wipe all data from TWRP.
Sent from my Nexus 7 using xda premium
mariosanoguera said:
Hy there I love xda and im a new user to xda nexus forum
With excelent guides I learnt how to root unlock and install custom rom (quite easy let it down into your internal storage and install from zip)
but I have few questions..
When I tried to wipe data and cache I accidentally did factory reset which ended up in no installed rom, internal storage empty and I was in custom recovery and I couldn't connect to computer, so I had to start from 0... last times I've been selecting wipe data and cache.. but I seen that in my nexus 7 some old files are still there (under a folder called 0) What should I do to make a clean install? which option of the new recovery should I choose? thankyou
Click to expand...
Click to collapse
I'd flash a stock recovery image onto your device available here which would restore your device completely back to stock (with your bootloader unlocked) From there I'd just re root and do what you want. However I'd personally use CWM Touch Recovery myself, but I just like that recovery more (have used it and the non-touch version for ages and on many devices)
smt8544 said:
I'd flash a stock recovery image onto your device available here which would restore your device completely back to stock (with your bootloader unlocked) From there I'd just re root and do what you want. However I'd personally use CWM Touch Recovery myself, but I just like that recovery more (have used it and the non-touch version for ages and on many devices)
Click to expand...
Click to collapse
I actually have Team Win Recovery Project..
under wipe I can find
Cache
Dalvik
Factory Reset (This is the one I use.. but It leaves in my internal storage with a folder called 0 and my old data from previous roms is stored there)
System
External Storage
Int. Storage ?
Format Data (I did this and I lost everything except TWRM which I could boot at it (but I had no option to install from zip neither couldnt transferr a file through usb mount sd card didn't work))
Which one of all of this should I run before doing the install zip from sd card?
mariosanoguera said:
I actually have Team Win Recovery Project..
under wipe I can find
Cache
Dalvik
Factory Reset (This is the one I use.. but It leaves in my internal storage with a folder called 0 and my old data from previous roms is stored there)
System
External Storage
Int. Storage ?
Format Data (I did this and I lost everything except TWRM which I could boot at it (but I had no option to install from zip neither couldnt transferr a file through usb mount sd card didn't work))
Which one of all of this should I run before doing the install zip from sd card?
Click to expand...
Click to collapse
I think it would be easier and cleaner if you restored back to stock before trying to re root, flash recovery, etc. If you have no important data on your device I'd go for it. If you do have important data, then try and pull it to your computer and then flash a stock image and re root etc.
I always find that in times when my device is screwing around, or I have file dregs around the place, I find it simply easier to backup important things and flash a stock image.
Well, it looks like I unintentionally wiped the /data partition using TWRP right after I did my first backup after rooting. Now I obviously can't boot since system, data, cache, etc. are wiped. The backup I just made was also wiped. As others mentioned in the TWRP thread, it's a bit different for the Nexus 10 compared with other devices - out of the 11 android devices I've had I've never done this!
Anyhow, can anyone a solution to getting a ROM back on my device? I can't seem to mount anything to my PC using TWRP. I can get fastboot working, but not ADB or file system mounting.
Thanks
Ehm, does the Nexus 10 have a ad card? If yes, use another phone to put a Rom on it and then flash it trough twrp
Sent from my awesome fridge
have you tried mount sd storage? or you can try the toolkit in the sticky thread.
Sent from my ADR6425LVW using xda premium
Get a stick drive, sd card reader, etc. Put a rom on it & transfer via twrp file manager
Sent from my Nexus 7 using Tapatalk 2
Just boot into fast boot and flash the stock images.
Sent from my Nexus 10 using Tapatalk HD
can you use adb to push a rom to flash?
TWRP allows you to adb sideload ROMs. Google TWRP adb sideload and it'll walk through the steps. You can also search the Original Development section and find MSkip's toolkit which I believe can flash ROMs and whatnot from your computer. It will also automate installing the proper drivers if that hasn't already been done.
Thanks for all the help. ADB wasn't working in TWRP - I believe it was a driver issue on my PC though. However, as jellydroid13 mentioned, I was able to use fastboot to flash the stock 4.2 image from google, and then boot up from there. Thanks again!
chompone said:
Well, it looks like I unintentionally wiped the /data partition using TWRP right after I did my first backup after rooting. Now I obviously can't boot since system, data, cache, etc. are wiped. The backup I just made was also wiped. As others mentioned in the TWRP thread, it's a bit different for the Nexus 10 compared with other devices - out of the 11 android devices I've had I've never done this!
Anyhow, can anyone a solution to getting a ROM back on my device? I can't seem to mount anything to my PC using TWRP. I can get fastboot working, but not ADB or file system mounting.
Thanks
Click to expand...
Click to collapse
Add me to the list of people who have wiped data over 9000 times in CWM and after updating to twrp and doing it there, have lost everything. I have backups, but am having no device found with adb sideload and suffice to say im a little confused. Confused why "wipe data" and wipe SD card and wipe SD EXT all do the same thing.
"
android01 said:
Add me to the list of people who have wiped data over 9000 times in CWM and after updating to twrp and doing it there, have lost everything. I have backups, but am having no device found with adb sideload and suffice to say im a little confused. Confused why "wipe data" and wipe SD card and wipe SD EXT all do the same thing.
"
Click to expand...
Click to collapse
+1 here
(i'll look for an OTG cable^^)
i had a similar problem several days ago
used ADB sideload to flash ROMs
why adb anything when like jellydroid said you can use fastboot and push all partitions and restore to stock?
I'm facing a similar issue but my device is Moto G5s Plus.
The problem I'm facing is that I accidently wiped out the mobile's system completely, and now it does not even have an "internal storage" partition at all (since it shows 0 MB). Hence, I cannot even transfer any files to my mobile because my computer does show the phone detected but no "internal storage exists".
Please help me out..
So I decided to try and flash Ubuntu last night... I booted into recovery made a backup 15min and 2.5 GB later it was done... wiped flashed no go would not boot... so back to recovery I choose my restore file... system says it was successful but when restoring the data it fails... I'm on twrp 2.5 ...then I tried to just restore the system when booting up I get that static image you see on cm flash every 5 sec but never boot nor goes inyo the boot animation...is there anyway to use this restore file... I just need the data part.. I have messages that i need to show my lawyer and numbers that I need... TiB won't restore my messages either....
Sent from my XT907 using xda app-developers app
You will need TWRP 2.6.3 / PhilZ / or a newer CWM that supports adb in recovery (not sure is 2.5 does)
First off, all of your pictures and other stuff are stored at "/data/media" or "/data/media/0" and are not "wiped" unless picked. These are both accessible in recovery, and you could do an "adb pull ....." to get those files to a PC. At this point you should have your pictures.
Sounds like Ubuntu messed some things up, and when you restored "/system" only it won't boot because of missing data. I once had a problem like this bouncing back and forth between 4.3 and 4.2. Assuming you were on a custom ROM, maybe try wiping completely including "/data/media" DO NOT WIPE "/DATA/MEDIA" IF YOU HAVEN"T BEEN ABLE TO PULL THE FILES VIA ADB IN RECOVERY!!! YOUR PHOTOS WILL BE GONE!!! Sorry for the bold caps, I just didn't want you to miss it. Next install your custom ROM, boot, and do enough setup to get to the home screen. Now go back to recovery and your backup should restore. From here you could "adb push ..." your files back.
Updating TWRP is one way to solve this in the future, like JB already posted. However, to remedy on 2.5, do a clean wipe prior to restore, mounting system prior. Then, restore only the boot.img from the ROM you want and then restore the full ROM you want. This is how I was able resolve this same issue. Hopefully, it will work for you.
I was on stock deodexed debloated prior to all this... after a few tries at the restore I just flashed that same ROM and used TiB to restore what I had on last back up... tonight I'll try and restore that twrp backup ... but either way I guess I'll be updating my recovery... I'm not worried about all my pics n what not I keep all that on the external SD card now...
Sent from my XT907 using xda app-developers app
If I backup my system on tw recovery, and flash a new rom, will wiping my phone delete the tw recovery backup in case I have to restore my phone? Feel free to correct me on this, but to my understanding teamwin has it's own partition, and wiping does not mess with this partition?
matthewbhass said:
If I backup my system on tw recovery, and flash a new rom, will wiping my phone delete the tw recovery backup in case I have to restore my phone? Feel free to correct me on this, but to my understanding teamwin has it's own partition, and wiping does not mess with this partition?
Click to expand...
Click to collapse
I think TWRP backups are normally stored on your internal storage partition, so if you perform a (EDIT full factory reset doesnt wipe this, thanks Silesh) or wipe your internal storage, your backups will be erased too. The TWRP itself does install to the recovery partition (which will only be affected by a flash to the recovery, which a wipe will not perform), you're correct on that but the backups are held separately to that. You can copy your backups to another computer or SD card, I found my backup under /SDcard/TWRP/BACKUPS - you could either copy the folder with a root browser or use the ADB pull command (with the ADB terminal), though the TWRP backup may not show on a Windows desktop even if it's been copied correctly. However, if copied back to your phone, the TWRP backup should function.
Edit: thanks Silesh for correcting me, I was thinking of app data rather than user data!
echo92 said:
I think TWRP backups are normally stored on your internal storage partition, so if you perform a full factory reset or wipe your internal storage, your backups will be erased too. The TWRP itself does install to the recovery partition (which will only be affected by a flash to the recovery, which a wipe will not perform), you're correct on that but the backups are held separately to that. You can copy your backups to another computer or SD card, I found my backup under /SDcard/TWRP/BACKUPS - you could either copy the folder with a root browser or use the ADB pull command (with the ADB terminal), though the TWRP backup may not show on a Windows desktop even if it's been copied correctly. However, if copied back to your phone, the TWRP backup should function.
Click to expand...
Click to collapse
Thanks for replying. I can't transfer files from my computer to my phone, but I have thought about using the ADB sideload option from recovery. Is there a way that I can move my backup from my phone to my computer (and to my phone from my computer) using the sideload option, just in case I need the backup? I refuse to flash a new ROM without access to my complete backup, lol.
Internal storage is not formatted during a normal wipe. You have to specifically go into the advanced wipe and select internal storage to wipe it completely. So there is no issue while flashing a new rom if you don't choose the advanced wipe option.
You could also create the twrp backup in your external sdcard. That way your backup stays even if you wipe your phone using a factory reset or by mistake.
Strange. What's the problem of making backups to external SD? The function is right there (as Silesh mentioned). BTW: the very last version of TWRP is able to make backups straight to pc. This needs to be done FROM a pc though. TWRP is capable to work with fastboot now (using special command though, or with this GUI for pc: https://forum.xda-developers.com/android/software-hacking/tool-twrp-backup-restore-tool-pc-t3572241 )
You can choose whether you want to use internal storage or SD card when making a backup. It doesn't matter which you choose as long as you (and I learned this the hard way) pay attention to what you are doing and DO NOT WIPE internal storage or your SD card. Advantages of SD card is you won't lose your backup if you decide to flash stock. Disadvantage: if your card craps out on you backup is lost unless you have copied to PC or saved on cloud.
My Solution
I solved my problem by using the pull command in adb. Now if I decide to flash a new ROM, I can push my TWRP recovery back to my phone using adb and then recover it in my TWRP recovery.. I also backup using adb backup which backs it up directly to my computer anyways.
I knew about storing my TWRP backup on an sd card, but I haven't made time to get one. . I recently switched to the Motorola G4 Plus after my iPhone 6s decided to turn off and not turn back on. I eventually grew tired of the iPhone anyways due to lack of accessibility and freedom. Back in the day I owned androids but never rooted one or had one that was rooted. I did jailbreak my 4th generation iPod a few years ago. But I went through an iPhone 5s, and upgraded to a 6s and had that for a few months. I eventually just switched back to android after the longest time and I can't say that I regret it.
My Moto G4 Plus has been an amazing phone. I've only had it for a few weeks now, but I rooted it the day after I got it . So I'm a bit of a noob in the rooting community, . Since then it's been a pretty smooth transition. I've only got root access and xposed framework as of now. I was thinking about flashing a ROM so I made backups just in case, but I don't plan on making any major changes to the kernel or flashing another ROM. I'm satisfied with the stock ROM since Motorola pretty much made it as minimal as possible. I would recommend this phone to anyone. It's the most solid phone I've had yet.