Related
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
Hello all...
First of all, I'm not very experienced at flashing roms.. HOWEVER, I've flashed several roms across multiple phones over the years and have yet to brick a phone.. so I am fairly familiar with recoveries, etc... But I've run into a "wall" and don't know what to do.... hopefully someone can shine some light to my issue.
My TMobile S5 is currently running Twisted Lollipop (v7?).. but I want to switch now to a CM based rom. I had PREVIOUSLY used a CM based rom (a nightly) dated back from June before I switched to Twisted. My phone is rooted.. and I am using TWRP recovery. However, NOW if I do a full on wipe... and try to flash a rom (so far only the latest nightlies).. it seems to do some partitioning stuff.. and then stops saying COMPLETE... I never get the typical "install" text you see when installing a rom in recovery.. If when it's finished.. when I click REBOOT.. TWRP asks me if I want to.. and warns NO OS is installed..
I was able to load a backup of a CM 12.1 based build from a June nightly I had.... but I get the same thing if I go thru the CM updater. I honestly haven't tried to flash anything else..
Am I missing or overlooking something.. I'm on the DOB1 firmware.
Thanks
aenielida
Guys,
i'm using cm14.1 i want to revert back to miui ....please help
when i tried flash fastboot rom (kenzo_global_images_V7.3.6.0.LHOMIDD_20160523.0000.23_5.1_global_aef179560d) my wifi not worked. then i came back to cm14.1 now everthing work fine but i need miui.....please help
(sorry for bad english)
Same happened to me, I guess because we try downgrade to lollypop which has different radios. First I tried with twrp and with fastboot, but no wifi on 5.1. MM works fine for me... If anyone know how to downgrade to 5.1 I want answer too
redminote3 said:
Same happened to me, I guess because we try downgrade to lollypop which has different radios. First I tried with twrp and with fastboot, but no wifi on 5.1. MM works fine for me... If anyone know how to downgrade to 5.1 I want answer too
Click to expand...
Click to collapse
Bro did miui dev 6.0 fastboot rom work ?
Yeah, wifi and all will work no doubt on 6.0
use xiaomi.eu rom...flash from twrp...everything work properly for me.
site: xiaomi.eu
I use EU ROM currently too and it is the best one for me to date, also freezed some system apps with Titanium Backup.
But still dont know, if theres a way to downgrade to 5.1 if I dont have backup from 5.1, because my Kenzo came to me with 6.0... It boots fine, but wifi dont work, so also other radios, so its not usable
P.S. Can I flash with TWRP(zcx) old EU ROM recovery with 5.1 and radios will work?
I guess ill try that now
redminote3 said:
I use EU ROM currently too and it is the best one for me to date, also freezed some system apps with Titanium Backup.
But still dont know, if theres a way to downgrade to 5.1 if I dont have backup from 5.1, because my Kenzo came to me with 6.0... It boots fine, but wifi dont work, so also other radios, so its not usable
P.S. Can I flash with TWRP(zcx) old EU ROM recovery with 5.1 and radios will work?
I guess ill try that now
Click to expand...
Click to collapse
yes...you can directly flash 5.1 rom from zcx.
backup your data then do factory reset in twrp before flashing LP rom to remove any MM encryption.
hope you can downgrade without any problem..happy flashing.
anyway, probably your bootloader will relocked. but i am not really sure about this, just check it first after flashing LP rom.
abihary said:
use xiaomi.eu rom...flash from twrp...everything work properly for me.
site: xiaomi.eu
Click to expand...
Click to collapse
how to download recovery rom xiaomi.eu ...i didn't get any download button over there
abihary said:
yes...you can directly flash 5.1 rom from zcx.
backup your data then do factory reset in twrp before flashing LP rom to remove any MM encryption.
hope you can downgrade without any problem..happy flashing.
anyway, probably your bootloader will relocked. but i am not really sure about this, just check it first after flashing LP rom.
Click to expand...
Click to collapse
I tried that yesterday, except I wiped all except cust/microsd , flashed 5.1 eu rom and then I flashed also SuperSU, it was a disaster, phone only shows Mi logo and turn off...I cant go to twrp, only to fastboot. Im going to get computer in two hours where I have everything set up And will try to go to EDL mode and then flash With MiFlash... I doubt that flashing 5.1 will work with wifi
Denis:) said:
I tried that yesterday, except I wiped all except cust/microsd , flashed 5.1 eu rom and then I flashed also SuperSU, it was a disaster, phone only shows Mi logo and turn off...I cant go to twrp, only to fastboot. Im going to get computer in two hours where I have everything set up And will try to go to EDL mode and then flash With MiFlash... I doubt that flashing 5.1 will work with wifi
Click to expand...
Click to collapse
from fastboot, are you check your bootloader? it seems your bootloader relocked, thats why you can't pass mi logo
if your bootloader relocked, you can easily unlock it using miunlock.
for wifi, you can easily flash any miui mm firmware from twrp.
Thank you for the tip, didnt thought about that...
im gonna borrow computer now, I have all drivers installed etc on it...
If its only relocked and I will be able to boot and wifi will not work, where can I get firmware (and you must be thinking LP firmware not MM, right?
btw I flashed older EU ROM MIUI7, 5.1 then flashed through zcx supersu and reboot, now Mi logo only flashss and turn off. Only fastboot I can enter.
I will then first check if BL is locked, and unlock it if it is...
thank you for help
Ok so you were right, BL was locked so I unlocked it and got enryption problem after booting up, I had to reflash ZCX TWRP, because EU ROM replaced it with official 3.2.0. So now I am finally booted up on EU rom MIUI 7.3 by xiaomi.eu/Beta, Android 5.1.1, but Wifi as expected dont work, also SIM is not recognised.
What and where to get radios I have to flash to get it working? Because it says unknown under system info about version of radios
Also it says unknown device ID (IMEI,..).
I have backed up all partitions before on MIUI 8 EU,6.0, so do I need to flash those radios or firmware or do I need it from 5.1? And where to get it if so
Nice I got it to work, restored EFS,MODEM,FIRMWARE ROM,FIRMWARE EMMC and wifi works and SIM is working )
Nice I had backup of that...still not sure if all works as needed, gotta test a bit
Denis:) said:
Thank you for the tip, didnt thought about that...
im gonna borrow computer now, I have all drivers installed etc on it...
If its only relocked and I will be able to boot and wifi will not work, where can I get firmware (and you must be thinking LP firmware not MM, right?
btw I flashed older EU ROM MIUI7, 5.1 then flashed through zcx supersu and reboot, now Mi logo only flashss and turn off. Only fastboot I can enter.
I will then first check if BL is locked, and unlock it if it is...
thank you for help
Click to expand...
Click to collapse
for me, it's positive thats your bootloader relocked. unlock it, and you can boot into rom. for firmware, you can download from below
link firmware:
miui LP firmware
miui 6.7.21 firmware
miui 7.3.2.0 firmware
miui MM firmware
miui 6.9.29 firmware
miui 6.10.13 firmware
redminote3 said:
Ok so you were right, BL was locked so I unlocked it and got enryption problem after booting up, I had to reflash ZCX TWRP, because EU ROM replaced it with official 3.2.0. So now I am finally booted up on EU rom MIUI 7.3 by xiaomi.eu/Beta, Android 5.1.1, but Wifi as expected dont work, also SIM is not recognised.
What and where to get radios I have to flash to get it working? Because it says unknown under system info about version of radios
Also it says unknown device ID (IMEI,..).
I have backed up all partitions before on MIUI 8 EU,6.0, so do I need to flash those radios or firmware or do I need it from 5.1? And where to get it if so
Nice I got it to work, restored EFS,MODEM,FIRMWARE ROM,FIRMWARE EMMC and wifi works and SIM is working )
Nice I had backup of that...still not sure if all works as needed, gotta test a bit
Click to expand...
Click to collapse
good, seems your problem already solved. :good:
Yeah, now a problem is I cant access fingerprint or password lock, I think because I cant connect to Mi account, cant find my device, also cant manually log in, because it cannot verify "find device", also cannot access to "Privacy" to install 3d party apps it is a must to enable this... Also settings freeze occasionally. I think I still didnt do something right... Any tip?
Thank you for helping me!
redminote3 said:
Yeah, now a problem is I cant access fingerprint or password lock, I think because I cant connect to Mi account, cant find my device, also cant manually log in, because it cannot verify "find device", also cannot access to "Privacy" to install 3d party apps it is a must to enable this... Also settings freeze occasionally. I think I still didnt do something right... Any tip?
Thank you for helping me!
Click to expand...
Click to collapse
sound like firmware problem, you can try to flash firmware from above link which suitable with your current android version. if you're in LP, flash 6.7.21/7.3.2.0 and see if it work. or, you can flash one of MM firmware above.
to avoid from getting relocked, you can delete emmc_appsboot.mbn from zip package using winrar/7zip without extract it and let the apps repack it again.
abihary said:
sound like firmware problem, you can try to flash firmware from above link which suitable with your current android version. if you're in LP, flash 6.7.21/7.3.2.0 and see if it work. or, you can flash one of MM firmware above.
to avoid from getting relocked, you can delete emmc_appsboot.mbn from zip package using winrar/7zip without extract it and let the apps repack it again.
Click to expand...
Click to collapse
I tried flashing your firmware 7.3.2.0 and had to restore EFS,MODEM(maybe only modem) to get wifi,SIM working also your firmware fixed only I could log in to Mi account and find device, but still couldnt set PIN,FP, also tried calling and couldnt hear anything also on the other side no voice.
Im losing confidence that I can get everything work on 5.1 MIUI7
Then I wiped everything expect microSD and wanted to restore backup I made on EU ROM,MM6, but it said read only. Then I flashed 6.10.13 EU ROM and it works everything perfectly here...
Still want to downgrade to MIUI7,5.1 if theres a way to get it all working, because I heard battery is lil better...
redminote3 said:
I tried flashing your firmware 7.3.2.0 and had to restore EFS,MODEM(maybe only modem) to get wifi,SIM working also your firmware fixed only I could log in to Mi account and find device, but still couldnt set PIN,FP, also tried calling and couldnt hear anything also on the other side no voice.
Im losing confidence that I can get everything work on 5.1 MIUI7
Then I wiped everything expect microSD and wanted to restore backup I made on EU ROM,MM6, but it said read only. Then I flashed 6.10.13 EU ROM and it works everything perfectly here...
Still want to downgrade to MIUI7,5.1 if theres a way to get it all working, because I heard battery is lil better...
Click to expand...
Click to collapse
ah...this is only for battery life?
miui 8 a lot better on battery backup comparing with miui 7. also you got android M with bunch of feature & security update.
if you want better battery, flash xposed & amplify (you can limits nlp wakelock), flash kernel & use darkness/zzmove gov, use adaway or minminguard to remove ads.
still want more? flash stable aosp rom & keep using above way. pure stock android will give you better battery comparing with miui.
Thanks for all this great info!
I used few CM roms for this device, but none of them were working flawless...Which one are you talking about? I tried almost all Nougat based and had a lot of problems, only CM13 from thestrix were the closest, but I like MIUI though... Thank you for your time to help me!
redminote3 said:
Thanks for all this great info!
I used few CM roms for this device, but none of them were working flawless...Which one are you talking about? I tried almost all Nougat based and had a lot of problems, only CM13 from thestrix were the closest, but I like MIUI though... Thank you for your time to help me!
Click to expand...
Click to collapse
give a try for nx rom or aicp, both mm base. i really like both rom stability & feature. almost all my friend using both rom
for N, its still in progress & you won't get stability using N for now. give more time to let dev work & you'll get stable N which better than MM.
you're welcome, enjoy your device & dont bricked it
Thanks man, I flashed NX ROM and its stable and fast so far, also 400MHz unlocked by default ,..Flashed it with pico gapps and kenzo radios.
I want to flash xposed and amplify now, hope xposed doesnt do contra effect.
Thank you again!
Hello
2 days ago i was trying to flash LineageOS 17.1 on my redmi note 3 (kenzo). Here it said i need latest MIUI GS 10.2.1.0 so i flashed it using TWRP, rebooted, then tried to flash LineageOS but i couldn't because i got error 7 "this package is for device kate kenzo this device is ." so i googled it and found a post here by user LeoYL that i need to change lines in META-INF/com/google/android/updater-script and i just deleted those lines since my device for some reason wasnt recognised as neither kenzo nor kate, then i could flash without any problems, then i rebooted again and flashed those gapps. When i rebooted to system, my SIM card was not detected, my IMEI was shown as "unknown" and my WI-FI wasnt working either (i dont know if bluetooth worked, i didnt check since i never really use it anyway).
After that i thought it was some sort of LineageOS problem, so i tried flashing Bliss and Evolution-X but had same problems on those.
Before all of this i was using LineageOS 14.1 for like 3 or 4 years (a long time anyway) and right before flashing MIUI 10.2.1.0 everything was working perfectly fine. I'm also 100% sure my phone is Kenzo since MIFlash won't let me flash any Kate software but Kenzo software is getting flashed with no problems. I tried to fastboot flash MIUI 10.1.1.0 for Kenzo (i couldn't find fastboot flash for 10.2.1.0, so i flashed 10.1.1.0), 10.2.1.0 for Kate, (i deleted lines in flash_all_lock.bat responsible for checking whether device is Kate or Kenzo and then MiFlash let me flash it) but it wasn't working on both.
I checked 3 different SIM cards, two different ones for slot 1, and one for slot 2, none of them worked on my phone while they worked fine on 2 other phones i have.
Ever since then i was trying to fix this and after countless attempts, with this guide's help i managed to get my phone to a state in which my WI-FI is working, SIM card is detected, IMEI is there, but still i have no signal. This guide says that i need to flash the QCN file but i didn't backup mine so i tried flashing the one in attachments and all it did was make my phone again not detect any SIM card, IMEI shown as unknown and WI-FI not working. I found another QCN file in some XDA thread (cant find it right now) and flashed it but it didn't fix my issue.
Sorry that this post is quite long but i wanted to include all info i can. I hope that someone actually can figure out what is wrong with my phone. Thanks in advance for all replies.
fonvi said:
Hello
2 days ago i was trying to flash LineageOS 17.1 on my redmi note 3 (kenzo). Here it said i need latest MIUI GS 10.2.1.0 so i flashed it using TWRP, rebooted, then tried to flash LineageOS but i couldn't because i got error 7 "this package is for device kate kenzo this device is ." so i googled it and found a post here by user LeoYL that i need to change lines in META-INF/com/google/android/updater-script and i just deleted those lines since my device for some reason wasnt recognised as neither kenzo nor kate, then i could flash without any problems, then i rebooted again and flashed those gapps. When i rebooted to system, my SIM card was not detected, my IMEI was shown as "unknown" and my WI-FI wasnt working either (i dont know if bluetooth worked, i didnt check since i never really use it anyway).
After that i thought it was some sort of LineageOS problem, so i tried flashing Bliss and Evolution-X but had same problems on those.
Before all of this i was using LineageOS 14.1 for like 3 or 4 years (a long time anyway) and right before flashing MIUI 10.2.1.0 everything was working perfectly fine. I'm also 100% sure my phone is Kenzo since MIFlash won't let me flash any Kate software but Kenzo software is getting flashed with no problems. I tried to fastboot flash MIUI 10.1.1.0 for Kenzo (i couldn't find fastboot flash for 10.2.1.0, so i flashed 10.1.1.0), 10.2.1.0 for Kate, (i deleted lines in flash_all_lock.bat responsible for checking whether device is Kate or Kenzo and then MiFlash let me flash it) but it wasn't working on both.
I checked 3 different SIM cards, two different ones for slot 1, and one for slot 2, none of them worked on my phone while they worked fine on 2 other phones i have.
Ever since then i was trying to fix this and after countless attempts, with this guide's help i managed to get my phone to a state in which my WI-FI is working, SIM card is detected, IMEI is there, but still i have no signal. This guide says that i need to flash the QCN file but i didn't backup mine so i tried flashing the one in attachments and all it did was make my phone again not detect any SIM card, IMEI shown as unknown and WI-FI not working. I found another QCN file in some XDA thread (cant find it right now) and flashed it but it didn't fix my issue.
Sorry that this post is quite long but i wanted to include all info i can. I hope that someone actually can figure out what is wrong with my phone. Thanks in advance for all replies.
Click to expand...
Click to collapse
I think u were using old twrp.
If u get error 7. Then u should use twrp 3.3.1 latest official.
Never flash miui rom using twrp. Always cLean flash fastboot rom using pc.
Black_Stark said:
I think u were using old twrp.
If u get error 7. Then u should use twrp 3.3.1 latest official.
Never flash miui rom using twrp. Always cLean flash fastboot rom using pc.
Click to expand...
Click to collapse
Yes when i was flashing for the first time i was still on twrp 3.1
Right now i have twrp 3.3.1, i flashed miui 10.2.1.0 using fastboot then flashed LineageOS 17.1 and it didnt change anything. My phone detects SIM card but i have no signal, when i try to call someone i get an error that says i need to turn off airplane mode so i tried turning it on and off but it didnt fix anything.
fonvi said:
Yes when i was flashing for the first time i was still on twrp 3.1
Right now i have twrp 3.3.1, i flashed miui 10.2.1.0 using fastboot then flashed LineageOS 17.1 and it didnt change anything. My phone detects SIM card but i have no signal, when i try to call someone i get an error that says i need to turn off airplane mode so i tried turning it on and off but it didnt fix anything.
Click to expand...
Click to collapse
Thats what happen when u dont know the simple thing about what model u r using. And remain confuse Whether u bought kenzo or kate. ?
And u keep on experimenting and flashing kenzo , kate, kenzo, kate on ur phone to try some luck and finally destroys ur modem.
What makes u thing that if calls doesnt work on miui but it will work on los 17 rom.
Did u official unlock ur bootloader??
Black_Stark said:
Thats what happen when u dont know the simple thing about what model u r using. And remain confuse Whether u bought kenzo or kate. ?
And u keep on experimenting and flashing kenzo , kate, kenzo, kate on ur phone to try some luck and finally destroys ur modem.
What makes u thing that if calls doesnt work on miui but it will work on los 17 rom.
Did u official unlock ur bootloader??
Click to expand...
Click to collapse
Yes i have unlocked bootloader in official way.
I wasnt confused whether my phone is kenzo or kate, i knew it was kenzo. I only started "experimenting" because i was looking for a solution to my problem on google and there were a lot of different guides on fixing my phone. I flashed kate MIUI once to "try my luck" as you said. Modem got broken probably after flashing MIUI using TWRP instead of fastboot when i was flashing before first attempt at installing lineageos 17.1. To be honest I didn't know that it makes any difference. When i bought the phone a couple of years ago I flashed lineageos 14.1 without any problems and it was just working so I didn't really expect anything to go wrong this time.
Anyway, i know what i did was quite stupid when i look at it from today's perspective, i am just looking for a way to fix it now :/
fonvi said:
Yes i have unlocked bootloader in official way.
I wasnt confused whether my phone is kenzo or kate, i knew it was kenzo. I only started "experimenting" because i was looking for a solution to my problem on google and there were a lot of different guides on fixing my phone. I flashed kate MIUI once to "try my luck" as you said. Modem got broken probably after flashing MIUI using TWRP instead of fastboot when i was flashing before first attempt at installing lineageos 17.1. To be honest I didn't know that it makes any difference. When i bought the phone a couple of years ago I flashed lineageos 14.1 without any problems and it was just working so I didn't really expect anything to go wrong this time.
Anyway, i know what i did was quite stupid when i look at it from today's perspective, i am just looking for a way to fix it now :/
Click to expand...
Click to collapse
Kate comes with extra band 20. U cant flash kate modem files on kenzo. Hardware wont accept it.
Kate miui rom also contains kate modem files.
Try to Flash kenzo old fastboot rom. May be older miui 7 based on lollipop.
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Giblet-dono said:
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Click to expand...
Click to collapse
Everytime I flashed havok I had to wipe data after flashing the ROM when it was in boitloop I held all buttons. Then went to recovery and wiped data then it booted fine