So, I tried installing open GApps (pico) for Resurrection remix ROM. Sadly, I got Error 70. I tried wiping /system and flashing gapps again, with no avail. I searched the internet for quite a while.
Please help.
I am also having this problem. Does anyone knows a fix? I only found for I9100, so I didn't try because it's different files from I9070.
Thanks!
Your phone has 600Mb system partition, unpack ROM and check how big is folder named "system", than you can unpack Gapps and compare how much space is needed.
After switching system to f2fs, you have even low left space!
agrastiOs said:
So, I tried installing open GApps (pico) for Resurrection remix ROM. Sadly, I got Error 70. I tried wiping /system and flashing gapps again, with no avail. I searched the internet for quite a while.
Please help.
Click to expand...
Click to collapse
Dont worry..
The best solution for this is :-
1) Go to settings
2) click on configruations
3) then go to updates
4) then download the gapps
5) flash it with a customrecovey....
Even i am using the same Rom now[emoji14].
Sent from my GT-I9070 using XDA-Developers mobile app
Hello, I just installed CM13 and it works perfectly fine. I did a backup, downloaded GApps from here with the selection of Platform ARM, Android 6.0, and I've tried two different Variants both mini and micro (I don't have enough space for full). Every time I install GApps through TWRP (latest version for titan 2.8.6.0) and once I reboot it keeps spamming "Unforunately Setup Wizard has stopping working" and "Google Play Services has stopped working" and I cannot do anything. I have to boot into recovery and do a restore before GApps. Why is this?
I think you are Installing Gapps After booting in CM13 and then going back to recovery to flash gapps.....
Just flash Gapps along with ROM and do A dalvik and cache wipe after....
Varun hellboy said:
I think you are Installing Gapps After booting in CM13 and then going back to recovery to flash gapps.....
Just flash Gapps along with ROM and do A dalvik and cache wipe after....
Click to expand...
Click to collapse
Wait, I need to flash Gapps and also my ROM? I've been just installing by clicking "Install" and hitting the zip and then booting. What's the command to flash them in adb?
First Wipe your Dalvik,Cache,system,data....
then goto install and select the ROM zip...
after flashing goto mount and Mount everything....
then goto install again and select The Gapps Zip....
wipe Dalvik and cache and reboot....
Recently got a kindle fire 7" and wanted to root it and flash a rom onto it, but having troubles with that part.
Using this guide https://forum.xda-developers.com/amazon-fire/general/root-t3471289
Rom:
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
Usb debugging/install from unknown sources/kingroot done
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Tried with and without mounting
Crashes after and starts a boot loop going into the amazon logo only
I'm new in regards for rooting, sorry if I'm a bit slow with this.
Thanks in advance for the help!
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Mr McBoatface said:
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
Still nothing, leads me into another boot loop.
New things:
Rebooted after installing flash fire
Verified the hash
Move the rom onto the internal drive (flashed from there)
No Automount
Any other ideas?
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Shugumi said:
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Click to expand...
Click to collapse
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
ggow said:
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
crazyates said:
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
Click to expand...
Click to collapse
Had the zip on storage and wiped before flash, nothing :/
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Mr McBoatface said:
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Click to expand...
Click to collapse
I might disagree with a few things you said there...
You only have to remove KingRoot if you're using v5.0 or newer. If you can use 4.9.6 to root, which I believe is what the SuperTool uses, then you can download SuperSu from the play store, update SU binary, then uninstall KingRoot with no issues.
As far as FF is concerned, the ROM developer says 0.55.1 is required, so I wouldn't stray from that.
The only other thing I would recommend is using the not-newest version of the ROM. For the last 6 months, the ROM has been based on a 5.3.2 boot.img, and recently switched to a 5.1.4 boot.img. Maybe the newer firmwares don't like the downgrade? I would try the Feb-2-2017 version of the ROM and try again.
Steps:
Restore to stock 5.3.2 (NOT 5.3.2.1)
SuperTool to install KingRoot 4.9.6 & GPlay
Kingroot to root
Install SuerSU (newest) & FF (newest) from Gplay
Use SuperSu to update SU binary
Put Feb-2-2017 zip on SD card
Use FF to wipe System, Data, Cache, Dalvik, 3rd party apps, & then install zip from SD.
Let sit for 5-10 minutes & do it's thing.
Having 2 root managers is not a good idea.
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
The version of flashfire shouldn't matter, but he is having issue so best to rule it out. The behavior of 0.53 is different to 0.55.1 . it flashes a lot quicker and is fine to use. I've used it several times in the last fortnight with the latest ROM.
The current ROM is fine, boot image and binary change won't cause the issue experienced here. The older ROMs are broken , in so far as either the camera or screen cast won't work. The latest ROM with the proven and stable binary is a better option, everything works
EDIT , also there are reports of several users losing supersuser seemingly random after upgrading to the latest SuperSU , hence why I suggested sticking with the current one on supertools.
I also suggested wiping cache, just incase an amazon update has downloaded while rooting and attempts to install at the same time at the nexus ROM is being flashed.
I have a Fire running Nexus Fire ROM (2/8/17), and my fiance has a Fire running stock 5.1.2 with root, OTA updates disabled, Nova Launcher, and Gplay Store. I wanted to flash hers from Stock to Fire Nexus, and ran into the same issues I had before.
FF was supposed to Wipe System Data, 3rd party apps, Dalvik, and Cache, then install zip, then inject SuperSU. When it did the wipe, it deleted the ZIP on the Internal Store, so FF sat there for 15 minutes not doing anything, and I didn't have a system to reboot into anymore.
I had to do a sideload recovery of 5.1.2, root, install FF, and do all the same steps as above, but this time install the zip from an SD card. Worked great.
Mr McBoatface said:
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
Click to expand...
Click to collapse
I used the SuperTool to root, and this is what I did also. Afterwards, I used the Gplay to update the SuperSU, which updated to the newest binary. I haven't seen any problems as of yet.
Unless internal storage was selected that shouldn't have happened, unfortunate that it did for you. The only time I've seen FF hang was when wipe was in the wrong order or when the USB cable was connected..... Don't know why the USB cable has that effect but I've seen it on 2 devices, other people have not had any problems.
Not seen the issue with SuperSU myself but read plenty of reports about it.
It seems users are affected by several random issues even if following the same instructions.
@Shugumi any update ?
Been swapping out roms and trying each suggestion but its been giving me the same boot loop.
So, I returned the kindle fire, and am waiting to try it on the new coming device :/, but thanks to everybody that replied to this thread. Even though we didn't get to root my kindle, it was great help! Thanks everybody.
So i recently decided to try out some of the different roms that were released for the moto e4. I decided to go back to Resurrection Remix, and when i tried to install the modules I had been using, found that some of them weren't working properly. There are no errors when they install, but seem to have no effect, such as the volume step increase, or the injected youtube background player...
other modules, like the app systemizer seem to be working just fine...
HigherStateD said:
So i recently decided to try out some of the different roms that were released for the moto e4. I decided to go back to Resurrection Remix, and when i tried to install the modules I had been using, found that some of them weren't working properly. There are no errors when they install, but seem to have no effect, such as the volume step increase, or the injected youtube background player...
other modules, like the app systemizer seem to be working just fine...
Click to expand...
Click to collapse
Did you do a clean install? (Completely wipe data and not restore it again in twrp). Some ROMs have trouble with some modules. Get logs and ask in the modules threads (the ones not working).
Clean install, full wipe, same as before, modules worked fine last install on the same rom, restore failed to boot, which is why I needed to reinstall the previously working modules
HigherStateD said:
Clean install, full wipe, same as before, modules worked fine last install on the same rom, restore failed to boot, which is why I needed to reinstall the previously working modules
Click to expand...
Click to collapse
I had a similar-ish problem on Moto g4 plus RRO.... If you still can't get it to work, here's what I did:
Rom, gapps, boot (usual steps)
Download Magisk APK from XDA
Give it storage permissions
From Magisk Manager, select install
It should ask of you want to direct patch (recommended)- select this option
Reboot and try modules again
I think it's something to do with storage permissions etc. When Magisk tries to patch boot IMG. Check your file systems too. Data partition should be fsfs and all others ext4.
If the steps above don't work try the fsfs Magisk loopback module. It's in the repo and mentions some of the Moto devices having issues with with patching boot img etc for Magisk. The module is installed via TWRP.
:good:
Got it working, somewhat similar process, ROM, gapps, MM apk, then uninstalled the magisk that came built into the ROM, and used the manager installer... Then encrypted, and then opt-enceypt... A script in sbin for my fingerprint from the original ROM and got safetynet passing.
So I have followed the usual way of installing LineageOS 17.1 and OpenGApps Pico for my phone. However, I don't see any Google Apps on my system...
I don't have ANY errors when installing them or anywhere else. Anybody know what the problem could be?
Shmotten said:
So I have followed the usual way of installing LineageOS 17.1 and OpenGApps Pico for my phone. However, I don't see any Google Apps on my system...
I don't have ANY errors when installing them or anywhere else. Anybody know what the problem could be?
Click to expand...
Click to collapse
This happened to me and drove me insane. When you install LOS with TWRP it mounts a bunch of folders, GAPPS won't visibly fail, but it won't be able to remount the folders and make the directories and files it needs and then out get nothing.
In TWRP go to Mount and switch to internal storage, uncheck system, and data then load GAPPS, assuming you have that on external..
Secondly after you install GAPPS you may run into an awesome crash loop once you start up where Trebuchet crashes repeatedly. If so, when you get the crash notification don't close it, just open the status bar and go into options, go into apps and find the Pixel launcher, make that the default.
This may help you as well as others. I was having this problem both with crDroid and LOS.
When I was installing the OS through TWRP, I installed the OS, then Magisk, and THEN gapps. This was the only way to have them stable in the launcher and actually show up.
I'm not sure as to why this happened and maybe it has to do with the mounting and unmounting of partitions done by Magisk that sets up gapps but I can only guess.
CrMeister said:
This may help you as well as others. I was having this problem both with crDroid and LOS.
When I was installing the OS through TWRP, I installed the OS, then Magisk, and THEN gapps. This was the only way to have them stable in the launcher and actually show up.
I'm not sure as to why this happened and maybe it has to do with the mounting and unmounting of partitions done by Magisk that sets up gapps but I can only guess.
Click to expand...
Click to collapse
Thanks so ****ing much!!!! Trying to help my brother with his phone and i ****ed up the system partition and recovery trying to install gapps.... ffs ;
Finally recovered it manually flashing the boot partition and the recovery and system stock partition, then boot again into twrp and did the steps to install LOS 17.1 then followed Magisk & Gapps and it worked.
Thanks again!!!