Develop Bugs

[Q][Solved] Google Apps on cm10

Hey,
I've read all the guides and they all kind'a passed through my problem without mentioning it..
I suppose it's a driver issue, but I'll try asking anyway:
I'm on cm10 (as of tonight), upgraded from cm7.
I installed TWRP 6 mo ago though KFU, but now I can't get it to work.
(it says "offline").
I tried connecting with 2 PCs and no luck (reinstalled drivers, restarted and rebooted several times).
Is there another way to install google apps? installing them one by one doesn't work ("App not installed").
and is there another way to update TWRP and FFF from within the KF, as opposed to by PC (not recognising KF)
i want to install my google account and get the KF to work normally with Gapps.
*yeah, I'm a noob.
some details:
I have the java dk and android sdk installed, downloaded the last JB Gapps.
adb shell (ie) gives me "error: device not found"
I have samsung gs2 i9100 that i use on the same PC
i can mount sd card using TWRP and cm10 with no difficulty.

You can transfer the files to your Kindle via AirDroid or directly download the file to the Kindle.
Boot into TWrP and install the Gapps and TWRP updates just like you installed the ROM.

veeman said:
You can transfer the files to your Kindle via AirDroid or directly download the file to the Kindle.
Boot into TWrP and install the Gapps and TWRP updates just like you installed the ROM.
Click to expand...
Click to collapse
flash the .img file of the TWRP? it didn't show it as flashable last time i tried.
didn't try flashing the Gapps. will try that, Thanks!

RYuval said:
flash the .img file of the TWRP? it didn't show it as flashable last time i tried.
didn't try flashing the Gapps. will try that, Thanks!
Click to expand...
Click to collapse
Or you can use smirkit to update fff and twrp. I'm not 100% sure that it will work on cm10 but you can give it a shot.

this can help you, when i have my kindle the first couple of weeks i did everything
with youtube learn about root,install twrp flash roms install android market
all with this boy from youtube
and for now i'm on cm10 jelly bean rom twa_priv.
i give you a link and you can follow him with everything.like i did.
http://www.youtube.com/watch?annota...&feature=iv&src_vid=D5FS2a5rmqk&v=rTkegVrnAvA

veeman said:
Or you can use smirkit to update fff and twrp. I'm not 100% sure that it will work on cm10 but you can give it a shot.
Click to expand...
Click to collapse
Thank you again!
details for anyone who has the same problem:
I had root, FFF and TWRP from previous installation, but older versions (twrp 2.0, FFF not sure), used cm7.
couldn't install Gapps on cm10, had no access via PC (prob. driver issue. gave me trouble - KFU and adb command didn't recognize device)
what I've done:
1. entered TWRP through recovery and flashed google apps in their original zip.
2. downloaded busybox & goomanager (Terminal emulator was already preinstalled in cm10)
3. opened each app to enable superuser [su] and install busybox
4. from goomanager, downloaded: browse all files -> devs -> smirkis -> otter -> smirkit -> smirkit v1.4 installer (most recent)
5. tried flashing it through terminal emulator ("su", enter, "smirkit", enter). su worked, smirkit didn't find the file.
6. rebooted to recovery (twrp 2.0), installed/flashed smirkit from there (the zip file was inside goomanager folder)
7. rebooted to cm10, opened terminal emulator, wrote "su", enter, "smirkit", enter and it worked.
8. installed TWRP 2.2.0 and FFF 1.4.
9. performed backup when everything was working.
EDIT:
managed to get it to work with PC commands. disabled and then enabled usb debugging & reinstalling drivers made it work this time. drivers are so random.
Thank you so much for your help. now I can use my kindle again with Gapps and updated recoveries.

Device bricked? No adb-access

Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco

Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there

Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!

That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.

Desperate cry for help

The title might sound a bit extreme but hear me out. Earlier I was updating Havoc-OS to the latest June 12th, 2019 build. Upon flashing it within the TWRP recovery it asked to update the firmware. The firmware that it required was V10.3.1.0.PEIMIXM. I flashed fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0 from the website where all of the firmwares are managed, but ever since I did this my recovery has then broken itself (ARB as well? Give me a second..). Every time I go into TWRP and want to transfer files, there is no way for me to transfer files from my phone to the computer and vice versa. MTP is enabled but I just cannot transfer files what so ever. I tried to reflash TWRP, update to the latest version and it still has not worked. One thing I have noticed while flashing TWRP within Fastboot was that it didn't require me to use the dummy.img in order to flash via fastboot which I thought was strange, knowing that my phone has ARB Level: 4. I have since then used Mi Flash tool to get the phone working again but every time I try to flash TWRP, MTP still will not enable and I have no idea what to do. I'm so scared as to what to do next because I don't know what to do. Please any help or suggestions?

BlackHawk580 said:
The title might sound a bit extreme but hear me out. Earlier I was updating Havoc-OS to the latest June 12th, 2019 build. Upon flashing it within the TWRP recovery it asked to update the firmware. The firmware that it required was V10.3.1.0.PEIMIXM. I flashed fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0 from the website where all of the firmwares are managed, but ever since I did this my recovery has then broken itself (ARB as well? Give me a second..). Every time I go into TWRP and want to transfer files, there is no way for me to transfer files from my phone to the computer and vice versa. MTP is enabled but I just cannot transfer files what so ever. I tried to reflash TWRP, update to the latest version and it still has not worked. One thing I have noticed while flashing TWRP within Fastboot was that it didn't require me to use the dummy.img in order to flash via fastboot which I thought was strange, knowing that my phone has ARB Level: 4. I have since then used Mi Flash tool to get the phone working again but every time I try to flash TWRP, MTP still will not enable and I have no idea what to do. I'm so scared as to what to do next because I don't know what to do. Please any help or suggestions?
Click to expand...
Click to collapse
Go to developer options, disable USB debugging and then enable it again connected to pc and wait that a pop-up appears on device screen, tap on always allow, then within adb/fastboot folder try to send device to recovery with "adb reboot recovery" see if was solved, if not then try erasing recovery partition through fastboot with "fastboot erase recovery" then flash TWRP again as usually, disconnect from pc before to boot to it, then in TWRP connect to pc and wait that pc recognice it.
If the issue persists you can uninstall and delete all the files related with drivers on pc directories and then make again a clean install also wiping cache/dalvik onto your device.

It's because u used the twrp meant for oreo firmware. It is incompatibile with new pie fw, you must flash latest twrp for example twrp 3.3.1 using fastboot. Use adb commands: 1.adb,2.adb shell,3.adb fastboot boot (location of the twrp 3.3.1) for example C:\twrp.... .img and then from the recovery flash twrp 3.3.1 as recovery.

i had same problem.
i installed latest global stable miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0 rom from sd card.
MTP is working properly.
but there is problem for me after that.
This is strange problem.
after installing miui rom twrp recovery uninstalls automatically after reboot,when install twrp via boot it encrypts twrp.
can anyone help me?
my problem is-
after all this if i try to install custom rom(from sd card) it says corrupt file or error 7 ,i tried to flash 3-4 different rom.
EDIT: my problem solved after installing this twrp https://androidfilehost.com/?fid=6006931924117884758 (from AOSP ext pie rom thread)

Flashing custom ROM assistance

Hi I've been away from the aftermarket ROM game for a while and I'm having a bit of trouble installing. Can anyone link to some instructions. All i could find was the ones posted by the Lineage Team but i am unsure if they are universal instructions or if they are only for Lineage. Some assistance would be great!
So details of what I've tried thus far:
Flashing from recovery (i assume this method is pretty much legacy at this point) -
reboot to recovery
factory reset
flash rom
While attempting this method I was unable to find a way to get the ROM zip on my device in an accessible fashion do to encryption, adb push never completeing, unable to mount external storage, and MTP not allowing me access to internal storage. (this is all with TWRP version 3.6 and 3.5 (the two newest as of this post))
ADB sideload -
Booted into TWRP and started the sideload channel
ran adb sideload <zip file>
this just sits and never progresses
I am using the adb and fastboot versions listed below:
ADB - 31.0.3
Fastboot - 31.0.3
I am also running Linux, I have tried using USB 2.0 as well as 3.0 (both had the same results). I have tried different cables (also same results).
Please let me know if any more information is needed to figure this out.
Thanks.

Some roms are designed to flash from fastboot, others from recovery.
Also, TWRP's failure to decrypt should only apply to Android 12 roms - but for those you'll need to format data (after a backup of course).
So tell us which rom you want to flash. Also see the rom's thread - generally, other users will have faced the same problems.

runekock said:
Some roms are designed to flash from fastboot, others from recovery.
Also, TWRP's failure to decrypt should only apply to Android 12 roms - but for those you'll need to format data (after a backup of course).
So tell us which rom you want to flash. Also see the rom's thread - generally, other users will have faced the same problems.
Click to expand...
Click to collapse
Sorry for the late reply, at the time I had just went back to the OS is was already running simply because they have a script to handle install. Though Right now I really want to at least go back to LineageOS, CalyxOS (the ROM on running now) is just too restrictive.
I know I've had issues installing LineageOS before and at that time I found away around it to get it installed but I don't remember what I did...
So this is what happens I When following the instructions here I always run into issues gaining access to the zip file in recovery/sideloading via ADB. I think last time I installed it I was able to boot to Lineag Recovery and sideload from there but sideloading in TWRP doesn't seem to work for me. and If I try to access the zip from TWRP (to flash in recovery) it's never there or errors out.
I think im going to try again today and will post any errors.

So i just remembered I can adb push and access an external drive while in slot_b but not slot_a.
Edit: NVM cant adb push on either slot in TWRP

So I just installed Lineage Recovery but sideloading doesnt progress at all just sits at verifying signature. I'll post in the lineage thread and post back here if I figure it out.

ok figured it out. Had to place the zip on an external drive, make sure my phone was in Slot A, boot TWRP, mount the external drive and flash from there, I got a few errors saying it couldn't mount /Vendor but it seems to work

deathblade said:
ran adb sideload <zip file>
this just sits and never progresses
Click to expand...
Click to collapse
Try connecting the phone through a USB hub. I had the same issue and this was how I resolved it.

LG F400S/K Kitkat unable to install TWRP recovery / unable to install Gapps (solved)

Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.