Help with stock rom ! - Amazon Fire Phone

Hello, So i recently decided to move back to stock os as i think the push notification bug is fixed (Is it ?) . So then i yesterday downloaded the rom http://forum.xda-developers.com/fire-phone/development/safestrap-v4-flashable-stock-image-t3150531. I downloaded the latest version 4.6.6.1 US Version. I remember i rooted the phone from 4.6.6 does it matter ? So i decided to check the rom before actually wiping all my data so i created rom-slot-1 and tried to install the stock os in it. It gave me a error ''Failed to update binary through zip'' i can not decide is it problem with non-stock rom or is it with the rom. There are 3 rom types on that rom page. I dont know what could be the problem. Does the rom vary with the model of the phone ? if yes then how can i know my model of the phone ?
Thanks

The Fire OS partitions are too big, so they will never fit into the manually created slots, which is a good thing because they prevent an installation that would be useless anyway.
You can install ROMs to slot1 but they won't work correctly (connectivity, etc.), so don't even waste time on trying...
Just backup your existing OS via TWRP through Safestrap and proceed with a clean install of Fire OS:
TWRP backup of "old" OS
wipe data, cache & dalvik
flash the CleanSystemPartition zip
flash the Fire OS zip right after
flash other things of your choosing, like SuperSU, etc.

Paras5 said:
Hello, So i recently decided to move back to stock os as i think the push notification bug is fixed (Is it ?) . So then i yesterday downloaded the rom http://forum.xda-developers.com/fire-phone/development/safestrap-v4-flashable-stock-image-t3150531. I downloaded the latest version 4.6.6.1 US Version. I remember i rooted the phone from 4.6.6 does it matter ? So i decided to check the rom before actually wiping all my data so i created rom-slot-1 and tried to install the stock os in it. It gave me a error ''Failed to update binary through zip'' i can not decide is it problem with non-stock rom or is it with the rom. There are 3 rom types on that rom page. I dont know what could be the problem. Does the rom vary with the model of the phone ? if yes then how can i know my model of the phone ?
Thanks
Click to expand...
Click to collapse
And no... The notification push bug isn't fixed -,-

Related

HELP Baseband Unknown and Deleted IMEI

Hello guys I just wanna inform you that there is something happening with the CM 11 4.4+ based ROMS
they deleted my Baseband and IMEI
I restored through KIES and got my Baseband and IMEI back but this thing keeps happening and I cannot figure out why?
It's painful procedure because I did this more then 10 times
First I had to Reflash everything through KIES which makes my phone as DEFAULT
then I had to ROOT and install the ROOTED Original 4.3 then I had to install Clockwork Mod with MOBILE ODIN in order for me to install different ROMS
after that I do FULL WIPE ALWAYS
Cache / Dalvik / Data / System even Internal Storage
I installed CM11 whatever ROM u choose:
http://forum.xda-developers.com/showthread.php?t=2453586 (tried this one no success)
Tried this one:
http://forum.xda-developers.com/showthread.php?t=2565259 again the same thing Bad baseband
Also this one:
http://forum.xda-developers.com/showthread.php?t=2493905 OMNI Rom (first installed older version everything was fine but when It updated to the latest OMNI I got the same Unknown Baseband and no DATA whatsoever)
so what the heck is going on? Please help me?
recovery might be the issue
I just had this problem yesterday. You wouldn't happen to be using TWRP recovery would you? I found that if I was using TWRP and Kit Kat AOKP I would have no service and my APN list would be empty. If I used Philz Custom recovery or CWM it would work fine.
I tried going downloading the newest 2.6.3.1 version of TWRP and it made my phone unable to boot. I had to flash another recovery via Odin in order to get back into my phone.
Just a thought.
I've had this issue as well and for some reason the latest nightlies don't play nice with my phone and recovery I'm using the latest official twrp for t0lte. Not t0ltetmo. I recently tried fishing the last multi window and I lost my microphone use. I have since reverted to a homemade build from January.. It seems to be the only thing that works.
Sent from my SGH-T889
Guys I used both CWM and TWRP both the latest versions... and this thing happen during both tries... I don't think it's the Recovery!

[Solved]Nexus won't boot after ROM and other things

Hello guys, I've searched a little and didn't find any posts that could help me specifically for the Galaxy Nexus.
I've flashed my phone a long time ago and have been using Paranoid Android for probably over a year.
The problem is, my cellphone was really really slow. So I decided to try a new ROM and re-flash it. And So I did.
I've tried flashing this Full_Auto R11 kernel then the CyanogenMod 12 and finally GAPPS.
I was getting error status 6 on Clockwork mod on gapps, but eventually got around it. But it didn't install play store, I've tried manually adding but it didn't work.
So I went for another 5.0 ROM (I'm really interested in getting android 5.0). Wiped all the data, all the cache, installed everything and rebooted.
Bam! Infinite booting screen.
No, I didn't create a nandroid backup because I'm really dumb.
So, I need your help. What I want to do is to get my phone working again with a 5.0 ROM (if possible).
I can boot into ClockWork Recovery just fine, if that helps.
Thank you for the attention.
I would recommend to install latest full factory package from Google.
Then you will start with everything stock, so flash latest TWRP recovery via fastboot (CWM is no longer supported, so error 6 when installing new Lollipop Google Apps appears).
Then in TWRP, do a factory reset, wipe /cache and /system partitions.
Then you can install your Lollipop ROM (over ADB or by pushing ROM package to emulated sdcard).
After this, install latest Full_Auto kernel.
At the end, install Pico Google Apps.
You must install the Pico version, because our /system parition is too small to handle Lollipop with all Google Apps included.
This should work for you, and you will have fully working Lollipop on your Galaxy Nexus
P.S: If you intall the AOSP Lollipop ROM by @freshgiammi and you miss root access, install latest SuperSU flashable zip.
Thank you!
Thank you man!
I've ran into some troubles but managed to do everythings correctly =)
This post can be locked up now.
Thanks again for the reply, LamarrCZ!!

İce Rom home button not working

Hi, I am install ice rom but not working home button.
How fix it this?
MM or Android N firmware?
Powered by HTC 10
2WildFirE said:
MM or Android N firmware?
Powered by HTC 10
Click to expand...
Click to collapse
N
3.1.0
Stock and elemental kernel not working
kallardo said:
N
3.1.0
Stock and elemental kernel not working
Click to expand...
Click to collapse
Please Kids, learn to read, before you flash something!!!
You must flash the rom on MM Firmware and homebutton will work.
kallardo said:
N
3.1.0
Stock and elemental kernel not working
Click to expand...
Click to collapse
You know 3.10 is just rom version and doesn't say anything about firmware? Are you sure you flashed correct firmware too?
Corrupt homebutton is usually the case when running N rom on M firmware.
@BladeOne1
Think you're misunderstanding. When first N roms came out, the custom recoveries couldn't yet work on N kernel. To workaround this problem, u could flash rom first from M environment and flash firmware afterwards.
Anyway, since the hero's behind TWRP already have a working version there's no need for this workaround anymore.
Best way now is to flash firmware (including twrp) first and then boot to recovery to flash rom. There's absolutely no reason to flash N-based roms while on Marshmellow firmware.
@Switcherd
!:
Backup your data, including internal sdcard
The ROM boots on old firmware and dirty flash of the ROM on top of Android M 3.5.0 works!
On the last screen on the installation, choose the firmware you plan to use. If you pick the wrong one your fingerprintscanner and home button won’t work!
After flashing the Android N ROM, TWRP won’t be able to decrypt your data, so you won’t be able to backup/restore etc. It is recommended to run the rom on unencrypted data, so TWRP is fully functionial.
Flashing the new firmware will break TWRP, you will only have a black screen. Therefore you would need to downgrade the firmware to have access to TWRP again.
A TWRP working on new firmware got released: twrp-3.0.2-7-pme-DEBUG.img
If you decide to flash the new firmware, do it AFTER the ROM, you should know why, since you read the above text.
Downgrading firmware should be safe on that base, it has been done by one of our devs several times. On earlier bases it caused a brick. Do it at your own risk, downgrading is always dangerous
When you downgrade, use a full firmware from Sneakyghosts thread. If you use a partial one, you will brick your device!
If the rom does not boot: Only ways that work are: Changing to Dev ED MID and CID and flash the Dev ED RUU/Firmware or following that instructions
Installation Instructions:
Dirty flashing, to keep your data from Android M
Stick with the old 1.9x firmware to have access to TWRP
Backup your Android M rom, best would be Viper10 3.5.0..other roms should work too though
Backup your internal sdcard
format data in TWRP to get rid of encryption
restore your Android M backup
DON’T reboot, else your device will get encrypted again
Flash the 4.x.x rom
Ensure you pick the correct firmware you want to use on the last screen on the setup, else your fingerprint scanner won’t work
Now you got an unenrypted Android N rom, with fully working TWRP
---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------
BladeOne1 said:
@Switcherd
!:
Backup your data, including internal sdcard
The ROM boots on old firmware and dirty flash of the ROM on top of Android M 3.5.0 works!
On the last screen on the installation, choose the firmware you plan to use. If you pick the wrong one your fingerprintscanner and home button won’t work!
After flashing the Android N ROM, TWRP won’t be able to decrypt your data, so you won’t be able to backup/restore etc. It is recommended to run the rom on unencrypted data, so TWRP is fully functionial.
Flashing the new firmware will break TWRP, you will only have a black screen. Therefore you would need to downgrade the firmware to have access to TWRP again.
A TWRP working on new firmware got released: twrp-3.0.2-7-pme-DEBUG.img
If you decide to flash the new firmware, do it AFTER the ROM, you should know why, since you read the above text.
Downgrading firmware should be safe on that base, it has been done by one of our devs several times. On earlier bases it caused a brick. Do it at your own risk, downgrading is always dangerous
When you downgrade, use a full firmware from Sneakyghosts thread. If you use a partial one, you will brick your device!
If the rom does not boot: Only ways that work are: Changing to Dev ED MID and CID and flash the Dev ED RUU/Firmware or following that instructions
Installation Instructions:
Dirty flashing, to keep your data from Android M
Stick with the old 1.9x firmware to have access to TWRP
Backup your Android M rom, best would be Viper10 3.5.0..other roms should work too though
Backup your internal sdcard
format data in TWRP to get rid of encryption
restore your Android M backup
DON’T reboot, else your device will get encrypted again
Flash the 4.x.x rom
Ensure you pick the correct firmware you want to use on the last screen on the setup, else your fingerprint scanner won’t work
Now you got an unenrypted Android N rom, with fully working TWRP
Click to expand...
Click to collapse
Its from Viper Rom, but its the same

Flashing ROM reboot issues, advice massively appreciated.

I rooted my phone yesterday fine and made a backup of my oxygen OS (original rom).
I am definitely successfully unlocked and rooted, and TWRP newest version is running.
I have tried so much to get a new rom running correctly I have tried both resurrection remix official and unofficial:
https://forum.xda-developers.com/on...evelopment/op3-3t-resurrection-remix-t3754941
I have also tried official paranoid android, but every time it starts up I get two issues the first is the error saying "android.media has stopped" the more serious being the fact that no matter which rom I flash it always begins force restarting over and over again, I get into the OS fine, have a scroll around and around every 2 mins or so it just force reboots, then it comes back and is fine for 2 mins then same again.
It has happened with the official and unofficial versions of resurrection remix and also happens exactly the same with paranoid android. I have no idea what else to try at this point.
The process I have been using for flashing is this:
1. Boot into TWRP recovery
2. Wipe everything but internal storage.
3. Install my rom.
4. Reboot.
5. Starts up successfully and then falls back into the standard boot loop and the android.media error.
I have also tried it with GAPPS which was throwing some setup wizard has stopped error, so for now I am just attempting to get an actual rom running without constantly restarting.
Any help is massively appreciated, I am tech savvy, hence why this is annoying me even more.
Thanks,
Kieran
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
jeffrey268 said:
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
Click to expand...
Click to collapse
My backup is the original oxygen and this restores fine and works fine just as soon as I try to flash a new rom it just keeps restarting every few minutes, I dont really know what else to try.
Also to add I sometimes see this issue when I attempt to flash certain roms..... 'assert failed: op3.verify_modem("2017-11-16") == 1'
Use the recommended firmware by the rom. Also you can't flash most roms without Gapps.
1. Flash proper firmware
2. Flash the rom
3. Flash Gapps or something similar.
4. Flash any additional kernel (optional).
5. Flash SuperSU or Magisk.
The assert failed littery tells you that you use using the wrong modem // firmware.
my first question which custom Rom you installed every Rom developer say it is stable but only few has been stable as rock . i tried everything but settled with AICP Rom. and then try to use GAPP as ARM64 android 8.1
u have first install Rom and then GAPP then magisk or Superuser anything which u refer
https://forum.xda-developers.com/on...e-development/wip-official-aicp-13-0-t3713637
this is the Rom which i use it . .they are stable and also update it weekly thrice ..
if u like it you can install this ROM

LG V500 Tablet - Nougat Upgrade Problem (Lineage File)

First off I'm no tech guru, so please provide as much detail as possible if you can so I can follow along... TIA!!
I am trying to upgrade my old LG V500 from KitKat 4.4.2 to Nougat.
I followed details in a video, by downloading the necessary files....
-Latest TWRP App (the APK)
https://dl.twrp.me/twrpapp/
-Latest TWRP Recovery for the v500
https://dl.twrp.me/v500/
-Stump Root
https://forum.xda-developers.com/lg-g...
-LineageOS build for the v500
lineage-14.1-20180909-nightly-v500-signed.zip
I hit Install and selected the above Lineage file and swiped to confirm the flash in TWRP.
What I got was this error...
https://drive.google.com/file/d/12ZY3y9pNaRJxqWHuCJSEmyl5Xmn3CtXq/view?usp=sharing
Now I am confused on what to do. I don't want to lose my old 4.4.2 build since this upgrade didn't work.
I could really use some serious help on what steps I should take. My preference would be to upgrade this tablet, but if I have to revert back then so be it (but don't even know how to do that). Wondering if I did something wrong or this .zip file is just outdated, not sure what else 'Error 7' refers to, other than Error installing .zip file.
Any help would be appreciated!
stargreen said:
Wondering if I did something wrong or this .zip file is just outdated, not sure what else 'Error 7' refers to, other than Error installing .zip file.
Click to expand...
Click to collapse
Most likely that is the case, rom file is two years older than the recovery. You can either:
1. Install newer version of Lineage with that recovery: https://www.los-legacy.de/v500
2. Flash older version of TWRP first and then install that older Lineage, or some other rom (for example I have TWRP version 3.3.1-0 and Resurrection Remix N 5.8.5 FINAL which works flawlessly https://forum.xda-developers.com/lg-g-pad-83/development/testing-resurrection-remix-n-5-8-3-oms-t3601456)
Thx Indie Zex for the options.
My dilemma now is, how would I install this new Lineage with the recovery file, since I am still in TWRP?
Need help on what steps I need to follow to either exit out of TWRP to get the newer Lineage file.
I assume you can't load anything from the link you provided while I'm in TWRP....am I correct?
If I exit out of TWRP now, will I completely lose my original 4.4.2 (KitKat) build?
TY
stargreen said:
My dilemma now is, how would I install this new Lineage with the recovery file, since I am still in TWRP?
TY
Click to expand...
Click to collapse
If I understand correctly, you are still in TWRP on your tablet right? If you performed full wipe of Dalvik Cache/Cache/System/Data (like you always should do before installing a new rom) then you can kiss your KitKat goodbye forever! If for some reason you didn't wipe anything, then in the main menu of TWRP you can select Reboot, then System and your tablet should (luckily) boot into KitKat. But lets say your tablet is wiped and you now have to install new rom:
1. On your computer download https://www.los-legacy.de/v500 and open gapps https://opengapps.org/ (ARM, 7.1, pico)
2. Connect your tablet with computer via usb cable and copy both rom and gapps to internal storage (Windows should see your tablet as a mass storage device no problem even if you're in TWRP and you have proper LG drivers installed)
3. Now on your tablet: from main menu go into Wipe, then Advanced Wipe, then on Select Partitions to Wipe page tick Dalvik Cache/Cache/System/Data and Swipe to Wipe
4. Back to main menu and select Install, then find rom from the internal storage, then Add more zips and find gapps and finally Swipe to confirm Flash
5. Once that's finished press Wipe Dalvik Cache/Cache and then Reboot
That should hopefully be it.
TY Indie Zex,
You understood correctly, and I did a full wipe of Dalvik Cache/Cache/System/Data. I was afraid you would say I lost my old 4.4.2., but I really just wanted some insurance to go back if things got messed up, which they did!
For the legacy OS, I assume I should be going with the very latest lineage file (2020-09-05 date)?
Question about Nougat vs Q or Pie - If I pick Nougat, is there a compatibility upgrade/update path via Nougat OS to get to Pie or Q, easily within the software just by selecting 'Update' option in the 'Settings'?
or if I ever want to add the latest Android OS like Pie or Q, I would have to again go thru the full swipe and re-load another ROM and the specific gapps for either Pie or Q.
I assume Q is still quite new and maybe buggy, but is Pie now very stable or still some unresolved issues? I know it might be difficult to answer, as there are always bugs in firmware version. Just trying to get a gauge for which would be safer to go with if I need to upgrade.
TY you again for being patient with a newbie
stargreen said:
For the legacy OS, I assume I should be going with the very latest lineage file (2020-09-05 date)?
Click to expand...
Click to collapse
Yes, the latest one.
stargreen said:
Question about Nougat vs Q or Pie - If I pick Nougat, is there a compatibility upgrade/update path via Nougat OS to get to Pie or Q, easily within the software just by selecting 'Update' option in the 'Settings'? or if I ever want to add the latest Android OS like Pie or Q, I would have to again go thru the full swipe and re-load another ROM and the specific gapps for either Pie or Q. I assume Q is still quite new and maybe buggy, but is Pie now very stable or still some unresolved issues? I know it might be difficult to answer, as there are always bugs in firmware version. Just trying to get a gauge for which would be safer to go with if I need to upgrade.
Click to expand...
Click to collapse
You always flash custom roms the same way in TWRP, you can not just update unfortunately. The next thing to pay attention to is to download correct version of gapps for Oreo or Pie roms (there are no Q roms for our tablet). You have probably seen this tutorial here for Pie https://forum.xda-developers.com/lg-g-pad-83/general/guide-tutorial-howto-lg-gpad-8-3-v500-t3967069. I have tried it as well as https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076 but they both have broken camera unfortunately. Everything else is basically fine, with Oreo having better performance.
stargreen said:
TY Indie Zex,
You understood correctly, and I did a full wipe of Dalvik Cache/Cache/System/Data. I was afraid you would say I lost my old 4.4.2., but I really just wanted some insurance to go back if things got messed up, which they did!
For the legacy OS, I assume I should be going with the very latest lineage file (2020-09-05 date)?
Question about Nougat vs Q or Pie - If I pick Nougat, is there a compatibility upgrade/update path via Nougat OS to get to Pie or Q, easily within the software just by selecting 'Update' option in the 'Settings'?
or if I ever want to add the latest Android OS like Pie or Q, I would have to again go thru the full swipe and re-load another ROM and the specific gapps for either Pie or Q.
I assume Q is still quite new and maybe buggy, but is Pie now very stable or still some unresolved issues? I know it might be difficult to answer, as there are always bugs in firmware version. Just trying to get a gauge for which would be safer to go with if I need to upgrade.
TY you again for being patient with a newbie
Click to expand...
Click to collapse
Rhetorical questions.
What's wrong with pressing the THANKS icon under Indie Zex's answers instead of writing "TY"?
.
Besides, if you were advised to install a very stable Nougat, why don't you try it first, before thinking about P and Q?
.
Indie Zex said:
Yes, the latest one.
You always flash custom roms the same way in TWRP, you can not just update unfortunately. The next thing to pay attention to is to download correct version of gapps for Oreo or Pie roms (there are no Q roms for our tablet).
TY.
You have probably seen this tutorial here for Pie https://forum.xda-developers.com/lg-g-pad-83/general/guide-tutorial-howto-lg-gpad-8-3-v500-t3967069. I have tried it as well as https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076 but they both have broken camera unfortunately. Everything else is basically fine, with Oreo having better performance.
Click to expand...
Click to collapse
Yes, I did see the Pie tutorial and did read through it, the non-working camera was certainly something I did not want. Good to know you have Oreo running on yours, and better performance.
So do you suggest I load Oreo vs Nougat?
For Oreo would I select v8 or v8.1? and what variant?
I found this info...I was thinking of Micro or Mini, thoughts? Can the V500 handle the memory requirements for these?
Variant:
Aroma: Graphical installer of the super package while in recovery menu, it allows user to select which applications to install.
Super: Includes all Google Apps that were ever shipped on a Google device.
Stock: Recommended package that contains all Google Apps that come standard on latest Nexus/Pixel phone.
Full : Very similar to Stock version.
Mini : Smaller set of popular Google Apps with extra functionality.
Micro: Limited set of Google Apps with Gmail, Calendar Google Now with extra functionality.
Nano : Minimal installation with extra functionality.
Pico : Minimum with Google Play functionality. (Each package varies with file sizes and included Google Apps)
TY again, much appreciated!
ze7zez said:
Rhetorical questions.
What's wrong with pressing the THANKS icon under Indie Zex's answers instead of writing "TY"?
Click to expand...
Click to collapse
Haha calm down ze7zez, he probably doesn't even know how . We've all been young and innocent once...
Indie Zex said:
Haha calm down ze7zez, he probably doesn't even know how . We've all been young and innocent once...
Click to expand...
Click to collapse
You right Indie Zex, Thx for the patience...hit the Thx icons for you!
Can you just take a few secs to answer my last few questions in last post, please?
stargreen said:
Good to know you have Oreo running on yours, and better performance.
Click to expand...
Click to collapse
No, as a matter of fact I have Resurrection Remix N 5.8.5 FINAL installed on TWRP version 3.3.1-0.
stargreen said:
For Oreo would I select v8 or v8.1? and what variant?
Click to expand...
Click to collapse
There is only one version of Oreo for our tablet: https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076. I have tried it, it runs nicely but camera DOES NOT work just like in Pie version (which is a little bit choppy for my taste).
stargreen said:
I found this info...I was thinking of Micro or Mini, thoughts? Can the V500 handle the memory requirements for these?
Click to expand...
Click to collapse
I wouldn't go above micro, 2GB of ram is a little bit tight. But hey, if you like Google so much try and see how it runs.
stargreen said:
So do you suggest I load Oreo vs Nougat?
Click to expand...
Click to collapse
Since you already have latest TWRP version installed, I suggest you go with latest lineage rom (2020-09-05) with gapps of your choice. For Oreo and other older roms you need to flash older TWRP version, such as above mentioned 3.3.1-0 (and please do not ask how ).
And finally I wanna say this: don't worry if you mess something up, you already have and you certainly will again :laugh:. There is a wonderful world of flashing roms (and wasting your precious time ) ahead of you, so go boldly into the unknown! :fingers-crossed:
Indie Zex said:
No, as a matter of fact I have Resurrection Remix N 5.8.5 FINAL installed on TWRP version 3.3.1-0.
There is only one version of Oreo for our tablet: https://forum.xda-developers.com/lg-g-pad-83/development/rom-crdroid-android-t3772076. I have tried it, it runs nicely but camera DOES NOT work just like in Pie version (which is a little bit choppy for my taste).
I wouldn't go above micro, 2GB of ram is a little bit tight. But hey, if you like Google so much try and see how it runs.
Since you already have latest TWRP version installed, I suggest you go with latest lineage rom (2020-09-05) with gapps of your choice. For Oreo and other older roms you need to flash older TWRP version, such as above mentioned 3.3.1-0 (and please do not ask how ).
And finally I wanna say this: don't worry if you mess something up, you already have and you certainly will again :laugh:. There is a wonderful world of flashing roms (and wasting your precious time ) ahead of you, so go boldly into the unknown! :fingers-crossed:
Click to expand...
Click to collapse
I guess I misunderstood you earlier on which rom you where using, thought it was Oreo. Does the camera function with this Resurrection Remix N 5.8.5 FINAL? Based on the Variant list I posted, how would you categorize this rom?
I am intrigued, I thank you for the words of encouragement, just a bit intimidating this world, but I am willing to try!
stargreen said:
I guess I misunderstood you earlier on which rom you where using, thought it was Oreo. Does the camera function with this Resurrection Remix N 5.8.5 FINAL? Based on the Variant list I posted, how would you categorize this rom?
Click to expand...
Click to collapse
Camera (and everything else) works on all Nougat (and earlier) roms. Differences between them come down to customization: for example Resurrection Remix N 5.8.5 FINAL and crDroid Android 4.7 offer more customization options compared to LineageOs, but are two years old. Latest Lineage, on the other hand, has literally last month security patches. And I suggest you install them all, one at a time
Indie Zex said:
Camera (and everything else) works on all Nougat (and earlier) roms. Differences between them come down to customization: for example Resurrection Remix N 5.8.5 FINAL and crDroid Android 4.7 offer more customization options compared to LineageOs, but are two years old. Latest Lineage, on the other hand, has literally last month security patches. And I suggest you install them all, one at a time
Click to expand...
Click to collapse
I followed your instructions...at least I'm pretty sure I did. lol
I got an install Error 20, it says to download the correct version for my rom 6.0.1
I went with the GAPPS file (ARM, 7.1, micro)
Does this mean I cannot use the micro variant?
stargreen said:
I followed your instructions...at least I'm pretty sure I did. lol
I got an install Error 20, it says to download the correct version for my rom 6.0.1
I went with the GAPPS file (ARM, 7.1, micro)
Does this mean I can use the micro variant?
Click to expand...
Click to collapse
Hm, the error suggests that you have 6.0.1 rom which you tried to flash with 7.1 gapps. Just in case, download older version twrp-3.3.1-0-v500.img and flash it in TWRP:
1. Copy twrp-3.3.1-0-v500.img from computer to internal storage of a tablet
2. In main menu of TWRP select Install, then Install Image
3. Choose twrp-3.3.1-0-v500.img and flash it (IMPORTANT: do not reboot right away!)
4. Go back to main menu then press Reboot and select Recovery
5. You will boot to recovery again, now the older version
6. Now flash rom ONLY (whichever Nougat variant you want) with standard described procedure (with wipe and everything) and reboot
7. Once you are in system, check it out and come back later into TWRP to install correct gapps (yes, you can use micro)
---------- Post added at 12:54 AM ---------- Previous post was at 12:23 AM ----------
And let me know did you make it in about 8 hours, it's late here so I have to sleep
Indie Zex said:
Hm, the error suggests that you have 6.0.1 rom which you tried to flash with 7.1 gapps. Just in case, download older version twrp-3.3.1-0-v500.img and flash it in TWRP:
1. Copy twrp-3.3.1-0-v500.img from computer to internal storage of a tablet
2. In main menu of TWRP select Install, then Install Image
3. Choose twrp-3.3.1-0-v500.img and flash it (IMPORTANT: do not reboot right away!)
4. Go back to main menu then press Reboot and select Recovery
5. You will boot to recovery again, now the older version
6. Now flash rom ONLY (whichever Nougat variant you want) with standard described procedure (with wipe and everything) and reboot
7. Once you are in system, check it out and come back later into TWRP to install correct gapps (yes, you can use micro)
---------- Post added at 12:54 AM ---------- Previous post was at 12:23 AM ----------
And let me know did you make it in about 8 hours, it's late here so I have to sleep
Click to expand...
Click to collapse
Hi Indie Zex,
I read your above instructions, but somewhat confused.
I looked for twrp-3.3.1-0-v500.img but can't seem to find it, has the file name changed?
I went to the link page you provided (below) for your Resurrection Remix build, and the Rom available there was RR-N-v5.8.5-20171001-v500-Final.zip
2. Flash older version of TWRP first and then install that older Lineage, or some other rom (for example I have TWRP version 3.3.1-0 and Resurrection Remix N 5.8.5 FINAL which works flawlessly https://forum.xda-developers.com/lg-...3-oms-t3601456)
stargreen said:
I looked for twrp-3.3.1-0-v500.img but can't seem to find it, has the file name changed?
Click to expand...
Click to collapse
Download twrp-3.3.1-0-v500.img from official page here https://dl.twrp.me/v500/
stargreen said:
I went to the link page you provided (below) for your Resurrection Remix build, and the Rom available there was RR-N-v5.8.5-20171001-v500-Final.zip
Click to expand...
Click to collapse
Yep, that is the "newest" one which I have installed. If download link is broken, you can get rom from here https://androidfilehost.com/?fid=4349826312261778561
Indie Zex said:
Download twrp-3.3.1-0-v500.img from official page here https://dl.twrp.me/v500/
Yep, that is the "newest" one which I have installed. If download link is broken, you can get rom from here https://androidfilehost.com/?fid=4349826312261778561
Click to expand...
Click to collapse
Before I try to flash my tablet with twrp-3.3.1-0-v500.img, what do I need to do with the lineage-14.1-20200905-UNOFFICIAL-v500.zip that I ran and is still in Internal storage. Can I just delete via my computer, or do I need to remove it thru TWRP?
stargreen said:
Before I try to flash my tablet with twrp-3.3.1-0-v500.img, what do I need to do with the lineage-14.1-20200905-UNOFFICIAL-v500.zip that I ran and is still in Internal storage. Can I just delete via my computer, or do I need to remove it thru TWRP?
Click to expand...
Click to collapse
If you don't need it anymore, you can delete it via computer. It doesn't really matter when you install .img file. When you select install image in main menu of TWRP you won't see any other files except for .img ones. Just make sure to reboot to recovery instead of reboot to system to continue with installing rom.
Indie Zex said:
If you don't need it anymore, you can delete it via computer. It doesn't really matter when you install .img file. When you select install image in main menu of TWRP you won't see any other files except for .img ones. Just make sure to reboot to recovery instead of reboot to system to continue with installing rom.
Click to expand...
Click to collapse
Great TY.
So from yesterday when my install failed, I just need some direction on what do I do to get out of this screen, please.
I have the option button to Wipe Cache/Dalvik or Reboot System.
Do I need to hit the Wipe button to remove the lineage-14.1-20200905-UNOFFICIAL-v500.zip? Or Wipe anything else?
Or do I just go back to the main menu for TWRP and install the twrp-3.3.1-0-v500.img and follow the rest of your instructions?
TY again.

Categories

Resources