Develop Bugs

[Q] FP1 - 1.6 unified storage upgrade: Problems

hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.

fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/

_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.

hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?

see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642

Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...

jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.

Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…

Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.

_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse

[Q] Can I flash the OTA zip in TWRP?

Finally, the OTA came out. But it's still not available in my area here (Malaysia) so I have to wait for it to come. But I'm a little short of patience here, and while the OTA zip files is out, I thought I could just sideload it via adb. But when I try to make it work, I spent 4 hours facing some adb problems. I'm using Linux most of the time, and I have Android SDK downloaded. It was so troublesome to make adb work. Initially adb just couldn't find my device. So I Googled about it, and did some modifications on the PC to solve the usb problem and finally adb could connect to my device (while in Android). Then I started to follow the instructions to sideload. I booted into TWRP recovery using adb command and just to be sure, I ran ./adb devices again while the device is in recovery. But then adb shows no device connected. Trouble. I thought it's the problem with some drivers so I used Windows to try it again. Same problem again. Then I started to Google about it and found some forums that mention that it only works when I manually boot into recovery (Volume Down+Power+Volume UP). I followed. And finally, it solved it. It was only the first problem. Then I pressed into adb sideload mode in TWRP and started sideload mode. And just to be sure again, ./adb devices, no device connected again. I thought it's some bug in TWRP, I stopped sideload mode, and went back to the main menu of TWRP (where adb once can detect the device) and ./adb devices again. Guess what, it shows no device again. Problematic. I restarted my pc for many times, switching from Windows and Ubuntu for many times, repeated the above steps for many times, but the problem is just so random. I even changed the usb cable but no luck. So I decided not to use adb anymore and I've Googled for just flashing ota in TWRP. But there's just very few articles on it. Most of them are using adb and stock recovery. Some of it mentioned that if custom recovery is present then it shouldn't have to be so complicated but none of them shows how to use custom recovery. And one of them says I could just flash the OTA zip file through custom recovery but no instructions for it. The last one is my ideal method now, but because of lack of references, I'm not sure about it.
In short:
-Nexus 7 with TWRP
-problems when using adb to communicate with my device whether it's in normal boot, TWRP recovery, sideload mode, or whatever
-problem is so random and I cant figure out whats the problem
-tried installing and uninstalling and installing drivers again and again
-I dont wanna lose my data
-fed up
Question:
Is the OTA zip file recovery flashable? I dont wanna mess with adb anymore. It just wont work properly with me. Or I have to wait for OTA to reach me?

Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.

jj14 said:
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
Click to expand...
Click to collapse
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?

ImjuzCY said:
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
Click to expand...
Click to collapse
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.

jj14 said:
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
Click to expand...
Click to collapse
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.

ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
cool! (it will almost certainly require a new XPosed app because of all the changes that Lollipop brought, but it won't hurt to leave it installed)
Edit: Just read http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5 - looks like you will need to uninstall XPosed too

ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5

[Q] Senior needs help rooted Nexus 7 and lollipop update

Please help and please be kind and patient with this senior citizen.
I have a rooted Nexus 7(2013). It is rooted at 4.4.4.
I saw the released Android updates to lollipop that I want to use and I need help with the procedures as I have to deroot my Nexus 7 first?
I also want to break it down to steps.
I assume that to update to lollipop, I would need to:
Backup using Nandroid
Deroot my Nexus.
Go to the Android site, then update to the latest version of lollipop.
When the upgrade if over, then re-root.
Even, though I was able to root my Nexus 7, I have forgotten many of the specifics.
Please help guide me as I think I need to:
Backup my Nexus 7 – I have both Titanium Backup Pro and Nanroid Backup Pro
Should I use Nandoid Online backup to ensure I can recover?
Nandroid Settings - Please help me with these Nanroid settings aftger selecting Custom Backup.
Backup Name – UTZ Timezone
Type – TWRP or Clockworkmod – I assume I select TWRP
Normal Backup Mode?
Do I select any of Yaffs2 as Tar or Exclude Dalvik Cache, Exclude Google Music Files.I have to admit, I have no idea what Dalvik and Yaffs2 are.
I will move to TWRP backup to my PC because it winds up being about 3gb and I haisve a 16gb Nexus 7.
This is where I get very confused. What exactly do I do and use start the derooting? Should I use the WugFresh(1.99) toolkit?
After derooting, I should NOT restore anything. I do an upgrade of Android to lollipop.
After my Nexus 7 is lollipop, I would need to do a recovery/restore of my Nandroid backup??
I have the following products that might help:
Titanium Backup Pro
Nandroid Backup Pro
BusyBox Pro
SuperSu
Root Checker Basic
NoBloat Free
Thank you for your time, expertise, kindness and patience in advance
Jon

Need a little more information. Understand you are rooted, but do you have custom recovery installed?
You actually don't need to remove the root before you update to lollipop if you use a factory image from Google.

Nexus7 and lollipop
SwoRNLeaDejZ said:
Need a little more information. Understand you are rooted, but do you have custom recovery installed?
You actually don't need to remove the root before you update to lollipop if you use a factory image from Google.
Click to expand...
Click to collapse
This is where I get confused and think that I am overcomplicating things.
I don't know if I have a custom recovery installed? I assume that I would have had to have made one. :crying:
How can I check? In Nanroid?
Can I make a new one?
It is great if I don't have to remove the root to upgrade to lollipop. When I was promoted by Google to update to lollipop, it failed, because I was rooted.
The bottom line is that I want to upgrade to 5.x and want my Nexus 7 rooted. :good:
Please tell me what information you need.
Thank you,
Jon

jolo100 said:
This is where I get confused and think that I am overcomplicating things.
I don't know if I have a custom recovery installed? I assume that I would have had to have made one. :crying:
How can I check? In Nanroid?
Can I make a new one?
It is great if I don't have to remove the root to upgrade to lollipop. When I was promoted by Google to update to lollipop, it failed, because I was rooted.
The bottom line is that I want to upgrade to 5.x and want my Nexus 7 rooted. :good:
Please tell me what information you need.
Thank you,
Jon
Click to expand...
Click to collapse
Alright, so the fact that your Nexus received the prompt to update tells me that you do not have custom recovery installed.
What you are going to want to do (easiest way to update as far as I am concerned) is just flash a factory image from Google. In order to do this, you will need to get your hands on a few things first:
1.) Windows PC/Laptop
2.) Micro USB cable
3.) ADB and Fastboot files (http://forum.xda-developers.com/showthread.php?t=2588979)
4.) Factory Image from Google for Lollipop for the N7 (https://developers.google.com/android/nexus/images - If you have the 2013 N7, get the one that says 5.0.1 (LRX22C) under the heading "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)")
5.) ADB/Fastboot USB drivers (your Nexus should install them when plugged in while booted to the Bootloader)
Now, download the ADB and fastboot files. Go to that thread, and follow the instructions to install ADB and Fastboot SYSTEM WIDE so that ADB and Fastboot will work from any directory (makes the rest of this process VERY easy). Once you run through that installer, and everything is good, download the system image listed above. Once it is downloaded, go to the directory it was downloaded to, and UNZIP it (right click it and select Extract here, or open the file and select Extract All).
Now, power off your N7, and then power it on, holding VOLUME DOWN. You will be booted into the BOOTLOADER, this is known as FASTBOOT MODE. Now, connect USB cable to the Nexus 7. The computer will probably say "Installing Device Driver Software". Let it finish. Now, press the START button, and in the search box, type CMD. A command window will open up. Type in the following without the quotes: "fastboot devices".
Now it should show something like this:
Code:
List of attached devices
HJFK54HSWE fastboot
If it says nothing, then the drivers are not working. Reply back to this thread, and I will explain how to update the drivers (don't want to confuse you now). Now assuming that everything is working correctly, all you still have to do is flash the 5.0.1 factory image. Close the command window that is open, and go to the directory where you downloaded the factory image. There is a file inside that folder called "flash-all.bat". With the tablet connected and in fastboot mode, double click the flash-all file. That will do EVERYTHING necessary to flash the factory image, and your tablet will reboot in lollipop.
Now, I don't think this will overwrite the root. If it does, and when you reboot, SuperSU or Superuser (whichever you were using before) isn't in your app draw, then reply here, and we will root you up.

"Factory Images "razor" for Nexus 7 [2013]
Why the hell is it named 'razor' in DL area?? This machine is 'FLO', right???

Razor is the name for all 2013 Nexus 7s. From there, you have deb and flo to differentiate between the LTE and Wi-Fi models.

nhizzat said:
Razor is the name for all 2013 Nexus 7s. From there, you have deb and flo to differentiate between the LTE and Wi-Fi models.
Click to expand...
Click to collapse
Actually, Razor is Google's code name for the Flo, and the Deb is the RazorG. Just like the Nexus 9 is the Flounder on XDA and Volantis on the Google image site. There are almost always two code names for Nexus devices (the community code name, and then Google's, just to keep everything as confusing as humanly possible..)

^^ LOL, but how totally stupid. In their own factory images download area, there are SEPARATE download areas for WIFI/LTE... why in God's name don't they use DEB/FLO? -______-

Nexus 7 (2013) LTE is not coming up

Hi there,
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...

vadim_se said:
Hi there,
Do not PM me for questions. Next time I'd not reply to PM questions.
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...
Click to expand...
Click to collapse
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply

Hnk1 said:
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply
Click to expand...
Click to collapse
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...

vadim_se said:
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...
Click to expand...
Click to collapse
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

Hnk1 said:
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.

vadim_se said:
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.
Click to expand...
Click to collapse
I'm glad everything is working fine. Unlocked boot loader isn't a problem at all. All of my devices are developer unlocked . So it isn't a problem if you like flashing/changing Roms.
Just keep it as you feel comfortable. If you have any other queries /questions, quote me and I be glad to answer your questions.

Erased my Fire HD 8.9 - Can it be saved?

I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!

rebelduke said:
I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!
Click to expand...
Click to collapse
Try to reboot into TWRP (press + hold volume up as soon as you see the first logo, keep holding till you see the TWRP curtain). If you are successful, copy a ROM zip into the kindle's internal storage (gapps are optional, but I recommend you flash them along with your chosen ROM), flash it, reboot, and cross your fingers.

Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!

rebelduke said:
Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!
Click to expand...
Click to collapse
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!

monster1612 said:
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!
Click to expand...
Click to collapse
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.

rebelduke said:
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.
Click to expand...
Click to collapse
From the TWRP FAQ for the sideloading feature:
TWRP versions 2.8.2.0 and higher will stream the zip from your PC without storing it on your device. If you wish to store the zip on your device for later, you should not use sideload and instead use adb push or some other method to copy the zip to the device.
Click to expand...
Click to collapse
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.

monster1612 said:
From the TWRP FAQ for the sideloading feature:
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.
Click to expand...
Click to collapse
Thanks very much for all of your advice and suggestions! I'm back up and running. The gapps package was causing an error 70 message. Once I found a smaller file it worked. It certainly was an excellent learning experience. Thank you again.