I am not responsible for anything that can go wrong... YOU HAVE BEEN WARNED!!!
Introduction
When Alcatel released Android 6 for there Idol 3 phones the Fastboot commands required to root were removed making it impossible. Well I have found a way and I was quite surprised that it worked. In this guide I will give a step by step tutorial on how to 1) Flash TWRP Recovery 2) Flash a Custom Rom 3) Flash GAPPS onto the Custom Rom. If you have any questions please ask away!
For this tutorial we will be flashing the Resurrection Remix Rom onto our phone.
I will be using the 5.5 variation for this tutorial
For the 4.7 variation, the steps should be the same but you will need to download the appropriate files for your device
What you will need
• A Windows PC
• Administrator privileges on the PC
• Extracting Software; WinRAR, WinZIP, etc (I'm not including the link, they are easy to find)
• A good Internet connection (for files to download faster)
• An Alcatel Idol 3 4.7 or 5.5 running Android 6.0.1
• A MicroSD card in your phone (To hold a backup and to hold our Flashable files)
• The Alcatel Drivers installed
• Files provided by link down below
Files Needed
*Note: Non of these links are mine, but they all worked and seemed safe to me*
*The links send you right to the download page, not to the forum where they came from*
• Sahara & Firehose Test [Broken] | New Sahara & Firehose Test [Uploaded by XDA Member]
• TWRP V3.1.1 for Idol 3
• Open GAPPS (Platform: ARM64, Android: 7.1, Variant: Whichever one you want (I'd recommend Stock)
• Resurrection Remix a.k.a the ROM
Getting things ready on Windows
Step 1: Drag all your files onto your desktop (To keep things tidy put them into a folder)
Step 2: Extract "Alcatel_Flasher" (Password: decker.su)
Step 3: DO NOT Extract the ROM or GAPPS
Preparing Phone
*Note: Make sure your phone has at least 70% Battery, if the battery dies during a flash it can break things*
*Make sure you device is also plugged into the computer*
Step 1: Turn off your device completely
*Note: Since the device is plugged into the computer it may "Turn on" again, this is just the phone going to the battery screen*
Step 2: Push and Hold the Power and Both the Volume Buttons
*Note: You should now see a Red Screen*
Step 3: Release All Buttons
Step 4: Quickly Hold the Volume Up Button until the screen turns Black
Flashing TWRP to the phone
*Now back to the PC*
Step 1: Open Alcatel_Flasher
Step 2: Next to "Device Model" select "Alcatel Idol 3 5.5" [OT-6045]"
Step 3: Click the "Detect" Button
*Note: Next to "COM #" there should now be something in the box*
Step 4: Click the "NPRG" Button
*Note: The console in the window should now have "Send done command" near the bottom of it*
Step 5: Click the "Get GPT" Button
*Note: The bottom of the window should now be full of Partition names and other information*
Step 6: Scroll down to "Recovery" (It might be 27 on the list)
Step 7: Scroll Across to "Filename"
Step 8: Check the Box next to "Filename"
Step 9: Double click inside the "Filename" Box
*Note: A prompt to select a .img file should have popped up*
Step 10: Locate the "twrp-3.1.1-idol3.img" file
Step 11: Open it
Step 12: Click the "Write" Button
Step 13: Click "No"
Step 14: Wait until the progress bar is full
Entering TWRP
Step 1: Hold the Power and Volume Up Buttons
Step 2: Wait for a vibration and then release the Power Button but continue holding the Volume Up Button
*Note: TWRP should have now opened*
*Note: If asked "Swipe to Allow Modifications"
Backing Up the device
Step 1: Press "Backup"
Step 2: Press "Select Storage"
Step 3: Select your MicroSD Card
Step 4: Press "OK"
Step 5: Select the Partitions you want to backup (I like to have a full backup)
Step 6: "Swipe to Backup"
*Note: Wait for the backup to complete, it may take a while but it's good to know that you have a backup if anything goes wrong*
Step 8: Press the NavBar Back button twice
Wiping the Storage
Step 1: Press "Wipe"
Step 2: Press "Advanced Wipe"
Step 3: Select "Dalvik / ART Cache", "System", "Data", "Internal Storage" and "Cache" (Nothing else)
Step 4: "Swipe to Wipe"
*Note: This Shouldn't take long*
Step 5: Press the NavBar Back button three times
Placing the Flashable files on the MicroSD Card
Step 1: Press "Mount"
Step 2: Press "Mount USB Storage"
*Note: "File Explorer" should have opened on your PC*
Step 3: Drag the "open_gapps-arm64-7.1-stock-20180216" and the "RR-N-v5.8.5-20171002-idol3-Unofficial.zip" into the MicroSD Card
Step 4: Wait for the transfer to complete and then Press "Unmount"
Step 5: Press the NavBar Back Button once
Flashing the ROM
*Remember that I am not responsible for anything that may happen to your device*
Step 1: Press "Install"
Step 2: Press "Select Storage"
Step 3: Select your MicroSD Card and then Press "OK"
Step 4: Select "RR-N-v5.8.5-20171002-idol3-Unofficial.zip"
Step 5: "Swipe to confirm Flash"
*Note: This might take a while*
Step 6: Press "Wipe chache/dalvik"
Step 7: "Swipe to Wipe"
*Note: DO NOT go on to flash GAPPS just yet, doing so can cause a boot loop. We will flash it later*
Step 8: "Reboot System"
*Note: The first Boot will take a long time, about 5 or so minutes*
*Note: Please keep your device plugged in to power during this time*
*Note: For some reason the phone is already set up*
Step 9: Choose a launcher
Flashing GAPPS
Step 1: Go back into TWRP
*Note: If asked "Swipe to Allow Modifications"
Step 2: Press "Install"
Step 3: Press "Select Storage" and choose your MicroSD Card and Press "OK"
Step 4: Select "open_gapps-arm64-7.1-stock-20180216"
Step 5: "Swipe to confirm Flash"
*Note: The "Super GAPPS" will open an installer for you to select which apps you want*
*Note: This can take some time*
Step 6: Press "Wipe cache/dalvik"
Step 7: "Swipe to Wipe"
Step 8: Press "Reboot System"
Step 9: Uncheck the 2 Boxes and Press "Do Not Install"
*Note: We do not need the app because we are using a version of TWRP that is modified to work on our device, so the app wouldn't do anything anyway*
Thaks a lot ^^*
Really appreciate you making this step-by-step noob-friendly guide. Worked for me exactly as advertised.
I had actually tried to flash TWRP and a custom ROM a few months ago after piecing together the necessary information from a few different threads scattered throughout the forum, but for some reason I couldn't get the Alcatel Flasher to properly read my phone's GPT. I spent hours trying different USB ports, different drivers, nothing. This time it worked flawlessly on the first try :victory: Maybe a Windows update between then and now fixed something.
It is so unbelievably nice to have a clean ROM for this phone after all this time. I've been doing my best to mitigate the malware stuffed onto it by Alcatel with the last few system updates and had finally reached the end of my tether. It's like a completely different device and plenty stable enough for a daily driver.
*edit* I think it would be nice if this thread was stickied since it consolidates all of the necessary information into an easy guide for novices.
thunderweasel said:
Really appreciate you making this step-by-step noob-friendly guide. Worked for me exactly as advertised.
I had actually tried to flash TWRP and a custom ROM a few months ago after piecing together the necessary information from a few different threads scattered throughout the forum, but for some reason I couldn't get the Alcatel Flasher to properly read my phone's GPT. I spent hours trying different USB ports, different drivers, nothing. This time it worked flawlessly on the first try :victory: Maybe a Windows update between then and now fixed something.
It is so unbelievably nice to have a clean ROM for this phone after all this time. I've been doing my best to mitigate the malware stuffed onto it by Alcatel with the last few system updates and had finally reached the end of my tether. It's like a completely different device and plenty stable enough for a daily driver.
Click to expand...
Click to collapse
You're using the Rom suggested in the instructions, right? Which Provider are you using and have you noticed any issues? I've had a bad experience with an unofficial ROM in the past that ruined certain features on a phone, and I noticed there were still a few people saying there where things not working properly in this release and apparently no more work is being done on it? so I'm understandably hesitant because I'd hate to do it and end up just as irritated knowing the only options are live with it or go back to the poison Alcatel hit us with. Anything you can tell me about it would be helpful as I don't feel like much has been said since this thread started.
PN04 said:
You're using the Rom suggested in the instructions, right? Which Provider are you using and have you noticed any issues? I've had a bad experience with an unofficial ROM in the past that ruined certain features on a phone, and I noticed there were still a few people saying there where things not working properly in this release and apparently no more work is being done on it? so I'm understandably hesitant because I'd hate to do it and end up just as irritated knowing the only options are live with it or go back to the poison Alcatel hit us with. Anything you can tell me about it would be helpful as I don't feel like much has been said since this thread started.
Click to expand...
Click to collapse
Yes, I'm using the Resurrection Remix ROM from the OP. I'm on a unlocked 6045I model; from what I've read a few users with the Cricket (6045O, I think?) variant have run into some quirks that other 6045 variants don't have, so YMMV. I'm in the US using a AT&T-based MVNO (H2O wireless) and haven't had any problems. It detected my SIM immediately on first boot, incoming and outgoing calls as well as mobile data (H+ and LTE) works. BT works. I don't use NFC, but the menu options for it are all there, so it probably works. Audio and video playback works. Camera works. Video recording works, but everything comes out about 3 shades darker than the still camera (this is a known bug on this ROM). Play Store works. I installed the nano GApps, so I can't speak to the full suite of Google services, but Gmail, Hangouts and Maps work. Other than that there's really not much I use on my phone, but Firefox and the handful of puzzle games I play all run just fine. App changes, screen changes and scrolling are all a lot smoother on this ROM than stock. I used to get a fair amount of lag doing those activities on both the old Lollipop and Marshmallow stock ROMs. The flip feature where you can answer calls with the phone upside down doesn't work, but A) I never used that feature on the stock ROM anyway, and B) it stopped working for me on the stock MM ROM after the last System Apps update a few weeks ago (the tilt sensor stopped working entirely in all apps except the camera, actually). I've yet to put the battery life to the test, but it would have to be absolutely atrocious to convince me to switch back, and I've seen no signs of that yet. After installing and spending probably 1-2 hours setting things up and screwing around testing features, the battery was at about 95%. To me it's no contest, the RR ROM is streets ahead of the factory ROM. I'd be willing to put up with a lot of quirks just to get rid of the Joy Launcher, but really the only minor issue I've run into is with the video recording, which isn't a big deal to me as I very rarely ever use it. Everything else is daily driver quality.
thunderweasel said:
Yes, I'm using the Resurrection Remix ROM from the OP. I'm on a unlocked 6045I model; from what I've read a few users with the Cricket (6045O, I think?) variant have run into some quirks that other 6045 variants don't have, so YMMV. I'm in the US using a AT&T-based MVNO (H2O wireless) and haven't had any problems. It detected my SIM immediately on first boot, incoming and outgoing calls as well as mobile data (H+ and LTE) works. BT works. I don't use NFC, but the menu options for it are all there, so it probably works. Audio and video playback works. Camera works. Video recording works, but everything comes out about 3 shades darker than the still camera (this is a known bug on this ROM). Play Store works. I installed the nano GApps, so I can't speak to the full suite of Google services, but Gmail, Hangouts and Maps work. Other than that there's really not much I use on my phone, but Firefox and the handful of puzzle games I play all run just fine. App changes, screen changes and scrolling are all a lot smoother on this ROM than stock. I used to get a fair amount of lag doing those activities on both the old Lollipop and Marshmallow stock ROMs. The flip feature where you can answer calls with the phone upside down doesn't work, but A) I never used that feature on the stock ROM anyway, and B) it stopped working for me on the stock MM ROM after the last System Apps update a few weeks ago (the tilt sensor stopped working entirely in all apps except the camera, actually). I've yet to put the battery life to the test, but it would have to be absolutely atrocious to convince me to switch back, and I've seen no signs of that yet. After installing and spending probably 1-2 hours setting things up and screwing around testing features, the battery was at about 95%. To me it's no contest, the RR ROM is streets ahead of the factory ROM. I'd be willing to put up with a lot of quirks just to get rid of the Joy Launcher, but really the only minor issue I've run into is with the video recording, which isn't a big deal to me as I very rarely ever use it. Everything else is daily driver quality.
Click to expand...
Click to collapse
Thanks, this is helpful to know. The compass/rotation/gyro sensors are something I use fairly often for various apps, and is one of the reasons I haven't outright just bought a new phone (because It's been hard finding phones that have both and are reliable)... oddly enough this was one of the issues with the last phone I had where the custom rom, installed by the seller, disabled the compass sensor. At this point I'd be happy just going back to the stock version of the rom, but it seems like there are more difficulties in doing that.
Supposedly once you root the phone you can use another to delete (rather than just debloat) the offending apps causing all the trouble. Maybe if this can get me to that point I might be able to just delete them and continue using the phone normally?
PN04 said:
Thanks, this is helpful to know. The compass/rotation/gyro sensors are something I use fairly often for various apps, and is one of the reasons I haven't outright just bought a new phone (because It's been hard finding phones that have both and are reliable)... oddly enough this was one of the issues with the last phone I had where the custom rom, installed by the seller, disabled the compass sensor. At this point I'd be happy just going back to the stock version of the rom, but it seems like there are more difficulties in doing that.
Supposedly once you root the phone you can use another to delete (rather than just debloat) the offending apps causing all the trouble. Maybe if this can get me to that point I might be able to just delete them and continue using the phone normally?
Click to expand...
Click to collapse
To be clear, the tilt sensor works perfectly in the RR ROM. It had gotten screwed up for me on the stock Marshmallow ROM with the last set of System Apps updates for some reason.
You can take a system backup once you get the TWRP recovery installed, so my recommendation would be to try the RR ROM and then keep your backup so you can flash back to the stock system if you need to. Rooting and debloating the stock ROM might be an option, but the RR ROM is complete enough that it's worth the upgrade to the Nougat base, IMO.
thunderweasel said:
To be clear, the tilt sensor works perfectly in the RR ROM. It had gotten screwed up for me on the stock Marshmallow ROM with the last set of System Apps updates for some reason.
You can take a system backup once you get the TWRP recovery installed, so my recommendation would be to try the RR ROM and then keep your backup so you can flash back to the stock system if you need to. Rooting and debloating the stock ROM might be an option, but the RR ROM is complete enough that it's worth the upgrade to the Nougat base, IMO.
Click to expand...
Click to collapse
Okay, then I guess I'll give it a shot (at least once I can get a spare moment where I can be phoneless for the process to complete.).
I've managed to install the new ROM, and boy, was it an adventure. While relatively "simple" there were variances between the instructions an what actually occurred between the screens on both the phone and my PC. I'm still evaluating the phone itself, and I'll probably post about it later if I find anything that others might want to know, but I will say it's refreshing to no longer have to worry about Alcatel's crappy software.
On the subject of the actual update. Again it seemed fairly simple aside from the fears of the USB getting unplugged during some important step but I'd say the first place where things went off the rails was Alcatel's drivers. Plugging the phone into my computer resulted in a driver install error, forcing me to got to Alcatel's website to download them... surprise! their website is suspiciously broken, so I had to find another source.
Next I needed to manually install the Legacy Devices because of the driver install error, and the instructions I googled assume I've clicked on a device first otherwise the option doesn't appear in the menu (not an entirely obvious thing), there were a couple of other cheek clenchers as I still got a few errors, but despite ignoring them things went okay in the Flashing TWRP stage, but I had to double click the check box rather than the filename box which only required one. The instructions that refer to backing out via the Nav bar didn't match so in one case I think the instruction was to back out 3 times I only had to go once and where it said once I think I needed to back out twice.
After flashing the Rom and being given the option to reboot the phone, it asks right then if you want to install TWRP as a system app. I tried to back out thinking maybe I missed something and ended up flashing the software twice, because it's not mentioned in the instructions until the GAPPS installation section later, so I wasn't sure if this would cause a Boot loop error. I decide it's not the GAPPS so I figure it's safe to install, the phone reboots without a problem, I pick the Pixel launcher and then go back to TWRP ( thinking "hopefully this didn't bork anything").
During the installation of GAPPS it never gave me an installer list to select which apps I wanted, it just automatically gave me all of them as far as I can tell, but I guess if I have bloat at least it's Google bloat that adheres to the rules and only works when you want it to I'll probably end up disabling some of these but most I think are still technically useful.
After it completed the installation I was given the option to reboot, and that's when I realized that there were no check boxes or "Do Not Install" option, but there was back after I first installed the new ROM, and that's where this I needed to see this instruction. Again, I don't think this messed up anything, but I'm still wading through the new phone and it's options right now (holy crap, is there a lot in here). I predict there may still be a few more unintentional crashes on the horizon, like the phone app crashing every time I opened it after the first time swapping between photo and video modes (I did get it back working by using the power button double click method to start it).
Fingers crossed, this may have saved me enough cash to be able to by a new computer.
Installing the TWRP standalone app won't hurt anything, it's just useless on this phone since we're using a custom TWRP image that will never be updated. I ran into the same screen, but I had pre-read the instructions and recognized the option from the GApps section and unchecked it.
I didn't get any options to choose specific apps when I installed GApps either, but I assumed that was because I chose the nano image rather than the full image. If you don't like the included apps, you can always boot into TWRP and install the nano or pico GApps package. Those will give you a much more minimal installation that gives you access to Play Store and basic Google services, and then you can pick which specific Google apps you want from Play Store.
Since I mentioned battery life before, I can report that the battery life on this ROM is substantially better than the stock ROM. With my usage patterns, I usually charge after 6 days and at that time the battery is usually in the 15-18% range. On this ROM after 6 days of typical usage the battery is at 49%. Very happy with that.
thunderweasel said:
Installing the TWRP standalone app won't hurt anything, it's just useless on this phone since we're using a custom TWRP image that will never be updated. I ran into the same screen, but I had pre-read the instructions and recognized the option from the GApps section and unchecked it.
I didn't get any options to choose specific apps when I installed GApps either, but I assumed that was because I chose the nano image rather than the full image. If you don't like the included apps, you can always boot into TWRP and install the nano or pico GApps package. Those will give you a much more minimal installation that gives you access to Play Store and basic Google services, and then you can pick which specific Google apps you want from Play Store.
Since I mentioned battery life before, I can report that the battery life on this ROM is substantially better than the stock ROM. With my usage patterns, I usually charge after 6 days and at that time the battery is usually in the 15-18% range. On this ROM after 6 days of typical usage the battery is at 49%. Very happy with that.
Click to expand...
Click to collapse
The weird thing is I didn't even get the option for the "nano" version. When I got to that point I expected at least that, but it just skipped passed that item in the instructions and installed everything. They didn't take up much room thankfully, but yeah, the option to remove the ones I may fond don't care for later is a relief.
I feel like I'm getting less battery life, personally. I still make it through most of the day but just checking my messages in the morning I seem to like 5% of my charge in the first 10 minutes and I only have my screen brightness on like 15% or 25%. I've even become a lot more cautious about what functions I leave active when it's idling (usually none), but the drop off seems much steeper than before.
As for other issues. the one major thing I've definitely noticed is that the Proximity sensor no longer works, I have to manually turn off the screen when I get a call. The sensor test app I tried even crashed when I tried to test it. I guess if any of my sensors had to go I'm most okay with this one. Double tapping the top of the screen to sleep is a little odd, I used the original Double tap to wake/sleep all the time before so not so much a flaw but this choice was awkward for me. I also experienced a weird situation where I had no mobile internet the first time I left the house with it, I could get calls and texts but neither my webbrower nor games that rely on an internet connection worked. I fiddled with a bunch of options that I'm not even sure apply to the US (I turned off some radio options that were meant for Brazil and India then tried to refresh my APN) and then finally rebooted before it finally worked. I have to see if it happens again next time before I get worried, though.
I run very few apps and the phone spends most of its time either idle or doing emails, so that might explain the difference in battery life. My screen brightness is set to auto.
I hadn't even noticed until you mentioned it, but I just checked and I get the same thing with the proximity sensor. I wonder if I've been hitting buttons during calls this whole time... Still an acceptable compromise as far as I'm concerned.
I had to manually input my provider's APN settings and toggle mobile data from off to on in order to get mobile data access, but that's the expected behavior. I had to do the same setup on the stock ROM. Haven't dropped the network once yet, and no issues with performance.
thunderweasel said:
I run very few apps and the phone spends most of its time either idle or doing emails, so that might explain the difference in battery life. My screen brightness is set to auto.
I hadn't even noticed until you mentioned it, but I just checked and I get the same thing with the proximity sensor. I wonder if I've been hitting buttons during calls this whole time... Still an acceptable compromise as far as I'm concerned.
I had to manually input my provider's APN settings and toggle mobile data from off to on in order to get mobile data access, but that's the expected behavior. I had to do the same setup on the stock ROM. Haven't dropped the network once yet, and no issues with performance.
Click to expand...
Click to collapse
I shut down all my apps when I finish with them (sometimes even when I'm not done with them) so we're probably not that different in terms of usage I feel like maybe there's some setting I haven't tried. I don't use the auto because I find auto modes get darker than I want it to be and brighter than I need it most of the time so I stick with a low but consistent brightness to avoid wasting battery when it gets bright.
I wear a wired earbud a lot of the time so I didn't notice the lack of proximity sensor until I had to answer without it a couple days into the change. Depending on whether you're calling someone or answering the problem is a little different. On dialing buttons from the dialer or address book are at risk of being pressed, but when answering I think the only one I almost pressed was the loud speaker button.
Depending on who your Provider is it may already have the APN settings built in (T-mobile lte in my case) so you probably just have to register it to get your mobile data to start after a reboot. Today I did some grocery shopping and it didn't miss a beat so it seems to be working fine now.
THANK YOU. I am free from bloat ware and a botched root attempt with some other random tool that ended up installing more bloatware.
Possible change to the guide,
Flashing the Rom Step 8. vs Flashing the GAPPS step 9 uncheck the two boxes... maybe this step should have been in the flashing the rom part.
No Problem
xz3064 said:
Thaks a lot ^^*
Click to expand...
Click to collapse
No problem, sorry for not getting back sooner notifications have been disabled.
RobbieRobski said:
THANK YOU. I am free from bloat ware and a botched root attempt with some other random tool that ended up installing more bloatware.
Possible change to the guide,
Flashing the Rom Step 8. vs Flashing the GAPPS step 9 uncheck the two boxes... maybe this step should have been in the flashing the rom part.
Click to expand...
Click to collapse
I'll look into it
thunderweasel said:
I run very few apps and the phone spends most of its time either idle or doing emails, so that might explain the difference in battery life. My screen brightness is set to auto.
I hadn't even noticed until you mentioned it, but I just checked and I get the same thing with the proximity sensor. I wonder if I've been hitting buttons during calls this whole time... Still an acceptable compromise as far as I'm concerned.
I had to manually input my provider's APN settings and toggle mobile data from off to on in order to get mobile data access, but that's the expected behavior. I had to do the same setup on the stock ROM. Haven't dropped the network once yet, and no issues with performance.
Click to expand...
Click to collapse
The proximity is annoying, but still it's better than all that bloatware
thunderweasel said:
Really appreciate you making this step-by-step noob-friendly guide. Worked for me exactly as advertised.
I had actually tried to flash TWRP and a custom ROM a few months ago after piecing together the necessary information from a few different threads scattered throughout the forum, but for some reason I couldn't get the Alcatel Flasher to properly read my phone's GPT. I spent hours trying different USB ports, different drivers, nothing. This time it worked flawlessly on the first try :victory: Maybe a Windows update between then and now fixed something.
It is so unbelievably nice to have a clean ROM for this phone after all this time. I've been doing my best to mitigate the malware stuffed onto it by Alcatel with the last few system updates and had finally reached the end of my tether. It's like a completely different device and plenty stable enough for a daily driver.
*edit* I think it would be nice if this thread was stickied since it consolidates all of the necessary information into an easy guide for novices.
Click to expand...
Click to collapse
Thanks, means a lot . I'm really glad to have gotten rid of the Alcatel software aswell!
One last thing
PN04 said:
Thanks, this is helpful to know. The compass/rotation/gyro sensors are something I use fairly often for various apps, and is one of the reasons I haven't outright just bought a new phone (because It's been hard finding phones that have both and are reliable)... oddly enough this was one of the issues with the last phone I had where the custom rom, installed by the seller, disabled the compass sensor. At this point I'd be happy just going back to the stock version of the rom, but it seems like there are more difficulties in doing that.
Supposedly once you root the phone you can use another to delete (rather than just debloat) the offending apps causing all the trouble. Maybe if this can get me to that point I might be able to just delete them and continue using the phone normally?
Click to expand...
Click to collapse
If you already did it or not sorry for getting back late. The proximity sensor doesn't actually work, it's not the hardware just the software. Also when enabling video mode inside the camera made the app crash and made the app not open after that (even restarting the phone wouldn't fix it). But after installing it a second time it all worked.
Dubstepwolf123 said:
If you already did it or not sorry for getting back late. The proximity sensor doesn't actually work, it's not the hardware just the software. Also when enabling video mode inside the camera made the app crash and made the app not open after that (even restarting the phone wouldn't fix it). But after installing it a second time it all worked.
Click to expand...
Click to collapse
Yeah so far that one crash was the only one I experienced on the camera app, using the shortcut of double clicking the power button fixed the issue for me. I'm learning to live without the proximity sensor but I'm still finding that I have to soft reboot my phone occasionally to get mobile data to work after leaving the wifi of my house. Also, another random quirk where the audio failed once, not sure what cased that, maybe putting it to sleep while running a game? I had to do a full reboot to get that back.
Related
ok basically i bought the phone second hand with lite'ning 1.4 on it and the wifi worked perfectly ok all the time. Since it was very old i updated it to 6.1. ever since then I have had issues with the wifi. it will connect perfectly fine to the router but i have no connectivity from it, nothing will get any net access at all. This is also not 100% of the time, its MOST of the time but not all, i do have moments where it does work fine. very very odd.
I have since tried updating the kernel to ninpho 2.1.3 from the 2.0.5 that comes with lite'ning 6.1, but that made no difference.
Someone suggested i try a wifi fix app from the market so i downloaded "FXR wifi fix and rescue" and ran that. It ran ok, wiped all my wifi settings and i restarted, but it has not solved the problem at all.
i find it very very odd since if it was a problem with the kernel OR the rom then everyone would surely have exactly the same problem. I know some people report wifi issues but most dont seem to.
anyone have any other ideas?
The odd thing is that it worked before the update. That means that it will most likely be software related.
You could try flashing something totally different like MIUI or CM. They provide kernels too, so this might resolve it, if your kernel and rom don't "like each other". This usually shouldn't happen, but updates breaking wifi shouldn't too. So it might be worth a try.
Sent from my GT-I9100 using XDA App
if i went to something completely different i assume i would have to factory reset the phone to wipe it first? (or factory reset it AFTER installing the new rom?)
was trying to avoid wiping it as i dont want to spend endless hours setting up everything again. i have backed it up with the free titanium but id still like to not have to find out whether the restore actually puts everything back properly
its very odd as its not completely broken, sometimes it does actually work, and it always connects to the router itself without any problem.
Probably wrong modem for you, flash another one. You can find modems in the developement section.
ok thanks I will have a look at that. It is currently on XXKH3 which is what came with lite'ning 6.1. i am confused though, all SGS2 hardware is identical so if this modem in 6.1 is causing this issue, wouldnt it affect every sgs2 that uses that modem?
I found the "shipped modem collection" post in the original development thread so have asked in there which modem i should try.
ok apparently i should try XXKI3. for o2 UK provider.
although i have now read that wifi is not managed by modem but by kernel only. if this is true then modem will not help me
Well, if the wifi is not managed by the modem, try what I proposed you earlier. The simplest would be to flash CM. Make a backup of your current rom, then do a full wipe and install CM.
As for your data:
1. Titanium backup restores your apps with their data (if you wish). That means that, for example, your games will keep their saves, other apps their settings and so on.
2. Assuming that you have a google-account, you don't have to worry about your contacts, calender,... Just sync it before you flash.
3. The backup you make in CWM will backup everything in case CM doesn't work for you.
In case it does work and you'll want to keep it, the other two other parts of your backup will minimize the remaining work. Note that you shouldn't restore "standard"-apps like the media-player or the SMS-app if titanium backup tells you that the app is not currently installed on your fresh CM. This means that CM uses it's own media player or SMS app. It could lead into problems to mix TouchWiz apps with CM.
A side-note:
Don't use the "stable" version. It had more bugs than expected and they made it a RC again. However, it is still in the stable folder. Get the latest nightly.
Sent from my GT-I9100 using XDA App
yep i think it is kernel. just noticed that 1.4 had cf-root, 6.1 had ninph 2.0.5 and i then tried ninph 2.1.3 and both ninph's have had the issue. i just tried speedmod k2-13 as i already had that downloaded and so far the wifi has been ok so hopefully thats it fixed. i guess it was something to do with ninph (i am thinking that because i have it set to sleep the wifi when the screen is off that somehow ninph is not handling this properly).
possibly one good thing to come of it all, ive updated the modem to KI3 which is supposedly the best one for o2 UK so i may even save more battery and speedmod is meant to be really good for battery too. I still have lite'ning on it at the moment.
i might have a look at CM anyway but i do kinda like lite'ning (although i havent actually used anything else since the phone came with it!)
also need to look at wakelocks to see if i can save some more, although not sure how i go about 'fixing' them at the moment
The choice between CM, MIUI and the stock mods is the choice between three different UI's.
I've had all three of them for some time. As you got CWM, you can just create a backup and do a sightseeing tour through the world of custom roms. Believe me, it's absolutely worth it. To get an idea of the main differences, I've written a short overview for you:
Stock mods use Samsung's TouchWiz. The default user interface that you get when buying a Samsung Android phone. So it mostly looks and "feels" the same and you can't do much about it.
CyanogenMod gives you the pure Android user interface. It's the closest to the Nexus phones by google, but gives you some extras. It is much more customizable than stock roms. It's sleek and fast.
MIUI is a whole different story. They're "Redefining Android". I think calling MIUI an "Android custom rom" is an understatement. It's an entire OS. The result of putting the best from iOS and Android into one powerful OS. It adds tons of useful(!) features. If you've ever used Windows Phone 7 or an iPhone, you know what a big step forwards Android is when it comes to features. Switching from Android to MIUI is just like that. There is just so much more. It is BY FAR the most customizable Android you can get.
Wow. If I look at how long the texts are, I see that I'm pretty biased. :O
Well maybe because I've switched so often between them. The stock roms had no chance, because after I used one of the others I found out that TouchWiz doesn't cut it anymore. I hate how "iPhone-ish" MIUI is, but if I flash CyanogenMod I just miss so much. Giving you a list of what MIUI adds would be another long post of this length.
Sent from my GT-I9100 using XDA App
cool thanks will have a look at MIUI at some point.
spoke too soon earlier, the wifi is maybe slightly better on this speedmod kernel BUT when i wake the phone from sleep, it takes about 30 seconds before i can connect to the net with anything. the phone connects to the wifi straight away, but i have no connectivity for a good 30 seconds and then it starts working. (its not the router, i am getting a connection and an IP pretty much as soon as i wake the phone). also the 30 seconds or so only STARTS once i try to connect to something. if i wake the phone and do something that does not want net access for a few mins and THEN try to get on the net via wifi (which shows as connected the entire time) then again i have to wait about 30 seconds from when it first tries to connect before it will start working.
ok slightly confused again.
I have lite'ning 6.1, speedmod k2-13 kernel and XXKI3 modem. I am trying to get cwm installed so i can make a full backup image of the entire phone while i try to sort out the wifi issues. i downloaded rom manager from market, and selected the firstion option in the app 'flash clockworkmod recovery'. it brings up a menu saying 'confirm phone model' with AT&T galaxy S2, a coulpe of i9000s and a plain "Samsung Galaxy S2" which is the one i selected. it downloads something and says successfully downloaded clockwork mod recovery.
i then choose reboot into recovery. when rebooting it attemps to install something but then says "failed to verify whole-file signature" and aborts. so im just stuck with the standard recovery instead.
so now im confused, have i missed something?
Ehhhhm, you don't need to do it.
Have a look at the features of the speed-mod-kernel:
Current features:
Root and CWM:
- Automatically installs root (su)
- CWM 4.0.1.5 recovery
It already installs it right away.
Just in case you messed something up. You should flash the kernel again.
Besides that you don't need the RomManager at all. Just shut your phone down and boot into the recovery with the key-combo. Create and restore backups from there.
Sent from my GT-I9100 using XDA App
I have created this thread to clean up the forums a bit and to fix one confusion that most people in the forums which are saying which can mislead people to think that user means that when they don't mean that.
Q: What is the different between brick and soft-brick?
A: This is the issue I was talking about above.
A soft-brick is where you cannot access the kernel or/and rom and a brick is where you cannot access the bootloader so you cannot turn on your device unless you JTag it.
Q: Since I flashed a kernel I got stuck on the splash screen (Google logo bootloader screen), I attempted to reflash but it did not help.
A: Make sure the kernel is supported by the Rom's build number and Android version, to fix this you have to flash a supported kernel, remember that not all kernels are supported.
Q: Since I upgraded to Android 4.3 via OTA I noticed a large battery drain, WHAT IS GOING ON?!?!
A: On day 1 after the upgrade Google Backup will be using your battery for restoring your data so you will have to wait until it is done BUT then it will backup your settings such has brightness and app data but you can switch off "App Data" from the sync settings to stop Google Backup.
Q: A while/day later the issue is gone but Google Services is draining my battery.
A: That is actually Google Maps doing the draining, it is using the internet to locate you, to stop the battery drain go to Settings, Location settings, and disable WiFi & Mobile network location.
Q: Titanium Backup is not restoring my backups, what can I do?
A: Flash SuperSU v1.51 via recovery, this will fix the root issues and the Titanium Backup restore issues.
Q: Root is not working on Android 4.3, I'm panicking!!!!!!!!!!!!
A: Don't worry, flash SuperSU v1.51 has mentioned above to fix root since it now uses the SU Deamon due to the new security.
Q: The stock recovery says "No command.", what can I do?
A: Either keep pressing or hold volume up and power to unlock the menu.
This does not always work for certain users so I would try volume down and power so see if that does anything.
Q: How do I disable the OTA updater?
A: You will need root and an application, thanks to @joshuab227 for the information, the following is from joshuab227's post:
Here's how to disable the auto OTA download on any ROM
Install Autorun Manager from the Play store.
Then enter its recommended advanced mode.
Go into the settings and enable the following : system entries and system app disable.
Disable com.android.gsf.update.SystemUpdateService$Reciever under Google Service Framework
Click to expand...
Click to collapse
Q: The Play Store app and web store will not recognise my device!
A: @ColdEmbrace has got this issue and found the solution so that should explain why the start of the post starts how it starts:
After trying all of the above options my device was still not showing in the store. I went to this link.
play.google.com/settings
I clicked on one of my devices and clicked the update option this loaded my Nexus 4 onto the list it is now available on the web store.
Thanks everyone for the advice and I hope this helps people who are still having issues.
Click to expand...
Click to collapse
Q: My device says that I have no internet connection with a empty signal bar with or without a sim card.
A: The user @matt0401 was one of the victims with this issue and managed to fix this issue with a interesting solution:
Wow, I'm up and running! Weird fix though...
I installed the toolkit and downloaded the ROM, and was attempting to get into fast boot manually because trying to do it during the unlocking process in the toolkit wouldn't work. I thought I remembered the buttons for getting into fast boot from my old Gnex as being "hold power and volume up at same time". I tried this, and the phone went to the white "Google" logo and then vibrated, and then screen went black and the LED notifier at the bottom of the phone glowed red for about 2 seconds. The phone then rebooted, about 10x faster than before might I add, and when I was booted up I saw "No SIM detected... emergency calls only". This would infer my SIM slot was finally being detected, whereas before even with no SIM inserted I just got "No Internet Connection".
I popped my SIM in, rebooted, and the network is connected. Time to review 5 days of missed texts. Thanks for the hand!
tl;dr --> Anybody having this problem, try turning it off, and then turning it back on with the SIM inserted, holding POWER + VOL UP til it does this hard reset type fucntion. When rebooted, the problem should be resolved.
Click to expand...
Click to collapse
Q: I have to reenter my pin code for my sim every time, what do I do?
A: @lucker#1 you guessed it has the same issue has well but he wasn't the OP of the thread that the issue was discussed in but he did sure find a fix, the following is a quote from his post:
i've also had that issue the second day after receiving the phone. I removed the sim, put it back in but that didn't help - i looked at my sim card tray and i realized that a one side of the sim card chip was close to one metal side of the tray and i figured that could be the issue - so what i did is i took a stripe of adhesive tape and made sure they wouldn't touch - I haven't had the issue again and it's been more than 2 weeks.
Click to expand...
Click to collapse
Q: Since I installed Android 4.3 a few of my apps are force closing, what should I do?
A: You have to reinstall that application to fix the issue.
Q: I am getting screen flickering.
A: Flash the correct kernel which supports your Android build and version.
Q: Got a kernel panic, HALP!!!
A: That is pretty rare for the kernel to panic but you can actually easily trigger it, to fix it you must reflash the kernel (make sure it is the correct one!).
Q: Since Android 4.3 on YouTube using Slimport there is a blue graphical glitch, why is it doing that and how to fix it?
A: Since Android 4.3 there is some major bugs, improvements and fixes and the graphical glitch (I got this myself) is due to the new Software Encoder, there is no fix yet but you can go around it by using VPlayer as it apparently supports YouTube videos and it has Hardware Encoding.
If you have any questions and answers please post them here.
Bump!, Not much people are reading this...
Sent from my Nexus 4 using xda app-developers app
Bump once again and the last time.
Sent from my Nexus 4 using Tapatalk 4
Hi - I'm very new to the forum and less new to custom ROMs and software.
In the last few days I installed solk2's unofficial CyanogenMod port, 20140711 root build. Went well; overjoyed to be rid of Samsung's bloatware. Thanks!
Since then, updated to first 20140808 and now 20140813. Used CWM recovery (installed via theunlockr dot com/2013/12/09/install-custom-recovery-samsung-galaxy-s4-gt-i9506shv-e330s/) directly instead of CM Updater - updater downloads the builds but when it reboots into recovery to apply them the process there cannot find the build file to install.
I've noticed:
1) When making / receiving calls, the face sensor doesn't appear to work any more - before CM, the sensor would notice when the phone is held to my cheek and blank the display, and light it up when I move the phone away. No longer.
2) The front start button doesn't appear to wake up the device from sleep any more (maybe I've missed a setting to toggle for that?)
3) the CM updater doesn't appear to work, as mentioned above
4) CyanDelta doesn't know about this set of nightlies I think - I've tried it a couple of times and it doesn't pick up deltas
5) the power button doesn't wake the device when it has darkened due to being on a call; instead it may cause the device to flash its screen up but then immediately darken again
1 & 5 make it quite difficult to control the phone during calls. Initially I thought this might have to do with ShakeCall, but the issues persist after uninstalling that.
I've cleared my cache and dalvik cache after the most recent flash to 0813.
I should say, this is relating to http://forum.xda-developers.com/showthread.php?t=2767448 and I'd have posted there but I cannot yet.
This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?
Is this the right place to ask, even? Does @solk2 work?
pfm102 said:
This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?
Click to expand...
Click to collapse
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.
solk2 said:
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.
Click to expand...
Click to collapse
Thank you very much - I'm running 20140914 and the proximity sensor now works during calls.
Hi,
in my spare free time I compiled a new unofficial LineageOS 14.1 ROM on my beloved Phenom II system with ECC RAM and made it available to you for 90 days from
https://www.filefactory.com/file/5fqmz223n9gx/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip
https://www.filefactory.com/file/121p40o8v8gb/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip.md5sum
The ROM can be installed through a recovery like TWRP. I also applied some modifications, in particular:
- the SonyLOS kernel has been replaced with the Sony AOSP version which seemed to be more up to date
- using some 7.1 binaries of Sony AOSP instead of the 7.0 binaries used earlier enabling some more features (?)
- replaced the LineageOS camera with the Simple Camera app
- integrated Total Commander, Apollo music player v2, SELinux permission changer and Viper4Android apps since I need them
Consequently,
- patchlevel now is March 5th, 2017
- the fingerprint sensor now seems to be usable to unlock your device
- the FM radio works (however, you have to manually scan through the stations once because automatically finding the stations initially still does not seem to work completely)
- the selfie camera image no longer will be upside down (seemed to be an issue with the LineageOS camera app, also will work correctly with i.e. Focal if you prefer a sophisticated app instead of Simple Camera)
- I can now use Apollo again as I did on the Z1 compact with CM 12
- the bass boost and equalizer are back with Viper, you just need to invoke the SELinux changer on the rooted device and install the drivers initially through Viper itself
Thanks fly out to Sony AOSP, SonyLOS and the app providers. Feedback is also very welcome.
Regards,
jtk_de
@admin: Could we please move this thread and my previous one to the ROM section ? I'm still not allowed to post something there
Great to see you're still updating your ROM. Don't understand why you upload at filefactory (sloooow download) instead of androidfilehost for example. Will flash your ROM tomorrow.
- should I flash a stock ROM first or does it not matter which version I'm coming from
- what do I need the .md5sum file for?
- gapps are not included, right?
I tried to use androidfilehost but my uploads got interrupted so I had to stick with filefactory for now. You don't need to flash the stock ROM first, just wipe the system, cache etc. partitions in your recovery and flash the .zip.
The md5sum checksum file is there to ensure the ROM integrity and is not needed for the flash, however, TWRP optionally can read it and veryify that the ROM has been correctly downloaded and copied to your phone's storage. Gapps is not included since I use alternative apps, hence it must be installed separately.
Root access is integrated already and can be controlled via the developer settings. The only issue I experienced so far is that the volume cannot be altered yet during phone calls
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Micka84 said:
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Click to expand...
Click to collapse
You need to enable root first and start the SELinuxModeChanger installed with the ROM and set SELinux to "Permissive". Then the Viper drivers can be installed which can take quite long (a minute or so). If an Android dialog pops up because of this confirm that you would like to wait longer. Then reboot as indicated and enjoy the bass
That worked for me thank you
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
dreadavi said:
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
Click to expand...
Click to collapse
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
lba810701 said:
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
Click to expand...
Click to collapse
Thanks for the hint. Did what you said, but i cant mount system in recovery. It cant be selected in the list. Any other suggestions? Ok solved it. had to flash stock rom and boot.img before the steps you asked me to try. Thank you!
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
avion540 said:
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
Click to expand...
Click to collapse
1. Yes, the volume can't be changed during phonecalls
2. Didn't notice any echos so far
3. True
Could you try uploading to mega.nz? FileFactory is so slow
minimum Brightness
Hey!
i was just wondering if its possible to lower the minimal brightness a bit more. because minimal brightness is quite bright still. Im using this ROM for a few days now. Everything works pretty fine, but the battery life is a bit short for what i was expecting. If i dont use extreme battery saving mode its always around 24 hours. i barely do phone calls and i use it not very intensively... Highest Consumer is standby with 5%, which i think is wierd, isn´t it?
:good: Kudos. Everything seems to work well aside from the Bluetooth Audio cutting out after a few minutes. Overall I am really happy with it - happy enough that it's my daily driver.
Hi!
ROM will be better and better. Thanks.
Battery charging speed a bit slow, and if I'm using a mobil net, it's draining a little fast, plus in the evening, with wifi on, it goes down nearly 5%>. Camera is good. But, im using open cam software from google play. Fingerprint sensor working good, just a little hard to configure it. I'm using substratum theme engine, and i can theme most of the base and google apps. ( Except fingerprint sensor, with themed settings, the fingerprint setup screen cracked... but inthinknits theme problem ) And about bluethooth.. yes, it's dropping the connection after a few secs. But, if you left it, then reconnect automatically and just after that, it goes good. Until you turn it off. I used a sony sbh70 wireless headset with power amp.
And echo sound in calling. I can't hear echo, but other peoples in line, they sad it. They hear onselfs twice.. :/
If you would like it, maybe i can upload a logfile ( with matlog ) about the bluethooth problem.
Anyway, thanks foe thiese rom for our x compact.
It's good to see some other people are using the ROM and testing things that I can't test
According to my own experience battery lifetime is around 2-3 days when surfing via wi-fi, listening to music and calling from time to time. Battery charging with the Sony AC adapter coming with the phone is quite quick compared to the Z1C although the battery capacity is higher.
If I make another build I'll upload it to some faster provider though.
hello all,
give it some news there? Last entry April 2017.....
Hi all, are there some updates? I love Lineage OS
I'm wondering why there isn't an official build for the Xperia X Compact yet ? If I google "kugo lineageos" I get a hit for a stats page:
https://stats.lineageos.org/model/kugo
Which just says the page isn't rendered yet, but obviously someone has been devoting his/her time to the kugo. What could be the hold up? Same goes for the lack of other roms btw. It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
harryharryharry said:
It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
Click to expand...
Click to collapse
Sony gives us a sliver of what is needed for AOSP to run, camera, bluetooth, wifi, and radio band stuff all has to be manually made to work. The z3 line was the ONLY xperia line to ever get mainstream AOSP support from devs. If you bought your xperia thinking Sony's AOSP program was good you were sadly mistaken.
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Unroot, lock and take it back for repairs? Sorry, not very XDA-style answer.
Edit: are you completely sure that you flashed the right stock ROM for your device?
Try again
Alvaro Luna said:
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Click to expand...
Click to collapse
I have a Retla and received official 9.0. download the 89-2 stock firmware. You can find it here. Use the .bat
File, place inside extracted firmware click & when it restarts you should get a notification to download 89-5.. once it completes the next notification will appear.. that's 116-11 9.0..
mod edit - telegram chat spam removed