Hi guys!
I have a Z Ultra GPE (model C6806) on which I have tried to install CM11. Everything is working fine except the most important thing: I have no phone service. When I check the status, it's returning a blank IMEI.
I have tried to go into CWM (v6.0.5.1), tried to wipe the cache, date, etc, reformat all the partitions... then reinstalled CM11. No luck. Did all that again, this time installed the latest nightly build. No luck.
I really don't know what to do anymore. My phone is useless now.
Please help!!
PS
I'm new to Android and CM. Please give me instructions I can understand. Do I need to install a new kernel? I don't know how to do that. Do I need a modem update? I found this post - http://forum.xda-developers.com/showthread.php?t=2783288 - but it says not to flash. And I wouldn't know how to do that anyway.
Azra4 said:
Hi guys!
I have a Z Ultra GPE (model C6806) on which I have tried to install CM11. Everything is working fine except the most important thing: I have no phone service. When I check the status, it's returning a blank IMEI.
I have tried to go into CWM (v6.0.5.1), tried to wipe the cache, date, etc, reformat all the partitions... then reinstalled CM11. No luck. Did all that again, this time installed the latest nightly build. No luck.
I really don't know what to do anymore. My phone is useless now.
Please help!!
PS
I'm new to Android and CM. Please give me instructions I can understand. Do I need to install a new kernel? I don't know how to do that. Do I need a modem update? I found this post - http://forum.xda-developers.com/showthread.php?t=2783288 - but it says not to flash. And I wouldn't know how to do that anyway.
Click to expand...
Click to collapse
As I said in the other thread I suspect you flashed the togari version and not the togari_gpe version of CM. Just tlash the _gpe version over top (data and cache wipes) and all should be good
blueether said:
As I said in the other thread I suspect you flashed the togari version and not the togari_gpe version of CM. Just tlash the _gpe version over top (data and cache wipes) and all should be good
Click to expand...
Click to collapse
No, I flashed the correct CM, togari_gpe.
Anyway, since I don't have much to lose, I tried to flash togari and see what would happen. CWM wouldn't let me.
Azra4 said:
No, I flashed the correct CM, togari_gpe.
Anyway, since I don't have much to lose, I tried to flash togari and see what would happen. CWM wouldn't let me.
Click to expand...
Click to collapse
I'm not a developer but i'd tried all the solutions suggested everywhere but it's not working either until i extracted the modem from ROMs that work for me (with IMEI/Baseband) and suddenly everything work like it should.
View attachment FD_C6833_Patch4.4-761.zip is the original zip i obtained from thread somewhere here in xda few months ago. (Forgotten where) For reference only
View attachment C6802_Modem_Patch.zip is my version with all the files needed for cm11 to work with my no baseband/imei z ultra <-- Flash This
I am pretty sure it will work with other z ultra variant, just replace the files in /etc/ and /system/ within the zip with files from the rom that work for your device and flash it via recovery. Hope my solution work for you.
Edit: Sorry about the confusion. It's 6am i'm still awake..
wtfhax said:
I'm not a developer but i'd tried all the solutions suggested everywhere but it's not working either until i extracted the modem from ROMs that work for me (with IMEI/Baseband) and suddenly everything work like it should.
View attachment 2973638 is the original zip i obtained from thread somewhere here in xda few months ago. (Forgotten where) For reference only
View attachment 2973639 is my version with all the files needed for cm11 to work with my no baseband/imei z ultra <-- Flash This
I am pretty sure it will work with other z ultra variant, just replace the files in /etc/ and /system/ within the zip with files from the rom that work for your device and flash it via recovery. Hope my solution work for you.
Edit: Sorry about the confusion. It's 6am i'm still awake..
Click to expand...
Click to collapse
I have this issue after installing CM12 on c6802, I had try your soulution but it failed to flash ( using fasboot ), any suggestion how to do it correctly.
Thank you
ichanz69 said:
I have this issue after installing CM12 on c6802, I had try your soulution but it failed to flash ( using fasboot ), any suggestion how to do it correctly.
Thank you
Click to expand...
Click to collapse
The file attached was meant to flash via custom recovery
wtfhax said:
The file attached was meant to flash via custom recovery
Click to expand...
Click to collapse
I flashed it using custom recovery (CyanogenMod recovery) but it shows an error..please help
Related
Hello guys,
I kinda confused about flashing jbx kernel because every time I try to flash it into custom rom (fresh install or not), it made my phone go boot loop (screen never go pass SS menu) right after first reboot system. But if i'm excluding the jbx, there's no problem about booting at all.
this is my flashing prosedure when using jbx:
- wipe everything except sd card & internal
- install rom
- install gapps
- install jbx kernel
- reboot....and bamm! bootloop
Already search the rom thread that everyone said it's compatible with it, tried with/without tweak, or wipe cache/dalvik cache every single flashing and still get same problem. Is it just me? Please help me
btw this is my 1st thread in xda so please go easy on me
additional note--> I'm always getting "unable to mount /osh". Maybe there's a connection with this.
Thx
guitarholixx said:
Hello guys,
I kinda confused about flashing jbx kernel because every time I try to flash it into custom rom (fresh install or not), it made my phone go boot loop (screen never go pass SS menu) right after first reboot system. But if i'm excluding the jbx, there's no problem about booting at all.
this is my flashing prosedure when using jbx:
- wipe everything except sd card & internal
- install rom
- install gapps
- install jbx kernel
- reboot....and bamm! bootloop
Already search the rom thread that everyone said it's compatible with it, tried with/without tweak, or wipe cache/dalvik cache every single flashing and still get same problem. Is it just me? Please help me
btw this is my 1st thread in xda so please go easy on me
additional note--> I'm always getting "unable to mount /osh". Maybe there's a connection with this.
Thx
Click to expand...
Click to collapse
It could be a corrupted zip file. Try re-downloading it.
The mount error you mentioned was faced by some users when they updated to SS 3.6x (some, not all), but it didn't cause any flashing issues.So that is not probably related.
neo.ank said:
It could be a corrupted zip file. Try re-downloading it.
The mount error you mentioned was faced by some users when they updated to SS 3.6x (some, not all), but it didn't cause any flashing issues.So that is not probably related.
Click to expand...
Click to collapse
thank you for your reply neo. sorry i forgot to mention that i already try jbx even before kitkat version is out. previously i try slimbean with jbx for jb. try re-downloading, try the previous build, still get that problem. And now i'm using KK LiquidSmooth v3.0 nightly and try flashing with JBX_Kernel-3.0-Hybrid-4.4_2014-02-06.zip, yet still getting bootloop. so until now im using it without jbx
98 2628252
is there no one here experience this except me? no one have another answer for this? I'm really eager to overclocking and tweaking my xt912
(sorry for the title. use wrong textbox for img verification)
guitarholixx said:
is there no one here experience this except me? no one have another answer for this? I'm really eager to overclocking and tweaking my xt912
(sorry for the title. use wrong textbox for img verification)
Click to expand...
Click to collapse
hi man, if you are able to enter to safestrap, mount system and delete bootanimation (system>>media) Good Luck!
guitarholixx said:
is there no one here experience this except me? no one have another answer for this? I'm really eager to overclocking and tweaking my xt912
(sorry for the title. use wrong textbox for img verification)
Click to expand...
Click to collapse
Are you sure you're downloading the and flashing the correct JBX for your OS. It sounds like the wrong version.
JBX-Kernel 3.0.8 Versions:
0.8.x ==> Android 4.2.2
1.x == > Android 4.3
2.x == > Android 4.4
JBX-Kernel 3.0.31 Versions:
3.x == > Android 4.4
Click to expand...
Click to collapse
If you're using the correct version with OS, try an older KK JBX zip, he has many for 4.4 (http://d-h.st/users/dtrail/?fld_id=28796#files) and I know at least half work with Liquid Smooth and CM11, did on my XT912. Also Verify MD5 before you flash.
Another problem, based on that error, do you still have root for the device? Double check.
I'm sorry for the late reply. Been busy since my last post.
siracuervo said:
hi man, if you are able to enter to safestrap, mount system and delete bootanimation (system>>media) Good Luck!
Click to expand...
Click to collapse
nope. still not working.
hakarune said:
Are you sure you're downloading the and flashing the correct JBX for your OS. It sounds like the wrong version.
If you're using the correct version with OS, try an older KK JBX zip, he has many for 4.4 (http://d-h.st/users/dtrail/?fld_id=28796#files) and I know at least half work with Liquid Smooth and CM11, did on my XT912. Also Verify MD5 before you flash.
Another problem, based on that error, do you still have root for the device? Double check.
Click to expand...
Click to collapse
I think i download the correct one. I'm using JBX_Kernel-3.0-Hybrid-4.4_2014-02-06.zip for liquidsmooth KK, and yes the root access still there.
And the last i try flashing, I still getting the bootloop. then I flash it again to restore the build in kernel and still flashing the moto x camera and a few tweaks and my phone boot perfectly with moto x camera installed. don't know with the tweaks though. I think just the kernel that made my phone bootlooping.
guitarholixx said:
I think i download the correct one. I'm using JBX_Kernel-3.0-Hybrid-4.4_2014-02-06.zip for liquidsmooth KK, and yes the root access still there.
And the last i try flashing, I still getting the bootloop. then I flash it again to restore the build in kernel and still flashing the moto x camera and a few tweaks and my phone boot perfectly with moto x camera installed. don't know with the tweaks though. I think just the kernel that made my phone bootlooping.
Click to expand...
Click to collapse
Do you have a ROM running now? So, I had this problem with slimkat and the jbx. Just flash the ROM over now! Go on recovery and flash the rom
EDIT: I didn´t read the massage... Solved?
Enviado desde mi XT910
siracuervo said:
Do you have a ROM running now? So, I had this problem with slimkat and the jbx. Just flash the ROM over now! Go on recovery and flash the rom
EDIT: I didn´t read the massage... Solved?
Enviado desde mi XT910
Click to expand...
Click to collapse
sorry for the late reply. Really busy here
Do you mean when I'm getting the bootloop, i have to dirty flash it again with the ROM? okay i'll try as soon as possible.
for changing the kernel, not yet solved. but for installing camera moto x, trickster etc, it's work. I still can't overclocked it.
after I dirty flash it, looks like the kernel got replaced with the new one. It's successfully booted, but I cannot overclock it, the apps like xposed, moto x camera, etc is missing.
finally it work. i flash it without any tweak at all. my phone need to reboot twice before it successfully enter homescreen.
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is also available.
NOTE: if you flash the deodexed version and have problems with root, flash UPDATE-SuperSU-v2.02.zip from here. I don't anticipate any root problems, but just in case, this will fix it.
100% stock: STOCK-4.4.2-P5200(fixed).zip
Deodexed + rooted: STOCK-DEODEXED-ROOTED-4.4.2-P5200(fixed).zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Restl3ss said:
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is in the works. Bear with me.
100% stock: STOCK-4.4.2-P5200.zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Click to expand...
Click to collapse
Very good work done by you! Yesterday I spent hours to unzip the file but unsuccessfully. I will try it right now! Thanks a lot!
Restl3ss said:
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is in the works. Bear with me.
100% stock: STOCK-4.4.2-P5200.zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Click to expand...
Click to collapse
I tried but it doesn't flash. Received "failed" message. I am using the latest TWRP by angel666. Any idea what I am doing wrong?
edsoedso said:
I tried but it doesn't flash. Received "failed" message. I am using the latest TWRP by angel666. Any idea what I am doing wrong?
Click to expand...
Click to collapse
I've got the same problem.
Hold on, I'm working on it
@edsoedso
@Max4000
I think I've fixed it. Reuploading now. Bear with me.
The problem was a fairly stupid one. I edited the assert to fit P5200 instead of P5210 (I'm using the same updater-script I used for the wifi model stock kitkat).
Problem is, I used mac textedit instead of gedit. One preserves linux encoding, the other does not. Can you guess which is which?
I believe it was Homer Simpson who said, "DOH".
Anyway, edited the updater-script with gedit and just removed the assert completely, so once it's done uploading you should be able to flash without issue.
Restl3ss said:
@edsoedso
@Max4000
I think I've fixed it. Reuploading now. Bear with me.
The problem was a fairly stupid one. I edited the assert to fit P5200 instead of P5210 (I'm using the same updater-script I used for the wifi model stock kitkat).
Problem is, I used mac textedit instead of gedit. One preserves linux encoding, the other does not. Can you guess which is which?
I believe it was Homer Simpson who said, "DOH".
Anyway, edited the updater-script with gedit and just removed the assert completely, so once it's done uploading you should be able to flash without issue.
Click to expand...
Click to collapse
Do not worry, I installed stock 4.4.2 using odin, than TWRP and superuser. It looks great! Please work on 4.4.2 Pimpdroid and let us known the results. Regards!
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
just uploaded a deodexed + rooted build. If you have any troubles with root flash SuperSU from the link in OP.
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
khaledreno said:
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
Click to expand...
Click to collapse
I always do a factory reset, format data, and full wipe with any ROM Can you move your files to your PC via USB cable?
khaledreno said:
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
Click to expand...
Click to collapse
I flashed without wiping and had big problems. You should really do a full wipe.
Restl3ss said:
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
Click to expand...
Click to collapse
I just saw your note. I am downloading both versions, flash them and let you know.
i have downloaded both versions but instal failed
any way does any one know which site i can download the MD5 of the software without corruption ?
Restl3ss said:
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
Click to expand...
Click to collapse
@Restl3ss:
I flashed both versions using TWRP 2.6.3.0 and everything went well. The first unrooted rom after completing flashing offered to install superuser and I did it. The second rom version did not offered it so I rebooted to TWRP and installed superuser from sd card. I am keeping the second version on my tablet. Looks nice and works very well. I will remove some system apps that I do not use and free some additional memory.
It seems that battery is draining faster than 4.2.2. Does anybody note it? Any solution? Thank you!
I have tried the rootet and fixed version, , but it doesn´t work, it hangs on boot!
Installed with TWRP 2.7.1.0, may i have to install this ROM with Odin ?
jamalau said:
I have tried the rootet and fixed version, , but it doesn´t work, it hangs on boot!
Installed with TWRP 2.7.1.0, may i have to install this ROM with Odin ?
Click to expand...
Click to collapse
hey man you need to wipe system, data,cache and dalvik-cache
then flash the zip and it should work
edsoedso said:
@Restl3ss:
I flashed both versions using TWRP 2.6.3.0 and everything went well. The first unrooted rom after completing flashing offered to install superuser and I did it. The second rom version did not offered it so I rebooted to TWRP and installed superuser from sd card. I am keeping the second version on my tablet. Looks nice and works very well. I will remove some system apps that I do not use and free some additional memory.
Click to expand...
Click to collapse
Is there an update zip for recovery? I have 2.6.1 twrp and get error message during install. Can i update to latest twrp or philz by Flash, or do i have to connect the tab to PC, and need to do the beginners Steps?
Thanks for advices
Aaah, i got it... A flashable philz for p5200...
quitschibu84 said:
Is there an update zip for recovery? I have 2.6.1 twrp and get error message during install. Can i update to latest twrp or philz by Flash, or do i have to connect the tab to PC, and need to do the beginners Steps?
Thanks for advices
Aaah, i got it... A flashable philz for p5200...
Click to expand...
Click to collapse
Can you post the link for the Philz 5200 recovery?
thks
So I saw this lollipop rom(http://forum.xda-developers.com/showthread.php?t=2716306) and I was waiting for the official one from htc but this had what I wanted. It said I need to have the 4.4.4 firmware but I didnt know how to get it because I couldnt get the ota update on stock for a certain reason and so it flashed the 4.4.4 gpe rom then after that I flashed the 5.0 rom but now I have no wifi and when I reboot its in the bootloop and I dont know what to do now. I would appreciate it if anyone could try and help me. Thank you.
If you just flash a GPe rom it dosent mean you flashed the firmware. I was actually having this same problem so I just flashed the US Dev Sense 4.4.4 firmware and the Lollipop rom worked fine.
Guide on Flashing Firmware: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Scroll all the way down and look for the 3.28.1540.5 firmware and flash that.
asap marcus said:
So I saw this lollipop rom(http://forum.xda-developers.com/showthread.php?t=2716306) and I was waiting for the official one from htc but this had what I wanted. It said I need to have the 4.4.4 firmware but I didnt know how to get it because I couldnt get the ota update on stock for a certain reason and so it flashed the 4.4.4 gpe rom then after that I flashed the 5.0 rom but now I have no wifi and when I reboot its in the bootloop and I dont know what to do now. I would appreciate it if anyone could try and help me. Thank you.
Click to expand...
Click to collapse
still need help? you need to just get back to bootloader an then enter recovery wipe device an restore a working backup so your phone is working an then go from there.
Tigerstown said:
still need help? you need to just get back to bootloader an then enter recovery wipe device an restore a working backup so your phone is working an then go from there.
Click to expand...
Click to collapse
forgot to backup but can I just flash the last rom I had.
asap marcus said:
forgot to backup but can I just flash the last rom I had.
Click to expand...
Click to collapse
Yea just do a wipe before...wipe both cache an data,system an then flash ROM should be good. Let me know what happens.
Tigerstown said:
Yea just do a wipe before...wipe both cache an data,system an then flash ROM should be good. Let me know what happens.
Click to expand...
Click to collapse
I got an answer and they posted the firmware so im going to try that first
Masterguy635 said:
If you just flash a GPe rom it dosent mean you flashed the firmware. I was actually having this same problem so I just flashed the US Dev Sense 4.4.4 firmware and the Lollipop rom worked fine.
Guide on Flashing Firmware: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Scroll all the way down and look for the 3.28.1540.5 firmware and flash that.
Click to expand...
Click to collapse
Thanks im downloading the firmware now. Ive been waiting for the official update from HTC when that comes out should I flash that or should I stick with the one I have now.
even more broken
Masterguy635 said:
If you just flash a GPe rom it dosent mean you flashed the firmware. I was actually having this same problem so I just flashed the US Dev Sense 4.4.4 firmware and the Lollipop rom worked fine.
Guide on Flashing Firmware: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Scroll all the way down and look for the 3.28.1540.5 firmware and flash that.
Click to expand...
Click to collapse
Before I flashed that firmware I wiped my phone and there is nothing on it. Also when I try to boot it it tells me to put in a password and I tried my google one but it didnt work also in twrp it says i have 0mb taken up on my phone. I also tried to adb sideload the rom to re flash it but that didnt work it said on my phone it couldnt put the file on my phone so it tried to put it on my ram. Are you sure that was the right firmware I have an att htc one m8. Also do you know what I can do or known some one that can help. Ive been having so many problems with my phone for two days straight and i havent able to use it.
Donot have to put in a password in recovery,format your data partition
asap marcus said:
Before I flashed that firmware I wiped my phone and there is nothing on it. Also when I try to boot it it tells me to put in a password and I tried my google one but it didnt work also in twrp it says i have 0mb taken up on my phone. I also tried to adb sideload the rom to re flash it but that didnt work it said on my phone it couldnt put the file on my phone so it tried to put it on my ram. Are you sure that was the right firmware I have an att htc one m8. Also do you know what I can do or known some one that can help. Ive been having so many problems with my phone for two days straight and i havent able to use it.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Donot have to put in a password in recovery,format your data partition
Click to expand...
Click to collapse
Thankyou so much it worked. But I don't know if its gonna get stuck in a boot loop thought but im not going to try to find that out now
Very welcome glad it got sorted out.
asap marcus said:
Thankyou so much it worked. But I don't know if its gonna get stuck in a boot loop thought but im not going to try to find that out now
Click to expand...
Click to collapse
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
phonester said:
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
Click to expand...
Click to collapse
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
khan_pegasus said:
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
It worked, thanks.
link to download radio.zip?
This situation happens when you switch to an OFFICIAL Rom from an UNOFFICIAL one like Mokee or RR from Siddhesh or Santosh. This is because these ROMs lock the bootloader and cause other problems too.
Radio.zip may not always fix the problem. If you are really stuck, there is a lengthy process that is guaranteed to work.
1. Flash one of the MiUI Fastboot ROM (global or chinese stable works fine) for RN3SD with Mi Flash tool. Use Flash All in the options at the bottom.
2. If you had an officially unlocked bootloader, use the Mi Unlocker tool to unlock your bootloader. Otherwise, you need to follow the unofficial unlock guide.
3. Flash official TWRP or a variant if you now what you are doing. Refer to this thread if you are not sure which TWRP will work.
3a. Download and copy this file to internal storage - LazyFlasher. I have verified this file to work with MiUI7 and MiUI8 global.
3b Reboot the phone in fastboot mode. On your PC, copy the TWRP img file to the adb directory and open command window there. Rename it to recovery.img. Use this command
Code:
fastboot flash recovery recovery.img
3c Boot into recovery (using ADB or Vol-pwr button shortcut). DO NOT BOOT into the phone before you do this. Flash the Lazyflasher zip with TWRP. You could probably flash this using fastboot too, I just never tried it.
Dhanajay made a guide video here. The video is a little outdated, and the updated instructions are in the description and comments.
You phone is now rooted and you have TWRP. Happy flashing.
This method will soon be outdated as a graphical UI for ADB is already in progress. Others have done it before, but this one shows real promise. Check here for details.
It has been a few months now since the RN3SD launch and the time has come when unofficial ROMs are no longer the best option around. Most Official ROMs, including the ones from RR and XOSP among others work great now and are incredbilby smooth and efficient. The war for the best kernel is now starting, and custom kernels will be responsible for the next round of reasons for bricked phones. Be VERY careful when you are flashing a ROM with a custom kernel. Be prepared to do some legwork if things go wrong.
Joswin said:
link to download radio.zip?
Click to expand...
Click to collapse
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
talkaboom said:
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
Click to expand...
Click to collapse
Link isn't working...
Can you mirror it?
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
Seems to be down. Normally works. Give it some time.
But if you are moving from an unofficial ROM, flashing radios alone is unlikely to work. Radio zip fix is for undetected SIM and IMIE errors. Check your IMIE number in About Phone. If you are showing an IMIE number instead of '0', flashing radio may be pointless.
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
New Link available.
https://mega.nz/#!9hlljJKD!QmjwPqMOH...gOqWkEJ0QasGE4
talkaboom said:
New Link available.
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
virtualgates said:
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
Link is from August 8th. That **** has mirrored a hundred times by now.
Also, the problem is now tackled in a different way. If you're facing a similar issue, ask in the rom thread you are trying to flash.
If you are facing this problem now, just flash the correct CM firmware.
P.S. On XDA, please do not question why someone posted a link or method that did not work for you. Do your research. No one is obligated to solve your problems.
Flashed radio. Zip. Worked for me.
Sent from my Redmi Note 3 using Tapatalk
Hello talkaboom!
the link is not working anymore. Any chance to upload it again please? Thanks a lot!
I'm left clueless here. I just can't get it to boot, no matter what ROM/Kernel i'd flash. It was originally running OOS 2.3.1 but flashing it now won't work anymore. It worked briefly for 1 hour with that AOSP 8.1 but then after trying to flash gapps it stuck again in a bootloop. Sometimes it also freezes and reboots while i am flashing sometimes. I really have no idea what should i do next, hope you can help me.
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Kéno40 said:
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Click to expand...
Click to collapse
I updated the bootloader like over a year ago or so. I also tried 2 different versions of TWRP, now i am using the latest one.
ALSO, very sorry it actually is OOS 3.1.4, not 2.3.1, i just typed briefly what i could remember, i haven't been using this phone for months now but i would like to give it to a relative so there's that. Hope you can help me out, i have no clue why is it acting up like that.
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Try to flash official ROM after having wiped everything
Kéno40 said:
Try to flash official ROM after having wiped everything
Click to expand...
Click to collapse
That's what i first tried, mentioned it in the main post.
yayakuya said:
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Click to expand...
Click to collapse
I don't know what to make of this, thought maybe anyone else encountered this problem and has a clue.
gabytzu338 said:
That's what i first tried, mentioned it in the main post.
Click to expand...
Click to collapse
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Kéno40 said:
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Click to expand...
Click to collapse
I don't really understand what you are trying to say. I did wipe everything and the only way to flash anything is through adb sideload anyway since the device is not recognized as storage while in TWRP. I think I am gonna give up on it, I was gonna sell it but I can't risk having it act up days/weeks after i sold it.