Related
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Flash fastboot room
Flash fastboot rom
always flash miui with mi flasher
[SOLVED]
alfarhaannizam said:
Flash fastboot rom
Click to expand...
Click to collapse
Worked like a charm. Downloaded MIUI 10.2.3 fastboot rom and flashed using Xiaomi Adb/Fastboot Tools. And then updated to MIUI 10.3.4 via system updater.
Thanks for the heads up. It was really helpful.
mendax99 said:
always flash miui with mi flasher
Click to expand...
Click to collapse
Mi Flasher don't work allright in my computer, since I only have USB 3.0 on my windows device and it seems MI Flasher doesn't work with USB 3.0
I'm using, usually command line abd and fastboot on windows. Today I've downloaded Xiaomi ADb/Fastboot Tolls and it was very useful.
I can't post links yet since I'm new on the forum. But search for Xiaomi ADB/Fastboot Tools GitHub. it is powerful.
otaodofino said:
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Click to expand...
Click to collapse
Why just not just freeze the app/ service ? That's what I did.
MasterFURQAN said:
Why just not just freeze the app/ service ? That's what I did.
Click to expand...
Click to collapse
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
otaodofino said:
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
Click to expand...
Click to collapse
Yeah. I know that flashing a fastboot ROM is the best way to repair corrupt partitions but it also resets the phone and I'm too lazy to restore everything back. Lol.
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
No custom roms at this time, why bother when you can custom Android 9 using Magisk , Xposed and Substratum. Although having a Lineage 17 would be nice.
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
lschafroth2 said:
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
Click to expand...
Click to collapse
If you private message me I cannot get to the messages here. If I click on messages it takes me to the register or reset password every time. I have no way to read them.
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
lschafroth2 said:
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
Click to expand...
Click to collapse
This might seem obvious, but could never get my PC (Windows10 64bit) to even recognize my Oukitel K9 until I (out of desperation, and to try to prove a point to someone) reinstalled Minimal ADB & Fastboot 1.4.3 from here:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
It's the same thing I had previously installed, and I didn't expect it to suddenly/miraculously start working, but it did.
I'll pm you.
lschafroth2 said:
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
Click to expand...
Click to collapse
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
nation888888 said:
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
Click to expand...
Click to collapse
Thanks, but I sold this phone and went to a Pixel 4 XL. I needed something reliable and InTune refused to work on the old Oukitel.
Has anyone worked out ramdisk partition for Magisk?
Discovery,
Thanks to Phh has developed the perfect ROM for the Oukitel K9. Strangely I have had to try many ROMs to find the perfect one. The Lineage ROM; I had GPS issues, the Recent app button not working, and signal loss. Wanted the latest OS and this one is the winner below.
https://github.com/phhusson/treble_experimentations/releases/download/v400.e/system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Llevo un par de semanas probando la rom y no funciona el detector de huellas,se puede mejorar?hay alguna rom(Android 12) mas estable y que todo funcione?,gracias
MOD Edit: I've been testing the rom for a couple of weeks and the fingerprint sensor doesn't work, can it be improved? Is there a more stable rom (Android 12) that makes everything work? Thanks
Try the updated version https://github.com/phhusson/treble_experimentations/releases/tag/v402
Should resolve the fingerprint issue. I have also tried the AOSP 12.1 v410 and the result is the phone goes into a boot loop. Not sure why when the previous version installs so easily. I have built a custom TWRP 3.6.1 and will be trying it soon. The reason why we need to update; that the TWRP 3.3.1 version is limited and could be the reason why there are install issues with some GSIs out there. The encryption keeps reactivating even if I use scripts, flash no verify-verity. Hopefully, this will work. I'm enjoying the new version too much to start again I will keep you posted.
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
nation888888 said:
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
Click to expand...
Click to collapse
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
[email protected]@ said:
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
Click to expand...
Click to collapse
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
Thanks a lot. I will give it a try!
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
I've flashed this one and found it is as laggy as CrDroid. I thought it might be due to not wiping data before flashing. Decided to reboot to recovery to wipe data. And.. phone stuck at twrp logo. No go further. Do you have any better TWRP than mine 3.3.1?
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
TWRP logo is for hours here.
Now I can't even enter fastboot after I've chosen reboot to recovery from cherishos power menu.
I hit volup+pwr and boot menu doesn't even show up. Tried 20+ times already.
I'm stuck. The last hope is to wait for it to discharge on twrp logo and try my luck with fastboot menu again.
Otherwise I have no idea. Now I question myself why on Earth I would even try to better something that works at least average ))))
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
I've managed to revive it. But still on cherishos and few other A13 roms screen is flickering. Have you got something like that?
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.