Hi friends, well basically the problem is I got a friends y GT-I9500 and it bootloops over and over with any ROM other than South Africa Rom 4.2.2 and has invalid baseband. It's a cell from a friend of mine I never new which rom was installed on this phone and as soon as I got it I installed the official stock rom from my country which was KIT KAT rom 4.4.2 tried unbranded ARO version first through ODIN, everything went fine, but it got stuck on bootloop.
These were the things I tried.
- stock recovery (I9500UBUGNG1_I9500UUBGNG1_ARO) --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Installed another Stock rom KIT KAT from corresponding Carrier (I9500UBUFNC1_I9500TFGFNC1_UFN) , did :
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Downloaded previous builds of stock rom going back to 4.2.2 , installed stock version of 4.2.2 ARO unbranded (I9500UBUBMG1_I9500TFGBMG1_UFN)
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
I also tried installed some custom roms , having flashed Philz recovery and installed from there onwards, no luck as well.
So I came across some threads which said the only possible way of downgrading if I had installed 4.4.2 kit kat , was using a South African ROM 4.2.2. So I tried it and to my surprise the phone booted fine without any problems. Honestly I don't remember if I did flash it with the PIT file and re-partition. But I did work . The only problem once inside the OS itself it showed invalid baseband. I suppose this was due to the EFS partition being changed intially by KIT KAT.
So I'm hoping someone might help me out as to know what else to try, because honestly I'm out of all ideas.
Thanks !
When you went into download mode, what was the product name the phone reported?
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
mmm I have to check, what do yo uwant me to see what string? I can put it on downlaod mode again.. and get you a screenshot
Screenshot is fine as it will give me what I need to know.
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
screenshot attached , please check
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Strephon Alkhalikoi said:
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Click to expand...
Click to collapse
Ok , thanks for such a complete explanation. It's always nice when someone with knowledge takes the time to go detail by detail explaining everything. This is the way things have to be done, and explained. Ok so let me get things straight
- Wanams Efs backup , I need to install within a working ROM right? It's not through Philz recovery, What should I backup with EFS backup only EFS?. Something I forgot to tell you was I did change some permissions to see if the invalid baseband got fixed, I changed some owner permissions on the EFS folder, you should know about this.
-Then you want me to install latest ROM should that be KIT KAT right?. Unbranded for my region. Yes I know about the PIT file to repartition, I've already done this and still bootlooped with all the rom variants I tried. The only possible way the phone boots and succeeds is with South African ROM 4.2.2 I've tried all previous roms even choosin the apropiate PIT and still bootlooped.
-The only thing I'm left thinking is all these bootloops have something to do with the modem file, which the South African rom 4.2.2 might have a different modem. Which modem should I install I've read the G versions onwards modified the EFS partition.
- Last, how would EFS backup fix the EFS partition if it's only backing it up, Cause i'm thinking as I've initially when I received the phone installed KIT KAT. IT changed the whole partition scheme of efs.
So now that I've gone through every point, can you clear again the steps sorry if I'm so tedious on reviewing again but I needed to clarify bit by bit.
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Strephon Alkhalikoi said:
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Click to expand...
Click to collapse
Hey so many thanks, honestly I don't know what have been wrong with the device. I'm suspeting this has to do with the modem. Could the modem version on the South africa rom be causing the ROM to install fine. But think of this me first installing KIT KAT and have screwed up the efs and as a consequence the IMEI. My only way would be to install kit kat succesfully as the EFS might have changed. Any advices on this?
The modem isn't likely to cause a bootloop. At worst, it's likely to render the cellular and WiFi services unusable until it's flashed again. Screwing the EFS up is where I believe your problems lie. The EFS partition may well be corrupted, which could cause your bootloop. I really think the only way you'll resolve this is by having someone at Samsung take a look at it. You've repeatedly installed ROMs and have had no luck, so installing a ROM again isn't going to help you here.
Please help me,
How to root freetel kiwami samurai and custom rom for it!
It is use android 6.0 not good
Any updates?
Kingo and kingroot work, but no custom roms. No twrp or any recovery for it either.
Would like to know if anyone has any ideas or news on this.
I'm looking at one of these on ebay right now, leaning towards buying it. I'd almost certainly buy it if I knew there were custom ROMs available.
For the price, definitely an amazing phone. It really sucks that there is nearly zero support for it anywhere.
For $120 I decided to grab it to replace my constant headache with our note 4 here.
The main camera, very, very nice.
The speed seems alright. The feel, the build is great.
The battery seems to drain kinda quick, but that might be my imagination.
I'm comparing it to our Y6Max and phab2 plus.
I used Kingo root on it initially, then went to and currently have kingroot on it. Kingo had annoying floating ads.. Kingroot seems decent but I'm suspecting that it has something to do with the battery drain.
Worst part for me at the moment, trying to work around not having twrp+xposed on it.
(the nav/status bar is taking up too much of the nice 6" screen)
If anyone has any way of getting twrp or something similar on it.... Please let me know - help us all out.
After some fighting with Kingo and kingroot, back and forth, I managed to get supersu to take over, install binaries and update... Now no more Kingo or kingroot. Tempted to try installing xposed, but I'll wait for now.
Found a command to enter in terminal to use full immersive mode all the time...
Adjusted dpi as well
Now the phone is looking nice.
Just gotta wait and wish for someone kind enough to help out with getting a custom recovery on these phones.
Really loving this phone
Stock rom for freetel kiwami FTJ152D
Hi all, I need stock rom or worked rom for my freetel kiwami FTJ152D.
Can someone upload this or what is the link to download this ?
I bricked my phone after flashing custum rom MM6.0 published on needrom. No touchscreen, very bad display, no imei, no root.
Please, help me.
meteor37 said:
Please help me,
How to root freetel kiwami samurai and custom rom for it!
It is use android 6.0 not good
Click to expand...
Click to collapse
Hi, I used kingoroot online and mine was rooted. (Freetel samurai kuwami FTJ152D stock rom 5.1)
But now, I have a big issues, I flashed it with a MM6.0 publshed on needrom and now there's no touchscreen, screen display very bad, no imei (impossible to put imei and root with few known method) and no root.
Could you please upload your worked rom ? Stock rom or custum but work fine.
Or where can I find link to download it ?
Please help me.
Myloverboy said:
Hi, I used kingoroot online and mine was rooted. (Freetel samurai kuwami FTJ152D stock rom 5.1)
But now, I have a big issues, I flashed it with a MM6.0 publshed on needrom and now there's no touchscreen, screen display very bad, no imei (impossible to put imei and root with few known method) and no root.
Could you please upload your worked rom ? Stock rom or custum but work fine.
Or where can I find link to download it ?
Please help me.
Click to expand...
Click to collapse
Seems like the rom on needrom was for a slightly different phone. However the phone is so cheap now its almost disposable ($100)
I have been able to get recovery but it is in microscopic Japanese Kanji, showing off the high resolution of the screen, but I can't read Japanese.
That is actually a diagnostic menu in chinese you went into (Google Translate FTW lol). For the stock rom recovery, you can turn the phone off, hold volume up button and plug in the usb cable that is connected to a computer. You can also hold volume up and power and let go of power as soon as freetel logo comes on. You will enter stock recovery that is in english but it is useless because you cannot use stock recovery to undo what you have done to your phone since there is no place online you can find a stock rom of this phone model (I have searched for many many hours online).
I am working on getting stock rom dump off my phone using sp flash tool but biggest headache for me has been the scatter file so far. Without it, I can't use the 'read back' option to extract an image dump of working stock rom. Only scatter file i found is from extracting the needrom MM 6.0 which is for the samurai FTJ152D.
I am unable to make a scatter file using MTK Droid tools since MTK Droid tools do not work for 64-bit mtk processors like the one in Kiwami. Scatter files are CPU specific but they are further modified based on the model of the phone and the android version of the rom, so the scatter file from MM 6.0 for FTJ152D is very close to what we need for FTU152D but even a slight variation will result in a rom dump that will not work. If any of you are willing to try, I can use the scatter file from MM 6.0 (FTJ152D) on my phone that is FTU152D to extract a rom dump, but keep in mind that this will probably not work and might make matters worse for your phone. Scatter files are sort of like 'Table of Contents', and if the page numbers are wrong you end up reading wrong chapter... (you get the idea).
I haven't found any other way of making a scatter file. If anyone knows how to get a scatter file from a phone running 64-bit processor such as MT6795, please help us out. Thanks.
Just an update, while trying to make a 'read back' dump using sp flash tool, I accidentally started a download of the FTJ152D MM firmware I was using the scatter file from... Needless to say now I have the demo version of marshmallow and have lost my IMEI info from phone. I did make a 'read back' dump of the phone before i messed up, using the guide from syserr about "Dump Full Rom" at
https://forum.xda-developers.com/showthread.php?t=2540400.
NOTE: If you are still on stock rom that the phone shipped with, DO NOT try upgrade using SP flash tool, at the very least you will loose IMEI information for both sim slots. For me, the phone connects with sim but I can only get 2g data speeds and make phone calls.
I am hoping that the following information can help others:
1) Most Important: If you root, do not use SUPERSU 2.79 or above versions or phone will be stuck in bootloader. Even if you make a backup of boot.img, sideloading it from ADB did not work for me, it kept failing. I am not sure if earlier SuperSU versions work or not, if they do work, make sure you disable auto update for SuperSU in Google Play Store.
2) Even if you make a backup of nvram.bin using sp flashtool, it will NOT restore your imei information in the phone because from what I researched so far, this information is populated using the BPLG and AP databases that are included with the stock firmware as separate files and quite possibly with 64-bit mtk processors, this information is protected and encrypted. Other possibility is that the nvram.bin i recovered from my whole rom dump is for lollipop and since phone is running on marshmallow, this bin file is invalid? I did try flashing two different nvram.bin (one i recovered from the stock dump i made when phone worked, another i downloaded from internet) using flashtool and it made the matters worse, all baseband info disappeared and both sim slots just totally greyed out in settings. If it greys out for you, just format the whole flash and flash the MM firmware again without any nvram partition. Just leave default settings for nvram in scatter file alone.
3) Currently, there is no way to root this phone when on marshmallow. Do not try the chinese one-click or other software such as miracle box, all the ones i downloaded and/or tried or not tried, were flagged by Anti-Virus as trojans and viruses.
4) Be very careful when trying to flash software on this phone, make sure you use the correct Preloader.bin file. The marshmallow firmware on needrom website has a preloader.bin file in it and it works fine. Do not attempt to try preloader from other similar phones or you will brick this phone permanently.
5) ADB and Fastboot commands do not help because the phone is not rooted anymore once you upgrade to marshmallow using the FTJ152D marshmallow firmware from needrom.
6) I have tried combinations of boot.img, and system.img from Priori 3 (it is also dual sim and rom on needrom website is android 5.1), was hoping for a miracle but no luck.
7) MTK Droid Tools works partially with this phone. Most options in the tool require root or do not work with mt67xx processors. I found mtk droid tools useful to enter recovery directly when usb debugging was enabled or to go to ADB terminal to try sideload or reboot bootloader to enter fastboot.
8) Even if you enable oem unlock in developers, the option (volume+up) in Fastboot menu to unlock the bootloader doesn't work. It seems that many MTK processors have this option disabled by the manufacturer.
9) TWRP custom recovery will not work with this phone because the 'boot script' (not bootloader) before actual recovery in the recovery partition has the touch disabled. I was able to get CWM to work by directly flashing it instead of stock recovery but installation of any zip files through recovery fail still.
10) I can confirm that the scatter file in marshmallow rom for FTJ152D available at needrom website has the right entries and address locations for our phone (FTU152D) because I was able to use that scatter file and a Hex Editor program (search for HxD on download.cnet.com) to carve out almost all the partitions from the 2gig partial rom dump I had of my phone in working state. When carving partitions from the dump, some trimming for certain folders is required because cutting the partition by size and making it a .bin or .image file will give errors in SP Flash Tool otherwise. The marshmallow rom or a Priori 3 lollipop rom, both can be used as a reference when cutting out the extra bytes.
If you are like me and have upgraded to marshmallow using the FTJ152D software, there are not many options. I haven't given up yet though, I backtracked my steps trying to make a backup of the phone in its current state using SP Flash Tool full rom dump and it was successful. If I could get my hands on full rom dump of 5 gigabytes of a working phone with lollipop software, I am confident I can restore my phone back to lollipop. This may not fix the IMEI problem but once the phone is running lollipop, it is possible to root it again using kingroot or towelroot and then use one of the imei repair apps or a program to rebuild nvram folder using the BPLG and AP databases and use root explorer to place it in the phone.
Phew... a long write but hope this helps others, and if anyone can help by sharing any thoughts or uploading their stock rom dump if own same phone (can read syserr's method of using 'read back' in SP flash tool to make one big partition dump for the whole rom instead of making seperate partitions which is a painstaking process.
Finally, some very good news for people like me who are stuck, figured out a way to root and install Xposed both Please give credit to Magisk and Xposed developers listed below.
Root:
Root this phone while it is running the FTJ152D marshmallow stock rom using the Magisk guide here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Follow the "Via Magisk Manager (Only support v14.0+): ... " method to install the magisk manager and the .zip file right through it. It patches the boot and makes a patched boot image that you can transfer to your computer and then rename it to boot.img and replace the original boot.img in the FTJ152D MM rom folder. Then use the SP Flash tool, load the scatter file in the rom folder and the 'Format all + Download' option in download tab (it will give you PMT error if you try to just flash the new boot.img alone). Hit the download button, turn the phone off, and connect it to the computer via usb. Everything else should be straightforward but if any issues, ask here, and I will try help if I can.
Xposed:
There is no touch support to make custom recovery work on this phone yet and the only custom recovery i got to work was an old version of CWM which behaved same like stock recovery and refused to let me flash zip files. The workaround I found that worked was 'Flashify' on Play Store. Now that root is working, flashify seems to work (tried Flashfire too but it just hangs and phone freezes). Follow the steps below:
1) Download and install the latest Xposed Installer Apk from their page.
2) Download the appropriate xposed zip file (SDK23 ARM-64), version 89 worked for me. Use Flashify to flash the zip file. If any issues come up, ask here and I will try help.
Official Xposed post is here:
https://forum.xda-developers.com/showthread.php?t=3034811
This post is also very helpful:
https://forum.xda-developers.com/showpost.php?p=67696847&postcount=2
All credits go to the respective developers for their work, including @topjohnwu, @rovo89, @mGforCe, @SolarWarez, @MaArCiN074 and others. Don't forget to thank them.
I also have been able to replace the demo mode logo with logo that was in the partial stock rom dump and will share it soon.
IMEI issue:
After gaining root and installing Xposed, a number of apps can help to at least temporarily get the IMEI written to the phone, that lasts till factory reset. One issue that people like me who installed the FTJ152D MM rom is that the bands in the phone are now based on the Japan region and almost all the frequencies and bands needed for phone to get 3g and 4g signal are disabled in the phone. From researching about this issue I found out (I may be wrong but that's the only information I could find and the bands that are enabled seem to confirm this), is that the latest mediatek chips come with all 41 bands and the phone manufacturers and operators disable or enable bands based on their regions and preferences, so that this phone, FTU152D is probably the exact same hardware as the FTJ152D and the only difference is the software which disables and enables the bands based on the baseband version of the rom. This is a problem for ppl like me living here in U.S but the enabled bands may be fine elsewhere. There is no way to change the bands as they are greyed out when you go to modem information though 'Phone Information' section (apps like 'Advanced Signal Status' can help access it). It doesn't allow me to select and enable band 4 and 12 as these are greyed out (but these worked before with stock rom, so I know the hardware supports them just the baseband version is wrong now).
Anyone know or can help get the right bands working, or have any hints to point me in the right direction, please post here. Thanks.
I was able to finish dicing up the raw dump to make back a working FTU152D stock rom with good baseband. Here is the link for instructions and download link:
https://forum.xda-developers.com/general/general/kiwami-samurai-ftu152d-stock-lollipop-5-t3750068
I have a question for any and all kiwami samurai owners /users. Is it just me, or does your WiFi seem to cut off regularly? I have been fighting with this from pretty much day one. When I'm using a sim card in the phone, I don't notice anything because the mobile data from the sim is working. But, I have 2 of these samurai phones now, and I bought a blackberry passport for my main phone and now both samurai phones are usually only using WiFi. Funnier thing... They both seem to have WiFi issues at the same time. How I know?... Well, I use an app on all of our phones and devices here - Zello. When the connection is lost, Zello sounds an alarm and lets me know. So if the phones are acting up, we'll hear this all day, disconnecting and reconnecting. I got one more for you, the disconnects seem much worse when I use the phones compared to just having them there sitting around. I even went as far to install many WiFi watching, locking, reconnecting apps to try and force the connection to stay on and alive. They have their work cut out for them seeing as when these phones decide they want to drop the WiFi connection, they will fight these apps to maintain WiFi connection until these apps pretty much give up. I have these as back up phones basically, so it doesn't matter so much but of course, this is extremely annoying and a huge inconvenience at times. Any one else out there experiencing this? The only thing I did do that may have a place in all this... Rooted the phones, and also I removed every google app. I have a note 2, note 4, doogee y6 Max, Lenovo phab 2 plus, tab s and an HTC one m8 that are all the same... Rooted and google removed. Playstore play services all that stuff - gone. Those phones don't act up anywhere close to as bad as these samurai phones. Many times I fight the WiFi off because doze and all that power save crap but these samurai phones are tough to figure out. Anyone have any ideas? I also froze and deleted a bunch of system apps(I know, I know) but that was only after I noticed the WiFi issue on the phone and was trying to see if possibly one of the system apps had anything to do with the WiFi disconnects or any power save features or control. So anyone.... Ideas?
J&G said:
I have a question for any and all kiwami samurai owners /users. Is it just me, or does your WiFi seem to cut off regularly? I have been fighting with this from pretty much day one. When I'm using a sim card in the phone, I don't notice anything because the mobile data from the sim is working. But, I have 2 of these samurai phones now, and I bought a blackberry passport for my main phone and now both samurai phones are usually only using WiFi. Funnier thing... They both seem to have WiFi issues at the same time. How I know?... Well, I use an app on all of our phones and devices here - Zello. When the connection is lost, Zello sounds an alarm and lets me know. So if the phones are acting up, we'll hear this all day, disconnecting and reconnecting. I got one more for you, the disconnects seem much worse when I use the phones compared to just having them there sitting around. I even went as far to install many WiFi watching, locking, reconnecting apps to try and force the connection to stay on and alive. They have their work cut out for them seeing as when these phones decide they want to drop the WiFi connection, they will fight these apps to maintain WiFi connection until these apps pretty much give up. I have these as back up phones basically, so it doesn't matter so much but of course, this is extremely annoying and a huge inconvenience at times. Any one else out there experiencing this? The only thing I did do that may have a place in all this... Rooted the phones, and also I removed every google app. I have a note 2, note 4, doogee y6 Max, Lenovo phab 2 plus, tab s and an HTC one m8 that are all the same... Rooted and google removed. Playstore play services all that stuff - gone. Those phones don't act up anywhere close to as bad as these samurai phones. Many times I fight the WiFi off because doze and all that power save crap but these samurai phones are tough to figure out. Anyone have any ideas? I also froze and deleted a bunch of system apps(I know, I know) but that was only after I noticed the WiFi issue on the phone and was trying to see if possibly one of the system apps had anything to do with the WiFi disconnects or any power save features or control. So anyone.... Ideas?
Click to expand...
Click to collapse
There are a lot of variables that could be causing your WiFi issues. Since it is happening on two identical phones, have you installed Zello on a different phone to notice if it happens on that phone at the same time as well? It is possible that it is your WiFi causing the issue more than the phones themselves. How far from the wireless router are you when this happens? It could be that the radio/antenna range on the Samurai phones is lower than other phones and when WiFi signal is weaker, these phones just disconnect. Also, in WiFi settings if you have changed 'Keep Wi-Fi on during sleep' from 'Always' setting to another setting? Another possibility is that 'Scanning always available' setting, if turned on, and you have uninstalled Google or system app(s) that interact with this setting, it could cause a bug where network is disconnected momentarily (see if this setting is on, turn it off).
How strong, how many bars does your WiFi signal show? Mine shows full bars up to 30 feet from gateway and at least half strength in my bedroom and WiFi is not affected or dropped even at half strength. Are you using 2.4Ghz or 5.0Ghz frequency? Try using 2.4Ghz as 5.0Ghz although faster, has a much lower range and if signal is weaker it does disconnect the phone to save battery life.
You could also check WiFi settings using the *#*#4636#*#* if it shows any issues in there.
Android# said:
There are a lot of variables that could be causing your WiFi issues. Since it is happening on two identical phones, have you installed Zello on a different phone to notice if it happens on that phone at the same time as well? It is possible that it is your WiFi causing the issue more than the phones themselves. How far from the wireless router are you when this happens? It could be that the radio/antenna range on the Samurai phones is lower than other phones and when WiFi signal is weaker, these phones just disconnect. Also, in WiFi settings if you have changed 'Keep Wi-Fi on during sleep' from 'Always' setting to another setting? Another possibility is that 'Scanning always available' setting, if turned on, and you have uninstalled Google or system app(s) that interact with this setting, it could cause a bug where network is disconnected momentarily (see if this setting is on, turn it off).
How strong, how many bars does your WiFi signal show? Mine shows full bars up to 30 feet from gateway and at least half strength in my bedroom and WiFi is not affected or dropped even at half strength. Are you using 2.4Ghz or 5.0Ghz frequency? Try using 2.4Ghz as 5.0Ghz although faster, has a much lower range and if signal is weaker it does disconnect the phone to save battery life.
You could also check WiFi settings using the *#*#4636#*#* if it shows any issues in there.
Click to expand...
Click to collapse
Thanks very much for the help....
so, the other phones( we have many) are mostly all set up the same way, all have zello...and no, they don't have the same issue disconnecting at the same time the freetels do.
The router here probably needs to be replaced but, cant get around to that for now.
a little update to this problem... I didn't want to try installing xposed before, because I didn't have recovery installed...got it done using flashfire. this got me xposed and I did this just for the hell of it since i didn't care so much about the phones since they were just being pains. However, after doing this, i also decided to install Lspeed. I remembered that I checked this app out before and i seen that It had some settings in it for tweaking wifi and Lnet. Not even sure what these would do, I started to mess around in there and toggled a few things on...just to see what would happen. also, i just happened to see something in xposed to download "Wifi regional problem solver". again, not sure what this would do, or if it would do anything, i said lets do it...installed it. and believe it or not, haven't had any issues like before with wifi since. Now, not sure what actually fixed the problem or if the problem is actually fixed or if it just took a break from driving me mad, but yeah...it's actually not a bad phone now.
as for Lspeed....using version 1.4.27(like this more than the latest for some reason) and I set up most things in the app to "balanced". not performance , not for battery. Under LNET Optimizer .... NET buffers : BIG. RIL tweaks enabled. NET TCP tweaks enabled. NET speed+ enabled. wifi scanning ...while i've always had off on all devices for as long as i can remember having androids...here in Lspeed i toggled on and set supplicant scan interval to 15secs and wifi idle ms to 1. left google dns off.
just if anyone wanted to know or cares ....and hey, maybe someone knows what any of that stuff means and might be able to say..hey, none of that would've changed anything so it's worthless....or maybe explain what each means or does and why it might have helped.
thanks again.
Hi all,
Before you jump at me telling me I haven't searched the forum, I DID and I couldn't solve my issue even with these solutions. To get you up to speed on what exactly I did.
Briefing (not very important):
I was doing my own business and I was free, I use my phone daily and it served me well. But I noticed that the last security patch I got was on 2020 and got me thinking. Why not just use custom ROMs to update my phone and get a year or two from my MIX3 (2018). I just recently flushed my brother's phone (Samsung) with a custom ROM and I liked it. I already installed TWRP 3 years ago on my brother's phone and I just had to install a zip file and boom new Android 12 on a 2014 phone.
The problem:
after reading here on the forums, it seemed that it is more complicated to do. I'm up to the challenge, I have done it before and the reward is worth it.
+Unlocking the Bootloader
this was a bit easy other than the connection issues but I got it unlocked eventually. (use the QR code to sign it. it is much easier)
I had an issue where after unlocking the bootloader the phone didn't allow me to install TWRP and do a backup, it immediately went into erasing the entire phone.
+Installing TWRP
I downloaded the files from TWRP website and everything was smooth other than the Mi Recovery popping every time I restart (install Magisk to plant TWRP then remove it if you don't need root)
+The downhill
after restarting, the phone worked fine I installed all the apps and restored everything. Afterward, I noticed that the camera does not work. It gives me an error. I reinstalled TWRP again since it was reverting to its Mi Recovery and I think here was the problem I flashed the recovery.img into the boot partition by mistake (I didn't notice at first) but after going back to the command I saw I made a mistake and reflashed the recovery with recovery.img and installed the Magisk and everything was ok. At the initial start, the SIM and the WIFI are not working.
after several attempts at reinstalling different flashable stock ROMs, I saw that the issue is consistent. I read online that you have five .img files that control the different parts of your phone. I got tired and decided to reflash the stock ROM via the Mi flasher and get it back to stock.
Even after flashing the stock ROM, I'm still having the same issue.
I reflashed the modem.img in the modem and still wifi and sim card are not working
I read that some phones have an A/B partition and my phone does NOT have it.
I'M AT A LOSS I CAN NOT FIX IT. IT'S BEEN 3 DAYS ON THIS AND I CAN NOT FIGURE IT OUT!!
Ok, If anyone was passing by I think I found what was the problem.
First, check if your problem matches mine. Go to Settings and check your IMEI. Or just dial *#06# ,if your phone did not return with a number then you lost your IMEI number.
follow this guide and I hope it helps. this is only for some phones so don't try it, it might break your phone
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com