Develop Bugs

[HOWTO] ClockworkMod Recovery & TWRP - Upgrade/Downgrade (Touch/Non-Touch Recovery)

[HOWTO] ClockworkMod Recovery & TWRP - Upgrade/Downgrade (Touch/Non-Touch Recovery)
IF YOU TRASH YOUR PHONE USING THIS PROCEDURE, THEN IT IS A VERY GOOD INDICATION YOU ARE AN IDIOT AND SHOULD NOT BE FLASHING ANY ROMS NOR PARTICIPATING ON THESE FORUMS. . . . JUST SAYIN'. . . .
Please be VERY careful when using this method as you can brick your phone. Make sure you triple check the file you downloaded is the right size and placed in the right area, but most importantly that the command lines you type are exactly right. If you are not comfortable using this method, then please do not and go find a flashable version of these recoveries.
I've posted a procedure to format/'flash' your recovery while on your phone in one of the threads on here and was asked by a Forum Mod to make a quickie guide to be placed as a sticky on the dev boards so others might benefit.
Anyway, here is a very quick and easy way to change your ClockworkMod recovery with a couple of command lines.
The TWRP link is in the second post.
Now for the ClockworkMod Instructions:
1. First, go here and look up your ClockworkMod recovery that pertains to your phone: http://www.clockworkmod.com/rommanager
2. Download the .img file for your phone and save it on your computer.
3. Rename the .img file to recovery.img and save it to your internal sd card of your phone. For example: recovery-clockwork-6.0.1.4-hercules.img ------> recovery.img
4. Open up Terminal Emulator on your phone and type the following 2 commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
(please note the second command is a one line command with spaces between "dd & if=" and ".img & of=")
If your Rom identifies your internal sdcard as /emmc instead of /sdcard, then make the adjustment to command line (dd if=/emmc/recovery.img) instead of what is posted above.
That simple.
You can also issue these commands from adb shell if you are connected to your computer.
If Terminal Emulator does not have Superuser or SuperSU permissions for root privileges then make sure it does. You can also go from NON Touch CWM to Touch CWM using this and vice versa. Simply make sure you have the right recovery for your phone and rename it to recovery.img.
As for explanations:
dd if= command is a common Unix program whose primary purpose is the low-level copying and conversion of raw data.
dd stands for "data description"
if stands for "input file"
of stands for "output file"
the = is the location of the data you are using. ie. /sdcard/recovery.img
the /dev/block/mmcblk0p22 is the location/partition of the recovery on your phone.
So essentially you are doing a low level rewrite of the recovery image on your phone via command lines.
***Also, the best way to remember this command line is to not to. Copy the command line and save it to your own personal contact info in Google under Notes and then you will have it with you wherever you go. You really do not want to mess with getting it wrong. You could brick your phone if you mess things up.
Anyway, I hope this helps. . . . it really is very easy to execute without fault.

Works with TWRP too.
This also works with changing to and from TWRP. Download the image (for our phones it's TWRP 2.3.1.1) rename it to recovery.img and follow the above instructions and you are good to go.
Follow this link to get the image file: http://teamw.in/project/twrp2/101
***I attached the old TWRP 2.2.2.0 is case you run into problems with the newer versions not restoring backups properly or renaming backups correctly.***

Excellent Thread, I hope Dev's requiring specific CWM versions can link to your post.
Thanks for your efforts.
Noellenchris
XDA Forum MOD

Thanks for the instructions! Thanks even more for explaining the command lines.

Just thought I'd point out a small bug with the Touch Recovery. If you flash one of the newer ICS roms like Darkside Evolution through the Touch Recovery, once booted, the ROM WILL NOT SLEEP through time out. I've confirmed this with 2 separate ICS roms. Flashing non-touch recovery through Rom Manager fixes this problem.

Wouldn't it be easier to use gscript and run the commands as you need them?
Thanks for the HOW TO I actually was looking for it.

What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.

dextroamphetamine said:
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
Click to expand...
Click to collapse
For some people Rom Manager doesn't work. On the T-Mobile SGH-T989 Galaxy SII, Rom Manager will only allow you to go to 5.0.2.6 not 5.0.2.7. And, I think you have to upgrade Rom Manager to go to Touch. I bought Rom Manager, and don't use Touch Recovery, so I am not sure.
I like to use the command structure verses program because I know it works, it's fast, and I can see the results if an error occurs.

Oh yeah...this was really simple...Thanks...went from Touch back to Non Touch.

Give this a try
If you want a simple way to flash the Touch Recovery then give this a try. I will be adding the Hard Recovery as well in the next release.
SGSII T989 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1650908

http://forum.xda-developers.com/showthread.php?p=26200755

I get a write error: No space left on device. 1001+0 records in 1000+0 records out 512000 bytes transferred in 0.132 secs.
I reboot into recovery and it's still on 5.0.2.6
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.

albanianbrotha said:
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
Click to expand...
Click to collapse
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.

hobakill said:
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
Click to expand...
Click to collapse
Haha no worries bro. I mean worries that it failed for no reason, but I already sent it in, he just got it today. Same person you linked. Definitely trying to install ics again when i get it. Plus I think the ota ics for tmo came out yesterday or something? Probably a better experience than what was already out there with the radio and stuff.

the files from the CWM site are not .img for me, they are .ndif is it the same procedure?

MustangFTW said:
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
Click to expand...
Click to collapse
No! Do NOT use this procedure with that file extension!
What recovery are you trying to install? And for what phone? I briefly ran my cursor over the various files and the download links are either .img or .zip files. I did not see .ndif file extension.
PM me if you need additional help.

Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!

fresherthanU said:
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
Click to expand...
Click to collapse
You're welcome, I'm glad I could help you. But, the link to the .img files is in the OP instructions. . . .

Unfortunately this method did not work for me... I have tried many ways to update my CWM and none of them worked, it is almost hopeless for me

Good news! You made front page! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)

[RECOVERY] ClockworkMod Recovery 6.0.3.2

ClockworkMod Recovery Version 6.0.3.2 is now available officially for your T-Mobile Samsung Galaxy S 4. You can install ClockworkMod Recovery on your rooted T-Mobile Samsung Galaxy S 4 by installing ROM Manager. ROM Manager is available on the Google Play Store at:
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Alternatively you can download the ROM Manager APK directly from ClockworkMod.com at:
http://download.clockworkmod.com/recoveries/RomManager.apk
Once installed use the "Recovery Setup" section to install or update your recovery installation.
You can also install the latest version of ClockworkMod Recovery manually. The images for both the touch and non-touch version are available directly at:
http://www.clockworkmod.com/rommanager
Simply locate your device (T-Mobile Samsung Galaxy S 4) and download the linked image to the right. You can than flash it manually or with any tool designed to manually flash recovery images.
CHANGES-
Version 6.0.3.2 - Initial version listed here

We are picking up. Nice

How do I install a .IMG file (the CWM recovery download file) onto the S4? There is no FASTBOOT mode (or I can't access it for some reason).
Yes, I know I can use rom manager to install CWM, but that isn't my question.

I can confirm - it does work.
Thanks for the quick posting of this!

Oh boy! i'm getting my S4 sooner then i thought now lol. Monday? i sure hope so if not i'll have to wait til the weekend i think but oh man, CM10.1 here we come

Nice recovery I downloaded rom manager and installed the touch recovery and it's very good but the only problem is that the space between the text is really close to each other I mean you have a really big screen and it only uses less than a third u know what I mean? Just saying so far I like it but that's the only thing I find annoying
Sent from a phone better than yours!

lagunas11 said:
Nice recovery I downloaded rom manager and installed the touch recovery and it's very good but the only problem is that the space between the text is really close to each other I mean you have a really big screen and it only uses less than a third u know what I mean? Just saying so far I like it but that's the only thing I find annoying
Sent from a phone better than yours!
Click to expand...
Click to collapse
Exactly the problem I am having. I am wondering if R.M. is installing the proper version of touch. It's almost impossible to use. It also doesn't support gestures which makes it more difficult.

gweedo767 said:
ClockworkMod Recovery Version 6.0.3.2 is now available officially for your T-Mobile Samsung Galaxy S 4. You can install ClockworkMod Recovery on your rooted T-Mobile Samsung Galaxy S 4 by installing ROM Manager. ROM Manager is available on the Google Play Store at:
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Alternatively you can download the ROM Manager APK directly from ClockworkMod.com at:
http://download.clockworkmod.com/recoveries/RomManager.apk
Once installed use the "Recovery Setup" section to install or update your recovery installation.
You can also install the latest version of ClockworkMod Recovery manually. The images for both the touch and non-touch version are available directly at:
http://www.clockworkmod.com/rommanager
Simply locate your device (T-Mobile Samsung Galaxy S 4) and download the linked image to the right. You can than flash it manually or with any tool designed to manually flash recovery images.
CHANGES-
Version 6.0.3.2 - Initial version listed here
Click to expand...
Click to collapse
-1 i would prefer if you didnt submit this
not enough rainbows

Does anyone have instructions how to install the IMG. Via terminal emulator?

jbats said:
Does anyone have instructions how to install the IMG. Via terminal emulator?
Click to expand...
Click to collapse
Use Odin dude its way easier to install.. It takes less than 15 seconds to do it
Sent from a phone better than yours!

How do u flash IMG. In Odin? All I need to know is where the IMG. Goes in /system ?? That way you can manually install any IMG. Via terminal. @shabbypenguin any ideas? Your a wiz with this stuff :good:

jbats said:
How do u flash IMG. In Odin? All I need to know is where the IMG. Goes in /system ?? That way you can manually install any IMG. Via terminal. @shabbypenguin any ideas? Your a wiz with this stuff :good:
Click to expand...
Click to collapse
if you use adb sehll then be sure to follow these commands as well:
adb shell
su
then once in a rooted shell (or terminal emulator) be sure you know the exact location and name of clockworkmod recovery.img
dd if=/sdcard/cwmrecovery.img of=/dev/block/platform/msm.sdcc.1/by-name/recovery
replace the bold part with the name of the file
replace teh underlined with where it is located

Thx shabby, I'll use this when mine arrives on Monday. Might be a good idea to create a thread with these how to's. Love your work, used your methods when I got my t769.

Works like a charm! now waiting for some good ROMs im tired of this crappy STOCK boring Rom!

shabbypenguin said:
if you use adb sehll then be sure to follow these commands as well:
adb shell
su
then once in a rooted shell (or terminal emulator) be sure you know the exact location and name of clockworkmod recovery.img
dd if=/sdcard/cwmrecovery.img of=/dev/block/platform/msm.sdcc.1/by-name/recovery
replace the bold part with the name of the file
replace teh underlined with where it is located
Click to expand...
Click to collapse
I'm running this with files and locations set exactly as in your example and getting "no such directory or file." Must be missing something obvious.

hmmm try on external sd and change the path to match that then?

How do you switch between TWRP and CWM? The WICKED ROM requires TWRP, but I've always used CWM... I'd like to be able to switch without much trouble if needed.

shabbypenguin said:
hmmm try on external sd and change the path to match that then?
Click to expand...
Click to collapse
Tried that as well with same result. Triple checked path and spelling & case (if case even matters). Can you double check your command line and make sure there is no typo? Thanks

MisterEdF said:
Tried that as well with same result. Triple checked path and spelling & case (if case even matters).
Click to expand...
Click to collapse
it does
try teh direct mmcblk then
dd if=/sdcard/cwmrecovery.img of=/dev/block/mmcblk0p21
and see if that works for ya, before you try using the command "ls -l /path/to/cwmrecovery.img" without the quotes and make sure teh phone sees it

shabbypenguin said:
it does
try teh direct mmcblk then
dd if=/sdcard/cwmrecovery.img of=/dev/block/mmcblk0p21
and see if that works for ya, before you try using the command "ls -l /path/to/cwmrecovery.img" without the quotes and make sure teh phone sees it
Click to expand...
Click to collapse
Turns out the path to the extSdCard is actually /storage/extSdCard. Couldn't see the directory of the sdcard noway nohow. Can't figure out why. /storage/extSdCard worked.
Thanks.

Easiest way to root HTC Evo Desing 4G

Okay, ive been doing my research, and I lasted aprox. 4-5 days and its sadly to know but this phone (HTC Evo Design 4G / Kingdom / Hero S) doesnt have that much of fame. But I was crazy trying and trying alot of methods trying to root my phone, but just couldnt. I was about to give up, until I found a Guide, and made it possible for me to root the phone, so I decided to share this guide to you guys, to who ever has a HTC Evo Design 4G / Kingdom / Hero S. Credits go to LOLINTERNET who wrote this guide. :good:
Ok, here we go. :laugh:
In order to root your Evo Design you'll need to unlock your bootloader, flash recovery, flash su binary, and install superuser and busybox. In this guide I will try to explain these steps as simply as I can. My goal is for it to be thorough enough that anyone that reads it can root their phone and enjoy the full benefits of this nifty little phone.
First and foremost, you will need to install the Java SE Development Kit. You won't use this directly in any way, but you need it in order to install the Android SDK.
Click Here To Download SDK
After installing the Java JDK, you will have to install the Android SDK which contains two tools that are essential to gaining root. They are adb (Android Debug Bridge) and fastboot. These tools are used to send files to your phone from a Windows command prompt. You will need these tools to unlock your bootloader and flash recovery.
Click Here to Download Android SDK
Instructions on installing the SDK
How to add packages to the SDK
Once you have the Java JDK and the Android SDK installed you will need to install the proper drivers for your phone. This one is pretty straightforward and necessary for your phone to be recognized while plugged into your computer. After you have the HTC drivers installed you can begin the fun parts, but first you will need a few things. :good:
HTC Drivers CREDITS TO: CNexus
You will need a recovery.img. 2fast4u88's unofficial ClockWorkMod Recovery version 5.0.2.7 and 5.0.2.8 are the only two recoveries I have used since I got my Evo Design. Many thanks to him for putting in so much work to get this device where it is today.
Download Recovery
Also, you'll need su binary version 3.0.3.2 efghi. This is the actual file that will root your device. It is a flashable .zip file that you save to your sdcard and flash in recovery. You'll be amazed at how easy this step is.
Download for su binary version 3.0.3.2 efghi
Download for su binary version 3.0.7 efghi
3.0.3.2 binary is for Gingerbread and 3.0.7 is for ICS
The superuser app is like the control center for apps that request root permissions after you're finally rooted. You will need to install this app and then Busybox, both of which can be found in the Google Play Store. After installing the Busybox app you will need to actually install busybox. The app itself is basically an installer for Linux applets that are required by root apps such as Titanium Backup and Root Explorer among many others.
Now that you have a basic overview of what it is you will be doing and the files need to do it, the only thing left is to actually perform these steps and root your device. So, lets do this!
1. Unlock your bootloader at htcdev.com. You will need to sign up and you will be warned that unlocking your bootloader will void your warranty. Once you've followed all instructions at the website an unlock token will be emailed to you. DO NOT DELETE THIS FILE. You can place it in the platform tools folder of the Android SDK and use fastboot in command prompt to relock and unlock your bootloader whenever you like. Also, anytime you unlock your bootloader all data will be wiped so be sure you sync all your contacts and backup other information first before performing this step.
2. After unlocking your bootloader you will need to flash a recovery.img. The manual way to flash recovery is to place the downloaded recovery.img for 2fast4u88's unofficial ClockWorkMod recovery port of version 5.0.2.7 in the platform-tools folder of the Android SDK. Power down your phone but be sure that Fast Boot in Power under the settings menu is unchecked or it will just reboot normally instead of into bootloader (also called hboot) like you want. After it's been powered down for a minute or two, press and hold Volume down then press and hold the power button. When the white HTC splash screen appears you can let go. Scroll down with the volume down button and select fastboot by pressing power. Plug your phone into your computer and open a command prompt, then run these commands without quotations.
"cd C:\android\platform-tools" (This is where adb and fastboot live. It may be different for you depending on where you installed the SDK. I always suggest installing it to the root of your C: drive.)
"fastboot flash recovery recovery.img"
Should only take a few seconds, then you have yourself a recovery partition and you can proceed to the next step after rebooting. Yay!
3. Next, we're going to flash the su binary in recovery. First, you'll need to place it on your sdcard. Doesn't matter where exactly just as long as you can find it. I would suggest the root of your sd just to make things easier on yourself. After you have the su binary zip saved to your sdcard power off your phone and boot into hboot. Now, I can't remember which, but either hboot or fastboot will have an option to boot into Recovery. Once you're booted into recovery, select "install zip from sdcard," then "choose zip from sdcard." Scroll down and find the su binary then select it. Pressing the Up Vol button will take you directly to the end if you don't want to scroll all the way through. After selecting the su binary zip select "yes" to flash. It's a small file, so it won't take long. When it's done select "reboot to system" and we'll move on to the next step because you just rooted your phone.
4. But, you're not done yet. You need to install the superuser app and the busybox app in that order. This is the easy part because both apps are free in the Play Store. Install Superuser, then Busybox. You shouldn't have to interact with the Superuser app, but if you want to set an automatic response to apps that request root you can open it and go to Preferences. Scroll down and you should see a few options. I have mine set to automatically grant su permission to apps that request it because I have no reason not to lol. I also unchecked the option to receive a notification every time an app is granted root permission because that junk just gets annoying. Next, after you install the Busybox app, you'll need to actually install Busybox. The app is merely an installer for the actual Busybox applets that govern root apps. The app should open automatically after you install it. You should see it in your notification bar. Open it up and follow the prompts. When you're done, reboot your phone.
5. Check If you have rooted your phone successfully, download Root Checker on Play Store.
6. Congratulations! You should now have a rooted Evo Design 4G. Enjoy. I hope this guide is both complete and comprehensive enough that everyone can enjoy the benefits of having a rooted device, but if I've missed something or if you have any questions whatsoever, please post them here and I will do my best to answer them in a timely manner. I hope you enjoy rooting your device, but please be careful. You now have administrator privileges, so use them wisely. I would highly suggest installing Quick Boot from the Play Store so that you can boot into recovery easily without having to go through hboot. I would also suggest using your newly installed app that requires root access to boot into recovery and make a backup. If anything should ever happen to your phone's system and data you will have a backup and can restore it to that state. Again, I hope you enjoy. I apologize for this being such a lengthy guide, but hopefully you understand the wonderful world of Android a little better for having read it. :good:
*EXTRA* 7. I recommend doing a backup via recovery of your phone, because this phone doesnt seem to have any roms or any stock roms etc, so i recommend making a backup, but dont worry, ill try to make a backup ROM so there could be one on the internet, because I searched and could find one! :s

Great post Julio. I saw this post somewhere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.

maikalwolf said:
Great post Juan. I saw this post somewere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
Click to expand...
Click to collapse
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?

re you follow up question
julio626 said:
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
Click to expand...
Click to collapse
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.

maikalwolf said:
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
Click to expand...
Click to collapse
Thanks man!

Gracias Julio
It was quite tedious to be honest. But reading your guide and this one how-to-unlock-the-bootloader-of-any-htc-device en cultofandroid I finally was able to root my phone. Thank you so much!

Amazing
This is the best guide I have ever found. It was fluid and easy to understand for me. Just went from my JB IPhone 5 (cellular happened to break). now i have this phone lol (but its so slow and useless I decided to root and it was an unbelievable pain.. nothing worked). Then I found your guide which is fantastic, completely like no other. I am very impressed with it and just wanted to say THANK YOU!!!!!! :good:

So Close PLEASE can you help.
I followed this guide about a year ago & got to the image you see linked h**p://i.imgur.com/zfle9n7.jpg To be blunt I do not recall where I left off in the rooting process except to say I'm dead ended. Where did my efforts go wrong and what do I need to do in order to finally get this rooted? Also please tell me what bearing info in this thread: h**p://forums.androidcentral.com/htc-evo-design-4g/142434-s-off-s.html may have on my results. THANK YOU

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.

Downloadling applications with custom Rom

So I am pretty new to this, but here goes....
About a month ago I got some help from a friend and downloaded lineage OS 15.1 to my Lenovo p2a42 device. Very happy with everything, until yesterday when the phone began to vibrate and then proceed to shut down with a blue indicator light showing. After some fiddling and attempts to get the latest update of lineage, I got stuck in my first boot loop. After all my various attempts to solve the problem, I decided to do a clean wipe and reinstall lineage. Which I've done successfully I believe, no crashes yet. What I am having trouble with now is remembering how to download the first applications since I don't have the Gsuite or Gapps downloaded. I remember my friend mentioning a problem with the stock file manager for lineage and I believe that is one of the first applications we downloaded along with the apk pure app store.
If anyone can help this newbie figure out how to download the apk mirror to my device without an appstore, I would appreciate it.
>maybe the answer is to download to my laptop first and then use adb to flash it to my device?
Thanks for the help!!

If you want to have Google apps on your phone, search for Open GApps and download for ARM64 devices (nano package is recommended). Then flash it alongside LOS in TWRP. You will have Google Play Store installed.
But, if you only want APKPure store then you must download the APK from their website (either via computer then move it to your phone, or by using default LOS browser). Navigate to your downloaded APK using file manager and open it, you will have a prompt to install it or not. That's pretty much it though.

XDAquareis said:
If you want to have Google apps on your phone, search for Open GApps and download for ARM64 devices (nano package is recommended). Then flash it alongside LOS in TWRP. You will have Google Play Store installed.
But, if you only want APKPure store then you must download the APK from their website (either via computer then move it to your phone, or by using default LOS browser). Navigate to your downloaded APK using file manager and open it, you will have a prompt to install it or not. That's pretty much it though.
Click to expand...
Click to collapse
I downloaded apk pure directly on my mobile from the website (not interested in GApps). It opens in the LOS default file manager and there are basically no options to run it. I think this is because the root may be disabled, my boot loader is unlocked, but it says adb only in my developer options settings. I am new to using adb to flash an apk. I was able to flash lineage, but not sure how to install the apk. For instance, should my phone be on when I enter command install xxx.apk or should it be in recovery mode or boot mode? I tried once already and the apk install failed, not sure what I am doing wrong here. Thanks for the response above.

LineageP2newb said:
I downloaded apk pure directly on my mobile from the website (not interested in GApps). It opens in the LOS default file manager and there are basically no options to run it. I think this is because the root may be disabled, my boot loader is unlocked, but it says adb only in my developer options settings. I am new to using adb to flash an apk. I was able to flash lineage, but not sure how to install the apk. For instance, should my phone be on when I enter command install xxx.apk or should it be in recovery mode or boot mode? I tried once already and the apk install failed, not sure what I am doing wrong here. Thanks for the response above.
Click to expand...
Click to collapse
Answered my own question. Was able to download a file manager using adb, this allowed me download apk mirror.