Ok, guys, since we have 5.1 firmwares with (cross)compatible modems, one can expect there will not be any new problems with "unknown baseband" issue. But it is still here with me.
My xt1095 (may be converted, I don't know how to chek it) with unlocked BL works fine with motorola original tmo_5.1 firmware and modem from retcn_5.1. But if I try to install CM12.1 (of course clean install) or any other rom based on it, I always have "unknown baseband" issue and
1) it CAN NOT be fixed only by flashing my modem backup files via fastboot.
2) it can not be fixed even if I try to restore EFS partitions from twrp backup or via any other stuff from google market.
3) manual copying partitions with /shell dd/ commands doesn't fix the issue too.
I also try to use the modem backup from my stock 5.0.2 firmware (wich I used before applying 5.1 update). Modem from 5.0.2 works fine with 5.1_tmo, but still "baseband unknown" with CM12.1. It seems that CM12.1 based roms do some "bad job" during install via twrp, or CM12.1 roms for victara on CM webpage are not compatible with my phone (what the hell!!). Last attempt was to try chineese version of mokee 5.1.1 rom (for xt1085), but the result was the same: it boots with "unknown baseband" issue and I can't fix it. I have to restore a full twrp backup finally
A little update.
I noticed a strange begaviour when I try to reboot to bootloader or recovery from reboot menu of any custom 5.1.1 rom (with "baseband unknown" issue). The screen became RED with "KERNEL PANIC DETECTED" yellow string and dumping physical memory. Simple reboot works normally (vol down + power works too). With CM12.1 based roms I tried to use Render Kernel - absoulutely the same kernel panic at reboot to bootloader. With motorola 5.1 rom I can reboot to bootloader or recovery via twrp app without any issues. Does anybody have same issues with kernel panics? And can it be the reason for unfixable "baseband unknown" issue?
Related
I flashed a self-build tar with a recovery image with Odin.
Afterwards the system did not boot up (stuck at CM boot animation) - this could be fixed by flashing Stock 4.1.2 ROM (Was 4.3 before using CM).
CM now boots up, but IMEI and Baseband-Version is unknown. I tried restoring EFS (EFS Professional backup) and I tried flashing an modem.img backup (from phillz recovery via heimdall) as well as flashing the modem.bin from 4.1.2 and 4.3 stock rom (heimdall).
Trying to flash Stock ROM (4.1.2 or 4.3, ODIN) results in "unsupported Version" on download mode screen (on the phone) and error message in Odin.
After this attempt, the phone shows "firmware upgrade encopuntered an issue. Please select recovery mode in Kies & try again"
the "emergency firmware recovery" in Kies does not list the device as "device requiring emergency recovery" - probably because it was not flashed using Kies.
I can flash all parts of the 4.3 stock ROM manually using heimdall BESIDES sboot.img (BOOTLOADER) - the "unsupported Version" is shown again on the phone,
Heimdall reports: "failed to confirm end of file transfer sequence"
With all parts besides the bootloader flashed, the device gets stuck at pre-boot logo, recovery can still not be entered
As it may help out others: You cannot Flash 4.1.2 because the bootloader of 4.3+ does not allow you to flash a pre-knox bootloader (this problem is known).
It turned out that my 4.3 stock was labelled incorrectly on the download page and was in fact another 4.1.2 - flashing a real 4.3, then heimdall CWM recovery and "install zip" the CM worked out in the end.
Hello!
I was trying to apply the Stagefright OTA on my XT1058, but I soft bricked it. Whenever a new update comes out, I prefer to flash stock image to avoid any unecessary issues that may arise from dirty flashing and not having the system requirements to apply the update without having problems. So that's what I did:
- I flashed the 5.1 stock image for my carrier (Vivo) using RSD and it worked fine, phone booted normally and etc.;
- I skipped the Google account setup and got the Stagefright OTA notification. Since I had already downloaded it before, I wanted to test it by sideloading it from Recovery. So I did it, I entered recovery mode and sideloaded the OTA. All went fine, no errors in the log. Rebooted phone. New bootanimation. Apps optimized;
- But I was getting 'gapps process has stopped' error and couldn't log into my Google Account, so I decided to reflash the stock image (I guess this was my error) using RSD;
- gpt partition flash fails;
- Phone stops booting, it just gets to the recovery menu or to the 'No command' screen;
- I tried flashing everything manually, doesn't work;
- I tried flashing gpt.bin from a Brazilian Retail firmware. It flashes without errors, but phone doesn't boot either;
Is there a way to recover from that? I have a TWRP backup from before I started all this process, but it looks like I can't restore it because my PC doesn't seem to recognize the sdcard when mounted.
Thanks in advance!
EDIT: managed to restore it using the steps from option 5 in Mark Venture's guide here. It was the only one that worked. BUT I had to flash gpt.bin and fsg.mbn from the OTA zip. Only then the phone booted. Then I took OTA normally and it installed without any hassle. So it looks like hash mismatches do not happen in this version of the firmware.
Hello everybody,
I rooted my Xperia Z1 about 8 months ago in order to install the 5.1.1 update which didn't roll out for my device probably because it was a global version (5.0.1 was the last OTA). I did a clean install with no problems, flashed DualRecovery, SuperSu, and BusyBox was working just fine. Everything was working perfectly.
About 3 months ago, I tried updating BusyBox, only to tell that the update failed (couldn't install in the path it used to be try changing the path), I read and read, and found that the solution was to delete a certain file from root that prevented me from modifying certain folders and their content(even with root access), and then do a clean install in a different path than the former one. However, I couldn't gain root access to my files, no root explorer worked! It bugged me, but I was busy at that time, so I couldn't resolve it.
Few weeks later I tried rebooting into recovery, but no method worked, no apps, no key combination, no adb, nothing at all worked! After 2 hard days I managed to install TWRP recovery using NUTS recovery project. I rebooted several times, and it was still working. I then installed BusyBox with no problems, and everything was back to perfect. Later I decided to install CM 12.1 because I always used on my Samsung Galaxy Nexus and I always loved it. So using my now working recovery, I backed everything up on a USB and then flashed CM 12.1 WITHOUT its recovery along with a GAPPS package.
CM was installed, which then rebooted into its recovery and tried to install the GAPPS package. The GAPPS installation was a fail. CM recovery asked me to try using TWRP to do such installation ( go figure! ); in fact, CM recovery couldn't flash anything besides another CM 12.1 update. After this point I wasn't able in any possible way to enter TWRP nor install it. Even if I want to flash using fastboot I couln't! adb reads my device just fine, and can use it to reboot into flashmode, which doesn't seem to be functioning properly. The blue light turns on but there isn't a thing on the screen, fastboot can't recognize is it and hence I can't flash anything using fastboot.
Should I reflash partitions if this could be done on Z1? ( I did it before on my Nexus ) Can I use Odin? I even doubt I can enter download mode on my phone
Any help would be much appreciated.
Thanks in advance!
Anyone?
No?
Ok! :sad:
Is your bootloader unlocked? To run cm on our z1 you need an unlocked bootloader because cm needs a custom kernel.
You can try Sony companion app or androxydes flashtool in combination with a pre-rooted ftf to reach stock again.
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
I managed to install TWRP using TWRP Manager app that I downloaded from APKmirror website. I installed GApps and it is working fine right now.
TWRP Manager said that I should have a FOTA recovery or something like that, and if I don't have one then I am installing the recovery on my responsibility.
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Mohdhamm said:
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Click to expand...
Click to collapse
AFAIK, Emma hasn't been updated for a LONG time. It will remain defunct with no updates and no support. Use flashtool from androxyde if you want to continue using Sony's stock ROM.
No bootloader or flash mode detection: That usually means the drivers that interfaces with your phone is missing. Search around XDA for the correct fastboot and adb drivers for your PC's OS.
My approach for fixing your issue: Find the right drivers and put a stable Lollipop ROM on your sdcard. If you have fastboot working (make sure you have unlocked bootloader), flash boot image from the Lollipop zip and flash the recovery image found in some Lollipop threads. If everything goes well, your phone will bootloop, but you'll have working recovery. Press Vol Down when the Sony Logo appears on screen to enter TWRP. Since you saved a backup of your phone elsewhere, erase all the partitions (minus sdcard), format them to ext4, and flash the Lollipop ROM from your sdcard.
Howdy folks,
This is my first attempt at flashing a custom Android ROM. It seems I can do just about everything except what I want to do, which is flash a 4.4+ ROM so my son can (at least try to) play Pokemon Go. This is on an i8190N ex Vodafone New Zealand (my understanding is that the phone is not SIM-locked).
I have:
Omni ROMs for 4.4.4, 5.1.0 and 5.1.1
GApps
SuperSU 2.77 beta
TWRP 2.6.3.0 and 2.8.0.1
Odin 3.12.3
The Voynich manuscript (irrelevant, but cool, check it out)
adb tools
Samsung drivers
Rooted the phone with KingoRoot
Flashed TWRP 2.6.3.0 using Odin
Attempted to flash all three Omni ROMs with TWRP without success (TWRP reports failure - phone goes into boot loop or boots to recovery) - wipe Cache, Dalvik, System, Data, install zip image (fail), install GApps and SuperSU, wipe cache and dalvik again anyway, cross fingers - nope.
Reflashed a (not the original) stock ROM many times
Tried to find an answer in the forums (but search seems to be broken, so it's only been skin-deep)
I can:
Boot to Recovery mode
Boot to Download mode
Get a response to adb devices
Get a response to adb get-state
Get the expected responses from many special dialler codes (e.g. the various test suites)
Reflash stock ROM using Odin or TWRP when the custom ROMs fail (Odin always reports failure, but it works; TWRP reports success)
Boot to reflashed stock ROM
I can't:
Successfully flash a bootable custom ROM
Boot into Bootloader mode (assuming it's different from Download mode - I'm still not 100% clear on that)
Get a response to the bootloader dialler code
adb reboot into BOOTLOADER mode (or any mode but DEVICE)
...and hence attempt to unlock the bootloader using fastboot
Successfully flash TWRP 2.8.0.1 (Odin says it has successfully flashed it, but when I reboot into Recovery it still shows as 2.6.3.0)
I suspect the bootloader is locked and hidden? Does that sound likely? Is there any way to crack it? Or is Download mode the same thing?
Could it be a TWRP version issue? I've seen it suggested somewhere that 2.6.3.0 can't do some things that 2.6.3.1 and above can. If so, why can't I flash TWRP 2.8.0.1? Or is there an extra step I've forgotten to take with 2.8.0.1?
Any help much appreciated.
I had another crack at this:
Downloaded cyanogenmod 12.1 and TWRP 2.8.0.0 from http://novafusion.pl.
Flashed TWRP 2.8.0.0 using Odin
Booted to Recovery - now successfully showing as 2.8.0.0
Installed cyanogenmod, GApps & SuperSU
Wiped cache and dalvik
Rebooted successfully (except that I keep getting an "Android App" error, which doesn't seem to stop me doing anything)
Pokemon Go still didn't appear in Play Store.
Downloaded Device Faker from Play Store
"Faked" several different models
Pokemon Go still didn't appear in Play Store
Downloaded Pokemon Go apk from: http://pokemon-go.en.uptodown.com/android/download
Installed Pokemon Go.
It appears to work - gets at least as far as Professor Willow and I have now shut down to leave it for my son to get started tomorrow.
This page suggests that you may get stuck at a blue-green screen during first run of the app. I didn't strike that, but the link provides instructions for what to do if that happens.
nzperso said:
Howdy folks,
This is my first attempt at flashing a custom Android ROM. It seems I can do just about everything except what I want to do, which is flash a 4.4+ ROM so my son can (at least try to) play Pokemon Go. This is on an i8190N ex Vodafone New Zealand (my understanding is that the phone is not SIM-locked).
I have:
Omni ROMs for 4.4.4, 5.1.0 and 5.1.1
GApps
SuperSU 2.77 beta
TWRP 2.6.3.0 and 2.8.0.1
Odin 3.12.3
The Voynich manuscript (irrelevant, but cool, check it out)
adb tools
Samsung drivers
Rooted the phone with KingoRoot
Flashed TWRP 2.6.3.0 using Odin
Attempted to flash all three Omni ROMs with TWRP without success (TWRP reports failure - phone goes into boot loop or boots to recovery) - wipe Cache, Dalvik, System, Data, install zip image (fail), install GApps and SuperSU, wipe cache and dalvik again anyway, cross fingers - nope.
Reflashed a (not the original) stock ROM many times
Tried to find an answer in the forums (but search seems to be broken, so it's only been skin-deep)
I can:
Boot to Recovery mode
Boot to Download mode
Get a response to adb devices
Get a response to adb get-state
Get the expected responses from many special dialler codes (e.g. the various test suites)
Reflash stock ROM using Odin or TWRP when the custom ROMs fail (Odin always reports failure, but it works; TWRP reports success)
Boot to reflashed stock ROM
I can't:
Successfully flash a bootable custom ROM
Boot into Bootloader mode (assuming it's different from Download mode - I'm still not 100% clear on that)
Get a response to the bootloader dialler code
adb reboot into BOOTLOADER mode (or any mode but DEVICE)
...and hence attempt to unlock the bootloader using fastboot
Successfully flash TWRP 2.8.0.1 (Odin says it has successfully flashed it, but when I reboot into Recovery it still shows as 2.6.3.0)
I suspect the bootloader is locked and hidden? Does that sound likely? Is there any way to crack it? Or is Download mode the same thing?
Could it be a TWRP version issue? I've seen it suggested somewhere that 2.6.3.0 can't do some things that 2.6.3.1 and above can. If so, why can't I flash TWRP 2.8.0.1? Or is there an extra step I've forgotten to take with 2.8.0.1?
Any help much appreciated.
Click to expand...
Click to collapse
All you need to do is clean install of stock ROM which suitable with your phone region, search on sammobile site. after that you can flashing stock rom, root phone, etc. Hope that will work
Hi. I had miui7 running on my Mi3 and I wanted to run cm13. I used cm12 before but went back to stock miui7.
But I needed to update baseband to update to cm13 so i used the cm13update.zip from jrizzoli.github.io/dotfiles/ and it had TWRP (modified maybe?) as the recovery and I easily installed CM13 after that. Later I updated via OTA several times and it went fine until the last time when it would not boot anymore and would stay stuck in bootloop or if i went to recovery, it would start installing the last cm13 update and then end with error 7 and would give system partition has unexpected contents error.
I tried to do EVERYTHING I could to make the phone show ANYTHING other than the cm13 updating in recovery screen or the ANNOYING cm13 logo. NOTHING worked.
I tried using miflash to flash old kitkat 4.3 rom, 4.4 rom (would give partition error but i replaced the flash_all.bat from a tutorial to bypass the partition erro) and the latest 6.0 chinese developer rom and it would finish successfully within under 100 seconds and would either go back to the cm13 bootloop or go to recovery and update cm13.
I tried QPST and emmc download with 4.4 rom and it would end with no error and go right back to bootlogo. tried flashing that rom with miflash and it would end within 80 seconds and go back to boot logo.
I tried QFIL with the latest miui8 chinese dev one with firehose and it would fail when it would go near userdata. dont remember the exact error but it was something like cannot divide by zero.
The ONLY time i could flash a different recovery is when i would use the same cm13update.zip and replace the recovery.img with another img such as cwm or mi stock recovery. when i used cwm, it would also try to install cm13 and fail as well.
I tried taking the battery off and shorting the two points which made it easier to get into EDL mode to try to use QPST with no luck.
among so many tries I booted to cm13 a few times. never could it go to homescreen though. once it would not go past the password lockscreen even if i put in the proper password and another time it would but ALL the apps would crash and i would not be able to even swipe the home screens.
sometimes when i tried flashing the cwm ota roms that was in the phone previously or the latest cm14 with otg usb, i would get
INSTALL ZIP SUCCESSFUL on top of twrp but the whole screen would fill up with red writing which said
Error opening : 'data/data/cyanogenmod.platform' (no such file or directory)
and the same thing about every app that was there on the phone.
i do not care about my files theyre all backed up. I just want to use the phone again. Any help is appreciated. thanks.
bump
Hello there, I can make and upload twrp backup of miui v8 dev version. Have you tried to restore a backup?
You'll have to make new partition for this backup ( there are so many threads like "extend partition mi3" or smth like that)
http://en.miui.com/thread-99430-1-1.html
Tried the ones from this thread?
http://forum.xda-developers.com/xia...instruction-to-restore-mi4-mi3-t3279927/page5