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.
Related
Tried to root and install CWM, CWM installed fine but I am stuck at the unlocked bootloader warning.
I've also tried installing stock roms and Pi-Llama's and Omar's custom roms using CWM, but neither would work (P-Llama would stop at the lying down android (in CWM) and Omar's finishes installing but brings me no further).
Now I think I should flash the original boot.img but I don't know which version to flash (I don't know my device info), what steps can I take?
Also is there any way to know the software version of the phone (for use with RSD Lite)?
Fastboot -> recovery brings me to CWM
Installing stock recovery and then Fastboot -> recovery brings me to the lying down android
Update: found and installed (Through RSD Lite) the right original firmware
jns1986 said:
Tried to root and install CWM, CWM installed fine but I am stuck at the unlocked bootloader warning.
I've also tried installing stock roms and Pi-Llama's and Omar's custom roms using CWM, but neither would work (P-Llama would stop at the lying down android (in CWM) and Omar's finishes installing but brings me no further).
Now I think I should flash the original boot.img but I don't know which version to flash (I don't know my device info), what steps can I take?
Also is there any way to know the software version of the phone (for use with RSD Lite)?
Fastboot -> recovery brings me to CWM
Installing stock recovery and then Fastboot -> recovery brings me to the lying down android
Update: found and installed (Through RSD Lite) the right original firmware
Click to expand...
Click to collapse
Did you wipe system/data on every install?
Intel device - Razr i Owner
Hit thanks if i help you or you like my style
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?
I'm in a weird situation, I flashed the latest stock firmware for my phone (N920GDDS4CRD2_N920GODD3CQJ2_N920GUBU4CRA1_HOME.tar) through odin and now it is stuck. Then I went to download mode again to flash twrp just to try to wipe cache and stuff to get it working, no luck as it wouldn't boot into recovery. Then I tried flashing the same firmware through odin again but I get an error (sw rev. check failed), I know why I am getting this. its because the phone doesn't allow downgrading and the firmware that I am trying to flash is the latest one. Any help would be appreciated.
Check last twrp installed. Next try flash any custom rom.zip
I'm having a bit of problem flashing my Note 5 using ODIN. Whenever I flash the stock ROM, ODIN finishes successfully but when the device boots up, it gets stuck on 'No command' and thereafter it is not possible to enter recovery mode or do anything further. I have now flashed TWRP and wiped the entire device and tried again and still, it gets stuck on 'No command'.
I am thinking that as a last resort, I may just get lucky by placing a flashable ZIP of the stock ROM onto the internal storage and install the ROM via TWRP/Recovery mode. I think I first need to get the SM-N920C stock recovery image and flash that first and thereafter flash the stock ROM from the stock recovery options.
Where can I find a stock ROM flashable zip and recovery image for my device? My device is the SM-N920C, build: N920CXXS5CRH2 XFA.
Finally, do you guys think that doing this is a waste of time since flashing with ODIN passed but resulted in the 'No command' error?
_______________________________________________
Model: SM-G973F [Beyond1LTE]
One UI: v4.1
Android: v12
Baseband: G973FXXSGHWB3
Build: G973FXXSGHWC1
Security Patch: 01 March 2023
Bootloader: Unlocked
(Verified through "Developer Options"
--> 'OEM Unlocked - On' (Greyed out)
_______________________________________________
I am having trouble flashing a Recovery file on this Galaxy S10.
I used Odin v3.13.3 and v3.14.1 ,
and in both times, Odin detects the phone is connected
but when I tried to flash the
• recovery.tar (in "AP")
• vbmeta.tar (in "CP")
Odin does not show that it flashed any of the files,
ie. there is no progress.
I'm waiting for about 1+ minutes, with no activity to show flashing is in progress.
Should it take longer than that?
I have also tried to patch the recovery through Magisk,
ie. after installing Magisk.apk on the phone,
and I directly patch the recovery.img file through Magisk.
Then, tried flashing this patched recovery.tar through Odin,
and there's still no progress in Odin to show me it's flashing.
I've figured out my problem.
I was able to flash the recovery file successfully today.
The solution was that the filename MUST be named exactly:
--> recovery.img (inside recovery.tar )
It must be spelt exactly that way: " recovery . img "
I only renamed my .tar file, as " recovery "
So, everyone ... don't repeat my mistake !
I have a weird issue now, on my S10 [Beyond1LTE].
I installed TWRP recovery and a LineageOS-based ROM,
and it was working fine for a few hours.
Through the ROM, I clicked to reboot to recovery,
and then, now my phone is in some kind of bootloop.
It does not go into recovery either.
I simply cannot get the phone to enter Recovery,
so I need help with this now.
Is it true that if the "USB Debugging"
in 'Developers Options' is switched on,
then I cannot enter the Recovery mode ?
Anyone got any tips or tricks, on how to get the S10 phone,
to enter into "Download" mode ?
Whatever I do, the phone just goes straight to booting ROM
(which itself does not load & hangs),
so I am trying to get into 'Download' mode,
to flash a new recovery, etc... and try again.