Develop Bugs

Backup/Restore N2E

Backup/Restore N2E OS X/LINUX
Rule one: Make a backup of your factory fresh Nook ROM.
Linux/Mac: Become root
Boot nook with noogie.img and connect to your computer via USB.
New link here
Linux:
use df -h to get your nook's /dev/sd? address.
typically something like: /dev/sdb
OS X:
use diskutil list to get your nook's memory address.
typically something like: /dev/disk3
Once you know the address, unmount the Nook.
Code:
Linux: umount /dev/sdb*
OS X: diskutil unmountdisk /dev/disk1
Make the backup
Code:
Linux: dd if=/dev/sdb of=my_backup.img bs=1M
OS X: dd if=/dev/disk3 of=my_backup.img bs=1M
After it is finished, double check and make sure the backup img file is exactly 1958739968 bytes long.
dd can wipe your computer's hard drive, so be careful! Make sure your're plugging the correct drives into the command above.
Restoring your N2E to factory-fresh is a simple reversal of the commands above:
(boot with the noogie sd card first!)
Code:
Linux: dd if=my_backup.img of=/dev/sdb bs=1M
OS X: dd if=my_backup.img of=/dev/disk3 bs=1M
Substitute sdb or disk3 above with your Nook's actual address.
This wipes your N2E, restoring the specified image file.
Windows users, see the next post.

BACKUP/RESTORE N2E Win7
Grab a copy of Roadkil's free DiskImager for backup and restore. http://www.roadkil.net/program.php?ProgramID=12
and a copy of free MiniTool Partition Wizard at:
http://www.partitionwizard.com/
Boot nook with noogie.img : http://nookdevs.com/NookTouch_Rooting (the "Rooted Forever" screen) and connect to your computer via USB.
Use DiskImager to copy your Nook partition to a file, being sure to select "Physical Disk" in the drop down list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the process completes, you now have a backup.
To restore your backup:
(Boot Nook with the noogie sd)
Run Partition Wizard and delete all partitions on your Nook. Careful in disk selection here, wiping the wrong drive could be catastrophic! This is required, because DiskImager won't write to a partitioned drive.
Now run DiskImager and restore your backup to the Nook drive. When done, pull the noogie sd card from the Nook and reboot.
You should be fully restored now.

jocala said:
Rule one: Make a backup of your factory fresh Nook ROM.
Click to expand...
Click to collapse
Well that's probably quite a lot of us early adopter hackers stuffed, then.

Loccy said:
Well that's probably quite a lot of us early adopter hackers stuffed, then.
Click to expand...
Click to collapse
Then make a backup now. For most of the stuff that's being done, a factory restore will put you back to pure stock.

jocala said:
Then make a backup now. For most of the stuff that's being done, a factory restore will put you back to pure stock.
Click to expand...
Click to collapse
Already doing so - my current state is quite solid at the moment so it'll do as a known good restore point, if not as a "get me back to being a virgin" state.
Factory restore only seems to wipe /data, though - so anything you've done in system is not restored to stock.

Loccy said:
Well that's probably quite a lot of us early adopter hackers stuffed, then.
Click to expand...
Click to collapse
I'm stuffed too. Is there any hope of a full factory install method that doesn't include making an image of the original ROM?

cymoze said:
I'm stuffed too. Is there any hope of a full factory install method that doesn't include making an image of the original ROM?
Click to expand...
Click to collapse
I don't see one on the horizon because the /rom/devconf data is individual to each N2E. Hopefully, I'm wrong.
As long as you're not currently in a horrible broken state, can't you force a factory refresh then backup?

may you can add the link for the nookie.img ?!
thank you

rev0l said:
may you can add the link for the nookie.img ?!
thank you
Click to expand...
Click to collapse
Done, thank you for reminding me.

jocala said:
I don't see one on the horizon because the /rom/devconf data is individual to each N2E. Hopefully, I'm wrong.
As long as you're not currently in a horrible broken state, can't you force a factory refresh then backup?
Click to expand...
Click to collapse
I did that and was able to backup. I noticed my 1.82GB image was actually on Physical Disk 7, but other than that it went by the book.

cymoze said:
I did that and was able to backup. I noticed my 1.82GB image was actually on Physical Disk 7, but other than that it went by the book.
Click to expand...
Click to collapse
I'm glad it worked for you.
Sent from my SPH-D700 using Tapatalk

Hi,
I made my backup without umounting the nook first (sadly, this step isn't mentioned on the rooting guide on NookDevs...) ,
tryied to restore it seems I bricked my nook... stuck at boot time.
it seems that (at least) /boot/uRamdisk is defected, thus my nook is not booting
I've wrote everthing here... but seems that the relavant part is what I wrote above...
http://forum.xda-developers.com/showthread.php?t=1149714
EDIT: seems that umounting before restoring and then restoring again solved the problem... aperantly the image was OK after all.

Fresh NookieT backed up, thanks for the guide.

You're welcome

And after some problems with TouchNooter I was able to restore to that image too! Thanks again.

I rooted my Nook Touch then decided to try to return back to original "virgin" state. I successfully backed up (verified the file size was 1958739968 bytes) and restored but after I registered my Nook and then restarted, the screen with the android logo and prompt appeared.
I can skip all the Android stuff but one thing I found that I can't do anymore is link to facebook in settings.
It seems if you didn't back up your ROM before you rooted, you will never be able to return to the original state. Hope I am wrong. If B&N release an update, will that help clean the Nook and free it of touchnooter?
Any help is appreciated

homesik_alien said:
I rooted my Nook Touch then decided to try to return back to original "virgin" state. I successfully backed up (verified the file size was 1958739968 bytes) and restored but after I registered my Nook and then restarted, the screen with the android logo and prompt appeared.
I can skip all the Android stuff but one thing I found that I can't do anymore is link to facebook in settings.
It seems if you didn't back up your ROM before you rooted, you will never be able to return to the original state. Hope I am wrong. If B&N release an update, will that help clean the Nook and free it of touchnooter?
Any help is appreciated
Click to expand...
Click to collapse
Yeah I had a similar problem. It seems you can't actually factory restore it. It gets rid of the launcher you installed but whenever I've tried doing the restore it's only a matter of time before the "Tap on the Android to begin" part reappears.
So I've re-rooted, and am leaving it as be until better progress comes out. I don't have market or Gmail working, but Kindle and other apps I need to work so I'll make due for now. I don't want to risk bricking the device as I'm in Canada and there's no Barnes and Nobles to return the Nook to,

oops - tried following these instructions for my Nook Color. DOH

Figured I should post this incase anyone has a similar problem.
After I made my backup, I began the process to restore. I opened the Partition Magic program and deleted all the partitions on the Nook device. I then opened up Win32 Disk Imager, tried to load up my backup and got this error:
"An error occurred when trying to get the devices geometry. Error 8:".
I tried it on another machine, same thing. The workaround for that problem is going into device manager and disabling your Floppy Disk controller and Floppy Drive. Also, moving the Nook backup image you made to the root of your C drive may work.
Or just try the Linux method, much easier

who can give me a backed up file, I use linux and use 'dd' command ,but the file is wrong ,so my nook touch can not be use anymore. I need a full backup file to recovery it . Where can I download this file ? Thanks.

[ROOT](11-17-12) Root Nexus 10 with CWM and SuperSu Zip (Stress Free and Simpler)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Updated 11-17-12: Now that we have a stable CWMR image thanks to damien667 this procedure should be a lot less risky and less stressful!
This is confirmed working but due to the procedure involved is risky! The standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your tablet by following this procedure!​
You must unlock the bootloader before performing this procedure!
Credits: Kidgoo for testing and coming up with the method, thanks to damien667 for the fixed CWM images, and Chainfire for the SuperSu zip and binaries!
Before you begin make sure you read and reread the procedure and fully understand the directions.
1. Download the CWM-SuperSU-v0.98.zip
2. Download damien667's fixed CWMR 6.0.1.6 touch version of from here
3. Connect the Nexus 10 to your computer
4. Flash the CWMR image you downloaded in step 2 using fastboot
Code:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
5. Touch "Install from SD Card" in CWMR
6. Select CWM-SuperSU-v0.98.zip that was downloaded in step 1
7. Let CWM-SuperSU-v0.98.zip install
8. Select "Reboot System"
9. Enjoy your rooted Nexus 10 !
To keep your custom recovery installed permanently and not get overwritten by the stock recovery when your reboot your tablet delete the following:
Code:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p

Reserved

works! thank you very much!

Awesome!
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!

WannaB101 said:
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!
Click to expand...
Click to collapse
One-Klick CWM Tounch + SuperSU would be great!!! :good::good::good:

So what am I supposed to do if ADB doesn't recognize the "sideload" command?

gravis86 said:
So what am I supposed to do if ADB doesn't recognize the "sideload" command?
Click to expand...
Click to collapse
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.

Perhaps a video?
Perhaps you could provide a video to help us along?

shimp208 said:
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.
Click to expand...
Click to collapse
Yep, my ADB was out of date... Thanks!

Got the latest version of ADB?

With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?

WannaB101 said:
Perhaps you could provide a video to help us along?
Click to expand...
Click to collapse
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!

shimp208 said:
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!
Click to expand...
Click to collapse
I hit ya with a question above...

joeski27 said:
With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?
Click to expand...
Click to collapse
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.

I know this is probably a noob question but the fastboot commands (the first two, for booting from CWRT) -- should they be done in Fastboot Mode or can they be done while Nexus 10 is on and at home screen with USB debugging enabled? If you need to be in Fastboot Mode, how do you get there with Nexus 10?
Thanks!

shimp208 said:
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.
Click to expand...
Click to collapse
Ok, the problem I have now is while I have the files on my tablet, I cannot move them to the root of the internal storage at this point...??? Suggestions??? Don't you have to be rooted in order to do this???

For some reason when I'm not in fastboot mode, I can use adb (adb devices lists my Nexus 10), but when I'm in fastboot mode, adb no longer recognizes the device. fastboot devices does however see it when in fastboot mode.
Anybody else have this problem or know why this might be happening? Thanks!

I'm still getting the sideload error after updating the ADB
Any insight, please?

So to others who are working on this and awaiting responses from the OP, where exactly have you placed the downloaded files on your tablet? specific locations?? and if so how did you get them there? I'm totally lost at this point, LOL, hoping to get some clarification soon...

Worked ... however .. you DO have to be in FASTBOOT already (power + Vol UP + Vol DOWN) - yeah it might be obvious when you're not tired as hell - but for those wondering
The first line should be:
fastboot boot /path/to/<recovery>.img
no fastboot reboot was needed - it rebooted itself.
I had a HELL of a time finding the sideload entry in CWM (that's just my brain deadness).
You have quite a bit of time More than enough.
THANK YOU!

start from a clean slate

Well Here I go again! Got my rooted KFHD 8.9 running 8.4.8 all fouled up and want to start again. I have no backups made anymorre since iaccidently deleted them. What has happpened is i tried to load google apps using kffirstaide but some how messed itup i have gone back to factory settings but after that i still have the google store su and es explorer loaded into my machine. also i have a bunch of theggogle apps slowinginmy aps folder but theydnt workand are i think partially loaded and NOT if i use es explore i see them in my system/aps folder but they dont work what i would like to do is remove everything but what is loaded on a factory reload except keep root google store and su and es3 HOW??????????? do i do that i thought a factory restore would clean out that folder but it doesntso now i halfway between a rock and brick job lol? Please someone have mercy on this ignorant tinkerer. Thx

larryb1951 said:
Well Here I go again! Got my rooted KFHD 8.9 running 8.4.8 all fouled up and want to start again. I have no backups made anymorre since iaccidently deleted them. What has happpened is i tried to load google apps using kffirstaide but some how messed itup i have gone back to factory settings but after that i still have the google store su and es explorer loaded into my machine. also i have a bunch of theggogle apps slowinginmy aps folder but theydnt workand are i think partially loaded and NOT if i use es explore i see them in my system/aps folder but they dont work what i would like to do is remove everything but what is loaded on a factory reload except keep root google store and su and es3 HOW??????????? do i do that i thought a factory restore would clean out that folder but it doesntso now i halfway between a rock and brick job lol? Please someone have mercy on this ignorant tinkerer. Thx
Click to expand...
Click to collapse
just use kindle fire first aid to restore the stock rooted os, that should get rid of google play and do what you want if i read this right. Esfile explorer should stay on the device since it installs to the userdata partitoin, and google will have to be reisntalled. Or you can delete things manually over an adb shell, but it would take more doing than just restoring with kffa.

stunts513 said:
just use kindle fire first aid to restore the stock rooted os, that should get rid of google play and do what you want if i read this right. Esfile explorer should stay on the device since it installs to the userdata partitoin, and google will have to be reisntalled. Or you can delete things manually over an adb shell, but it would take more doing than just restoring with kffa.
Click to expand...
Click to collapse
so whats gonna be the effect since im running 8.4.8 and none of the restores are that version? or can i restore to an earlier os update and reroot?

That's what those do, they downgrade to a previous is that is pre-rooted. I don't think ota's are disabled by default so it will probably update at some point back to 8.4.8 and clear any changes on the system partition like rooting and alternate launchers and such. These kinda things are the reason I left amazon os and haven't used it for almost a year.
Sent from my Amazon Kindle Fire HD using Tapatalk

Stack on kindle fire boot logo
Hi - i see that i have same problem...
I was made succesfull root, than i putted TWRP recovery, made a backup, and full wipe, than i realize, that i forgot to load CM11 rom... So i restarted device, enter TWRP, and make a restore of backup...
After that, after reboot, the device just show static orange kindlefire logo...and that is all.
Only thing I can do - is to enter * using CMD line * to the fastboot mode.
Now i am trying to restore kindle using KFFirstaide - but i get errors because of that there is no files to download from dropbox...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also tried SRT, and it looks like it works, something was loaded, but after that, still have static logo, nothing more..
HELP

My adventures with my ZenWatch over the weekend

I spent a lot of the weekend trying to root my Zenwatch (on 4.4.2w), or get a custom recovery working. Here's what I have tried and found out so far. They locked it down pretty damn well.
Unlocking bootloader and accessing recovery
Go to Settings -> About -> Press Build Number 7 times -> Swipe right, Developer Options now shows under About.
Theres a few different options including an Asus utility to check sensors and such.
To get into recovery or fastboot, you need to active ADB Debugging, unplug the watch than plug it back in, then run "adb reboot recovery" or "adb reboot fastboot"
To unlock bootloader, you need to push the reset button on the back to select.
In recovery, swipe right to left to show screen, up and down to select, and left to right to select.
My Findings so far
The kernel source and ROM source are not available anywhere.
There is no way that I can find to get root. I even went as far as loading towelroot onto the watch through adb install, but it just hangs and eventually closes.
There is no way I have found to build a custom recovery with CWM or TWRP.
There is no way I have found to dump the boot or recovery partitions.
There is no su binary preinstalled. Attempting to link a su binary has come up null.
dump_image binary is not installed, nor can you get it to install.
Trying to install any packages through stock recovery gives signature error.
Trying to use dd command to dump boot or recovery ends with "permission denied"
Trying to use "fastboot oem saveprt2sd recovery -n recovery.img -a" ends with "invalid page size". Same with trying to dump boot in this fashion.
Trying to boot either the LG G Watch or Samsung Gear Live unsecured boot images comes back with "(remote) dtb not found" (No surprise here, but it was worth a shot)
fstab is root only.
/dev tree is root only.
all init.asus scripts are root only.
You can install packages with "adb install" but all the standard root gaining apps stall or force close. Towelroot seems to try, but locks up after hitting "make it r4in." trying to change the modstring on v3 (with triple tap title) does not provide a field to change.
Kernel command line is root only.
I browsed EVERY file on my watch hoping to find a hole that I could build off of, but alas, I had failed.
Even trying to do "adb backup" results in "Confirm on Device," and closes immediately afterwards, with no confirm.
I believe that unless they release either the kernel source or the full ROM source, we are unable to root or modify any options.
Which really sucks, because the "OK Google" screen is REALLY F****** BRIGHT.
if anyone has success, please share

I thought I'd try installing one of my own apps and see what happened. It installs okay, but it crashes immediately. I'm guessing it's because I'm using something that's not supported, probably sound or Webkit (the app displays an HTML tutorial the first time it's run). I haven't had time yet to run it from the debugger and see what's going wrong.

I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/

dgjenkins said:
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
Click to expand...
Click to collapse
To build a custom recovery, you need to pull the existing recovery or boot partition off of the device and pull partition information (fstab, which is not readable by user on this device) and the build.config information (which is also not readable by user), or pull the fstab.anithias and build.config from the running system (which again is not accessible to the standard user account).
Without that information, you can't build a custom recovery. I've been attempt this for almost 2 weeks now, and its locked down pretty well. The G Watch and Gear Live allowed access to the needed files, but Asus did not with the ZenWatch.
If anyone is willing to risk bricking their watch (by getting past the dtb error when trying to boot the LG G Watch or Samsung Live recovery images, which is a long shot in itself) to get the openRecovery/CWM/TWRP to install and work to the point of getting ADB working through recovery mode, I can do the rest to build the recovery.
I just dont want to risk bricking mine quite yet, as the google play store was out of stock the last time I checked to purchase a "testing" watch.

@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip

CSX321 said:
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
Click to expand...
Click to collapse
Kernel source code
Sent from my SM-G900P

@z3nful And an ota? Would it be usefull?
OTA LWX48S

I haven't had a chance the last week to work on this with the holiday season going on and having to run my store. When I get a chance to get back to it, I'll let you guys know what I come up with

I started trying to build the kernel yesterday, but I'm not getting far yet. I've been a developer for over 30 years, but most of my Linux/other UNIX experience was over 10 years ago, and I've forgotten a lot.
I've tried a couple of different compiler versions, but I'm pretty quickly running into different issues with either one. I'm not sure what version Asus used, but it's apparently not either of the ones I've tried. Also not entirely sure what configuration to use. I'm using the 8226 configuration now, because there's no 8026 configuration in the source archive. I don't know if that's suitable or not.
All-in-all, I may not be out of my depth, but I'm out of my area of experience, at least. Any tips, @z3nful?
Edit...Is there any useful information in the OTA zip file? It's available. Partition info or a boot image or something?

@z3nful and @CSX321 - Any luck moving forward on this? I'm not a programmer, but I'd be glad to offer any assistance if needed!

btonetbone said:
Any luck moving forward on this?
Click to expand...
Click to collapse
No progress here, I'm afraid. I think I just don't know enough about this environment to do it, without devoting a lot more time to learning.
I've also lost some motivation, because there doesn't really seem to be anything I need root for on the watch. About the only thing I would do if I had it is delete a couple of apps, but since Mini Launcher lets me hide apps, I don't care so much about actually deleting them.

Has anyone had success with adb push? It seems the system is read only and doesn't allow for pushing files. Is root required?

Asus is good at locking down their devices, requiring you to register it with them to get an app to unlock it (you also acknowledge that by downloading the app you are voiding your warranty). I really wouldn't be surprised if they did the same thing with this watch and just haven't released the unlock app yet.
I am kinda disappointed to see this sort of thing from a device licensed by Google. It's like the exact opposite of the Nexus line.

@z3nful Just some helpful links, thought I could help a wear user out (I have the G Watch)
Kernel --> https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release
Also, Gohma ROM for gwatch includes a boot img that auto roots android wear. (http://forum.xda-developers.com/g-watch/development/rom-gohma-2-0-12-15-2014-t2974052) Named rboot.img, I think it might be worth a shot to run "fastboot boot rboot.img" to see if it does anything.

Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.

I tried, no luck.. Gave the same "dtb not found" error.
Here is a thread related to DTB in boot images: XDA Topic 2428117
Attached is the rboot.img if anyone wants to see if they can modify it to pass whatever DTB issue is making it fail, if that's even possible. I will dig a little bit deeper once I get out of the office.
The error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rboot.img, zipped:
View attachment rboot.zip
Ignore my sig, it is several years out of date
Regards,
weasel5i2
Doc Ames said:
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
Click to expand...
Click to collapse

[Q] Bloatware that is safe to remove?

Which packages did you guys remove?
I am happy that I could remove Firefly with Titanium Backup.
The app started randomly, in my pocket (I presume the camera button got pressed against My pocket), and I never really used it anyway.
I would like to know what does Whisperlink and if it is safe to remove.

arth_ur said:
Which packages did you guys remove?
I am happy that I could remove Firefly with Titanium Backup.
The app started randomly, in my pocket (I presume the camera button got pressed against My pocket), and I never really used it anyway.
I would like to know what does Whisperlink and if it is safe to remove.
Click to expand...
Click to collapse
Personally, I believe Firefly is a nifty little app that doesn't affect the phone in any way to actually consider removing it. But, well, to each his choice, right?!
Anyway, Whisperlink is an app that syncs your Kindle books info - purchases, reading progress, highlights 'n notes - across other amazon devices.

Amazon Appstore

The single issue is that it often starts up in my pocket and drains my battery.

[deleted]
NEW version here - http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008

Bingo Bronson said:
FireOS 4.6.1 (KK 4.4.4)
Things I have removed so far: ........
to free up system space.
Used 'SD Maid' to scan for leftover "Libs" and other obsolete files.
Click to expand...
Click to collapse
And so after all these have been removed, how much free system space do you have, and do you think it is making an observable difference in terms of performance?

Bingo Bronson said:
FireOS 4.6.1 (KK 4.4.4)
Things I have removed so far:
REMOVED
Apps used (for now):
F-Droid Repo: AdAway, AFWall+, Amaze File Manager, ApkTrack, Autostarts, Calculator, Camera, Kernel Adiutor, Kitchen Timer, MuPDF, Sound Recorder, Swiftnotes,
VA: BusyBox, Buzz Launcher, Dolphin, KingUser, Multiling O Keyboard, MX Player, RAR, SD Maid, Titanium Backup, WhatsApp, Wifi Analyzer, WiFi File Transfer Pro
I removed all the lockscreen scenes (including \system\etc\com.amazon.lock\files\lockscenes\ls_moon.vbl) and used a black 1x1 px jpg instead, Amazon stock lockscreen.
I deleted \system\euclid , \system\media\fremedia (bootanimation.zip & boot.wav as well) and \system\tts to free up system space.
Used 'SD Maid' to scan for leftover "Libs" and other obsolete files.
Click to expand...
Click to collapse
Very radical list but thanks for trying each app. I just wonder if you remove com.amazon.device.settings then how can you change any setting in your system ever?

@ O.a.T. The perfomance hasn't changed that much, feels just as fast as running it with disabled "dynamic perspective". I am just trying to get the system as lean as possible. I will encounter problems with the current configuration, no doubt, so I will update the list in the future. System partition: 733 MB used, ~ 1,38 GB free.
edit: Battery life benefits the most from these changes, of course, using apps like 'Kernel Adiutor' or 'Kernel Toolkit' have the biggest influence compared to disabling / removing apps and services. Installed 'Greenify' for a couple of minutes, tells me "no apps need to hibernate" (big surprise ^^).
@ najoor The system settings is called 'Settings' / 'Settings Storage' (AmazonSettings.apk, 99% sure it's the main settings app ^^). 'com.amazon.device.settings' is a different component, so even with this one being removed, access to the settings menu works as usual.

Anyone know to reinstall fresh firephone OS ?
I messed up something and want to reinstall it. But, the "factory reset" just reset setings and won't recover, or reinstall fresh FireOS.

stunvn said:
Anyone know to reinstall fresh firephone OS ?
I messed up something and want to reinstall it. But, the "factory reset" just reset setings and won't recover, or reinstall fresh FireOS.
Click to expand...
Click to collapse
You can find the latest FireOS ROM in one of the Topics here on XDA and then if you are rooted, I believe, you can use Flashify from the google play store to install.
Personally, I rooted, and created a nandroid and a titanium backup of my current setup and all the apps before I started tinkering with the OS.
Or maybe this ...
http://forum.xda-developers.com/fire-phone/general/how-to-update-fire-phone-to-fireos-4-6-t3085745
is even easier.

What O.a.T. said, or try this as an alternative gah, ninja'd and edit by O.a.T. nevermind
1. Download the *.bin file (FireOS 4.6.1)
UK - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin
GER - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-34.4.6.1_user_461013320.bin
US - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin
I strongly recommend using a download manager to speed up the download. Regular download with a browser is tedious.
2. Boot phone in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin

Bingo Bronson said:
What O.a.T. said, or try this as an alternative gah, ninja'd and edit by O.a.T. nevermind
1. Download the *.bin file (FireOS 4.6.1)
UK - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin"
GER - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-34.4.6.1_user_461013320.bin"
US - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin"
I can't post links yet, just copy the above mentioned file name of your choice, your browser will be able to download it.
2. Boot phone in recovery: PWR + VOL. UP
Choose "install update from ADB" (something like that...)
3. adb sideload "name_of_your_chosen bin_file"
I recommend renaming the the downloaded file to "update.bin" so can just type in cmd: adb sideload update.bin
Click to expand...
Click to collapse
I followed those steps and have trouble at step 3. Device not found. Do you know how to fix this?
I tried to run adb devices but nothing show up. It's weird. because, before that I still can see my device on the device list.

stunvn said:
Do you know how to fix this?
Click to expand...
Click to collapse
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method. That's why your phone "disappears" as soon as you (re)boot into ADB.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try this tool (& driver) http://forum.xda-developers.com/showthread.php?t=2588979
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload"

Thank you very much :fingers-crossed: :good::good::good::good::good: