Model is P48WVB4 which I think is the Kindle Fire HD 7".
Software version is 11.3.2.2
I found instructions here: http://kfsowi.com/guides/root
If I understand them correctly, it is replacing the boot image with the older software version one.
Then rooting it.
Then replacing the boot image again.
My question is does replacing the boot image wipe the device?
I'm trying to root so I can either backup the clash of clans data with titanium backup to move it to another device.
Or so I can associate it with a google+ account.
So obviously I don't want to erase the data in the rooting process.
I tried backing up the data with Helium but it wouldn't backup clash of clans.
Will Rickards said:
Model is P48WVB4 which I think is the Kindle Fire HD 7".
Software version is 11.3.2.2
I found instructions here: http://kfsowi.com/guides/root
If I understand them correctly, it is replacing the boot image with the older software version one.
Then rooting it.
Then replacing the boot image again.
My question is does replacing the boot image wipe the device?
I'm trying to root so I can either backup the clash of clans data with titanium backup to move it to another device.
Or so I can associate it with a google+ account.
So obviously I don't want to erase the data in the rooting process.
I tried backing up the data with Helium but it wouldn't backup clash of clans.
Click to expand...
Click to collapse
i haven't checked the script for rooting a kfsowi, but replacing a bootimg doesn't in itself wipe anything, all the bootimg is is the kernel +intramfs. I don't think the rooting process on kfsowi touches the data partition outside of storing some temp data. Like i said i have not looked at the script to see how the process works yet though.
Edit: didn't see anything that looks like it will wipe it in the script!
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.
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
vagos696 said:
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
Click to expand...
Click to collapse
I don't trust TiBU. its a real mess for me. I for one backup my ANDROID folder, and flash all apps through recovery. and then copy back the Android folder on SDCARD.
How did you root your 4.3 image? Many custom kernels break root on 4.3. Try re-flashing SuperSU or re-flash ROM and stick to the stock kernel.
via Nexus Toolkit. I'm still rooted even after applied Franco, but I'll revert back to stock kernel just to check your possibility.
Even the saved TiBU apk's are not getting installed.
How can I re-install the broken apps which were affected from TiBU? As I mentioned even fresh installation from the play store is not processed.
I was hoping to avoid re-flashing and re-rooting from scratch.
Nope even with stock kernel I face the same problems. Any suggestions?
I guess there's something wrong with your /data partition. I'd either start over with flashing the factory image or at least format /data (not wipe, really format). Don't forget to backup your internal sdcard content first, it will be deleted with both methods.
Also I'd recommend not using a toolkit for flashing the factory image and rooting. It's easy enough using fastboot and a custom recovery. This way you'll be on the safe side, not missing any errors etc.
Make sure your TiBU directory is set to storage/emulated/legacy/TitaniumBackup, not storage/emulated/0/TitaniumBackup.
It worked for me, anyway. Well, after having to perform a factory reset, as it screwed up the UUIDs, that is
Thanks for the suggestion. You were right my path was storage/emulated/0/TitaniumBackup.
I revert it to the suggested one but I have the same issue.
Factory reset, start from scratch, initial path storage/emulated/legacy/TitaniumBackup
The same problem which also end up destroying the fresh apk as well.
Hopeless
Tell us exactly what you're doing. Which ROM / image, software, versions, procedure, all the details. Maybe something other well ring a bell.
As already quoted
1. Before updating to 4.3, I updated TiBU to the latest version and kept backup of the apps+data
2. Clean flash of stock 4.3 ROM (JWR66Y) via Nexus Toolkit
3. Root (Busybox, SU etc)
4. Flashing Franco Kernel r178
5. Installation of TiBU
6. Try to restore - PROBLEM
Plan B:
1. Factory Data Reset
2. BusyBox gone but still have root access
3. Stock ROM - Stock Kernel - Rooted
4. Install TiBU
5. Restoring - PROBLEM
Description of the PROBLEM:
I cannot restore apk's is getting into a loop and never ends.
I can restore data to an installed apk, but then the app crashes
I cannot re-install the (restored) app via playstore, I get "unknown error code during installation -24-"
Current situation
1. Factory Data Reset again
2. Franco r178
3. No restores via TiBU
Don't shoot me, but it still sounds like the TiBu 4.3 ROM backup folder path problem. Here's what I do and what works for me:
1. Open TiBu
2. Click on "Menu"
3. Click on "Preferences"
4. Click on "Backup folder location"
5. Click on "DETECT!"
6. Click on "Whole device"
7. Choose "/storage/emulated/legacy/TitaniumBackup"
8. Click on "Use the current folder"
9. TiBu will now ask if it should move the other backups to the new folder, say no.
10. Exit the preferences with the back key
11. TiBu will now reload with the new preferences
Now restoring should work if the path is the problem.
About loosing root with a custom kernel on 4.3 ROMs:
If you lose root by flashing a custom kernel it may still seem like root is active, i.e. the root frontend app will still be there and ask for root permissions etc. Try the following to ensure that TiBu is running with full root privileges: Uninstall some unimportant system application (some Gapp for example, like Google Currents - backup first if you need it). If uninstalling gets cancelled with a message like "Can't find the apk file", it's likely that root doesn't work properly.
Come on man, I hate to give up
Thanks for the inspiration but unfortunately:
1. I can unistall, backup and restore properly Google Currents (hence proper root)
2. Back up folder was set properly also by verifying your steps (2-10)
And again if I try to restore an old app (not the data) it gets to the familiar loop.
Ok. I'd now flash the full factory image, thus resetting every partition (backup internal sdcard first). Please try without a toolkit to be safe. You need the drivers installed (your toolkit should already have taken care of that) and have adb and fastboot ready. There are batch/shell scripts included in the factory image which invoke the fastboot commands in one step.
Next flash a custom recovery with fastboot and use it to flash SuperSU for root access.
Refrain from flashing a custom kernel now and try if you can successfully restore with TiBu at this point.
If you can, the problem was either one of your partitions/filesystems f_cked up or the toolkit doing something wrong.
Hello guys!
I was updating from 4.4.4 to lollypop via OTA, then I realized that even if I run the stock ROM, I am still unlocked + root, meaning that the OTA won't run.
I did a complete nandroid backup via Wugs Nexus Toolkit, including data.
Then I wiped and flashed the new 5.0 via Nexus Toolkit, but when I tried to restore only the data it didn't work.
I decided to go back to 4.4.4. and do things properly, but now I'm not able to restore anything.
I am not bothered with the apps and stuff, but I had plenty of pictures which I forgot to backup, and I want to restore them. I even tried to access the nandroid backup files, but no success!
I was accustomed with the old CMW, where you had the .img files, but I got no clue on what to do here!
I add the picture of the nandroid backup folder on my PC ( I think the data files are splitted, but I cannot open them in any case, not even with 7zip).
The nandroid was executed via Nexus Toolkit, but I guess it has been done through TRWP.
Long story short:
1) how can I access the pictures inside the nandroid backup?
2) how can I restore a nandroid backup that keeps failing?
theraizen said:
1) how can I access the pictures inside the nandroid backup?
Click to expand...
Click to collapse
Maybe CWM does things differently, I don't know, but with TWRP, a Nandoid backup doesn't back up your SD card partition, so if you wiped everything, all your pics are gone. Sorry.
Yeah, I guess so.. Managed to recover something with DISK DIGGER (its an app, free on the store). Just wanted to write it here, so if anyone has the same issue can recover this way!
I updated an old thread on this. Long story short I have another G5 plus and rooting it is going nothing like rooting the first one.
In theory, I should be able to just pull an image from the first one and use TWRP to restore it, skipping the EFS partition. I have the correct EFS backed up on the new G5 plus.
Currently the new phone has TWRP 3.2.3-1 installed and has the boot loader unlocked. I have the zip file for Magisk 16 but it is not installed. I was able to overcome many problems with the new phone booting after I tried to restore the image I wanted.
My goal is to have them both function the same.
Is it possible to use a backup I made with one phone on the other, or should I manually install everything?
Would attempting to use that backup corrupt it?
Restoring a backup from an identical phone on to a new one
shadow460,
Restoring a backup from an identical phone on to a new one. Will work just fine. I have done it before. After breaking a screen, pulling the sdcard & putting it in the other phone. And using TWRP to restore (clone) the original phone.
Ned
Is there any way to backup the data partition before you root the device? I've got the bootloader unlocked and TWRP installed (3.5.2_9-0).
Every time I've tried, it fails with error 255. I've looked at the recovery.log file and it seems to be failing as soon as it starts creating the tar file. One of the directories it's trying to copy does contain a comma in the name. Unfortunately, I can't rename it, even using the file browser in TWRP.
I'm going to install Magisk, but they say that will wipe the data partition and I've got some game data I'd like to keep, and the app is too old to support the app data backup that is built into android.
Installing Magisk doesn't wipe anything, at least I've never heard of it. The only thing that does wipe (at least on OnePlus) is unlocking the bootloader but you already did that.
You could try alpha backup, it doesn't look like it needs root to backup/restore but I'm not sure.