Hi all,
Just wondering, on pershoot's blog it states that for CWM 5.0.2.7:
"Note:
Models with a radio will not have that partition available."
Does this just mean that it's not possible to update the radio from CWM, or does it actually completely disable the radio partition?
Related
Hi guys,
I search over this thread, i can't find any usefull information about this. So i start a new thread. sorry if i make a double thread.
I was trying to unlock my T-Mobile vibrant with SGS Unlock, but there was no code found. Then i tried to search in this forum about repairing nv_data.bin, and i followed the tuts written in the thread. At last i found my vibrant unlocked.
My question is, after i reboot the device, i see the baseband is unknown. i have to turn off flight mode everytime i reboot it to make the signal available. i try to wipe data / wipe cache, and the baseband will show up. But it happen again after i reboot the device.
how can i get the baseband back? the baseband is T959UVKB1.
update:
i was on bionix 1.3.1 before, and i was using overstock kernel.
then i updated the kernel to cm7 kernel, because i wanted to reflash the radio i found in this forum (cm7_radio_KB1).
now, my vibrant is in clockworkMod 3.0 and stuck on cyanogen startup logo.. :-D
i can't install any firmware from sd card, it only shows internal drive. when i click on external sd in recovery mode, i can't access it.
this is so confusing.
any help will be appreciated.
thank you.
CWM 3.0 uses edify scripting while 2.x uses amend scripting. That's why you're unable to flash anything in cwm. As far as the unknown baseband after unlocking....I'm somewhat in the same boat. Some rom's I flash will result in an unknown baseband and some won't. This all started after trying cm7. Did you happen to backup your /efs folder before flashing the cm7 kernel?
MINUS Stl said:
CWM 3.0 uses edify scripting while 2.x uses amend scripting. That's why you're unable to flash anything in cwm. As far as the unknown baseband after unlocking....I'm somewhat in the same boat. Some rom's I flash will result in an unknown baseband and some won't. This all started after trying cm7. Did you happen to backup your /efs folder before flashing the cm7 kernel?
Click to expand...
Click to collapse
yes, i read that after i tried to update any rom after i flash with cwm 3.0. i did backup the efs folder, but it seems it has been updated since i tried to unlock with sgs unlock yesterday and there was no code found.
hello
i install the CM7 stable version and now the gps doesn't work at all
i search in this forum for solution and i read that upgrageing the radio Fix the problem.
but.. i try to move the radio file to sd card and install it With CWM3 and the device wrote me installation aborted... what i doing wrong?
i must say my device is S-ON With fake flash
http://tinyurl.com/3jurzlb
I would advise avoiding flashing radio if you can, if it goes wrong your Legend WILL be a brick
cwm 3 don't support radio zip, but cwm 2 yes.
I'm already running fw 2.4.19 after following the info in this thread:
http://forum.xda-developers.com/showthread.php?t=1196318
What would be the most effective way of upgrading to is latest 2.4.81 kernel without loosing the data ext4 partition content?
I've seen someone mentioned using the Stock firmware, rooting again, then re-do the ext4 kernel and re-edit init.rc... but is that really the best way to do it?
Finally updated it myself...
-Flashed the stock FW from the recovery menu
-Without booting the stock kernel I flashed chulri's rw root kernel (restart then recovery menu directly)
-Without booting again, I flashed WhoDunnit's rw/ext4 kernel
-Deleted stock Android kernel from the menu.
Completed the reboot without loosing any data...
(Please note that I am not looking for advice on rooting --- I am already familiar with CF-root and other rooting methods for the SGS2 and have read most guides/FAQs etc. I am not asking about flashing anything either. I have a very specific question about a behaviour difference between stock Gingerbread recovery and stock ICS recovery: It is about using unrooted stock firmware to launch CWM recovery over ramdisk.)
The thread
http://forum.xda-developers.com/showthread.php?t=1501719
shows that even without root, ICS stock recovery can "chain-load" CWM recovery, via the "apply update from SD card" menu item, with the CWM recovery .zip file on the SD card root. At that point CWM recovery takes over (still on initramfs) giving the user full control provided via CWM (e.g. mounting system partition read-write and installing suid programs etc).
On the other hand, from the Gingerbread stock recovery <3e> (on unrooted SGS2 running 2.3.4 factory stock XXKG6), attempting to "chain-load" CWM recovery using the same zip file fails with:
E: failed to verify whole-file signature
E: signature verification failed
(This is true for both the 5.8.1.5 touch recovery and the 4.0.1.5 non-touch recovery zip files for the SGS2 available from http://www.clockworkmod.com/rommanager/.)
My questions:
1. Is this because of a vulnerability in Samsung ICS stock roms which is not present in the Samsung Gingerbread stock roms (for the SGS2)?
2. If so, can we expect that future releases of Samsung ICS stock rom for the SGS2 to have this security hole closed?
Cheers.
Without going in to details, that I don't know anyway....
Ics recovery has option to load cwn from internal storage.
So it seems that (at least so far) ICS stock recovery has removed the signature verification check that was present in Gingerbread stock 3e recovery, right?
Trying to get my first rom on to this note.
Ive tried twrp 2.7.1 / 2.8.0 and cwmr 5.5 / 6.0.4.3 and I havent managed to get one installed yet.
Current error im trying to get past is
"radio must be newer than ucmd3." on CWMR
"E:Error executing updater binary in zip" In TWRP I'm getting
dzee206 got me up to the latest CWMR which helped but now I'm stuck.
Currently on stock 4.0 rooted with custom recovery
----------------------------------------------------------------------------------------------------------------------------------------
SOLVED
apparently you need a new radio from the factory image. if you return to stock using odin and the imgs for stock linked here apparently it puts an old radio in.
you need this radio to flash 4.4+ in both TWRP and CWMR
http://forum.xda-developers.com/showthread.php?t=2261713
oscar the grouch said:
Trying to get my first rom on to this note.
Ive tried twrp 2.7.1 / 2.8.0 and cwmr 5.5 / 6.0.4.3 and I havent managed to get one installed yet.
Current error im trying to get past is
"radio must be newer than ucmd3." on CWMR
"E:Error executing updater binary in zip" In TWRP I'm getting
dzee206 got me up to the latest CWMR which helped but now I'm stuck.
Currently on stock 4.0 rooted with custom recovery
----------------------------------------------------------------------------------------------------------------------------------------
SOLVED
apparently you need a new radio from the factory image. if you return to stock using odin and the imgs for stock linked here apparently it puts an old radio in.
you need this radio to flash 4.4+ in both TWRP and CWMR
http://forum.xda-developers.com/showthread.php?t=2261713
Click to expand...
Click to collapse
That is why i always suggest to odin the latest firmware if coming from ics and wanting to flash a jb or kitkat rom… its actually a partition issue involving the modem partition. Which is very important to booting up.
I couldnt find that info. Samsung needs a fastboot feature. odin is a pain