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.
Related
Hey all rooters,
I wanted to write this in the developer section of this ROM but the forum didn't let me since I had too few posts and was then regarded as a n00b. In a way I am but I have done a lot of searching and testing to get this ROM to run on my SGS2 but fails every time.
It gets stuck at the boot logo every time and here is what I have done after reading more then 55 pages of the official thread and also searched in it to find ppl with similar problem.
1. Installed XXKI3 stock via Odin. Rooted it with CF-Root-SGS2_XX_OXA_KI3-42-v4.2-CWM4. Booted into CWM Recovery. Flashed with Androidmeda_Hyperdroid-Amazing_Aquila-v1.0.0-signed.
Result: Stuck on boot
2. Since I saw ppl gone from LeoMar75 I restored a backup from that ROM and tried again to just flash from CWM Rec.
Result: Stuck on boot
3. One guy said he struggled with this for a week until he finally stock flashed XXKH3 to get the old boot loader.
http://forum.xda-developers.com/showthread.php?p=18328417&highlight=stuck+on+boot#post18328417
I did the same just before I went to bed last night. Stock installed XXKH3 and rooted with CF-Root-SGS2_XX_OXA_KH3-v4.1-CWM4. Flashed with Androidmeda_Hyperdroid-Amazing_Aquila-v1.0.0-signed.
Result: Stuck on boot
Of course prior to flashing any kernel or firmware I do a full wipe.
Is there anyone out there that can help me with information what exactly I have to do to flash this ROM? Like what's the preferred baseband, kernel and build number prior to flash?
I have tried to follow the guides in the official thread but of course with no luck. I have flashed a lot of other ROMs with no problems (Cognition 1.5.1, VillainROM, CM7, LeoMar75 etc).
Finally I just restored a backup to just get it running again and right now I have:
Android version: 2.3.5
Baseband version: I9100XXKH3
Kernel version: [email protected]
Build number: GINGERBREAD.XXKI3
I really want to try this rom so please.......HELP!!!
I tried some new stuff.
I read also ppl saying to "format /dalvik" from CWM recovery. I have no such option under Mounts and Storage (CWM 4.0.1.4). I have:
format /cache
format /system
format /data
format /sdcard
format /emmc
I formatted cache and system while I was on CF-Root KH3 but it still wont start up. I allowed it to recreate the Dalvik for 20-25 minutes.
I also read that you don't need to remove the yellow triangle if you only flash the Theme and not a Surgeon. But I thought I would give that a try.
But the guide does not say which firmware version should be used for this to work. I tried with the KH3 version but after flashing the stock firmware the CWM app was gone hence I could not flash the zImage kernel to permanently remove the yellow triangle.
I am completely out of ideas now and I really want to give this ROM a go.
Please.......HELP!!!!!
Close this thread. I'm in now with new version.
Hi Everyone,
Glad to be a part of xda..I need your advise on a possible screw-up that I did out of curiosity
I have a Galaxy S2 i9100. I had flashed CM7 on it successfully, with proper root access and everything else in order. Cm7 did not appeal to my tastes, so I decided to switch from it to VillianROM.
To flash VillianROM, I downloaded its zip file from official source and used clockwork mod recovery mode to flash it over cm7 after deleting dalvik cache and user data..
Now, I have installed VillianROM with partial success since I have lost root access to my phone.
I tried to regain root access by being a smarta** by flashing Siyah Kernelv2.6.1. Even after installing it, I dont have root access. -.-
Here are the details of my phone:
Model Number: GT-I9100
Android Version: 2.3.5
Baseband Version: I9100UHKI1
Kernel Version: [email protected]#42
Build Number: VillianROM 3.0
Can anyone please help me understand what mistake I did and how to remedy it?
Also- I plan to flash MIUI ROM now and settle with it. Any help with that with be appreciated )
Sargoon said:
Hi Everyone,
Glad to be a part of xda..I need your advise on a possible screw-up that I did out of curiosity
I have a Galaxy S2 i9100. I had flashed CM7 on it successfully, with proper root access and everything else in order. Cm7 did not appeal to my tastes, so I decided to switch from it to VillianROM.
To flash VillianROM, I downloaded its zip file from official source and used clockwork mod recovery mode to flash it over cm7 after deleting dalvik cache and user data..
Now, I have installed VillianROM with partial success since I have lost root access to my phone.
I tried to regain root access by being a smarta** by flashing Siyah Kernelv2.6.1. Even after installing it, I dont have root access. -.-
Here are the details of my phone:
Model Number: GT-I9100
Android Version: 2.3.5
Baseband Version: I9100UHKI1
Kernel Version: [email protected]#42
Build Number: VillianROM 3.0
Can anyone please help me understand what mistake I did and how to remedy it?
Also- I plan to flash MIUI ROM now and settle with it. Any help with that with be appreciated )
Click to expand...
Click to collapse
How did you know that you dont have root access???Install superuser and busybox first(restart).Download and install terminal emulator.Open it up.
Type the following
su
busybox whoami
If it says
whoami: inknown uid 0
sometimes,it says just root
Then you have root access !!
LOL!
Did you just installed a ROM over another totally different one without deleting it first? xD
If you switch ROMs, you should format /cache /data /system and Dalvik if you want to work correctly. In this case you installed VillainROM over CM7 files so the files in common are overwritten but CM7 specific files are still there and might corrupt the other ROM.
If you still have access to CWM, you can format the above partitions and reinstall VillainROM.
If you don't have access to CWM, I would suggest flashing a Stock and start it over from root.
chetan_mohanty said:
How did you know that you dont have root access???Install superuser and busybox first(restart).Download and install terminal emulator.Open it up.
Type the following
su
busybox whoami
If it says
whoami: inknown uid 0
sometimes,it says just root
Then you have root access !!
Click to expand...
Click to collapse
I used Root Checker Basic from the market to confirm that I dont have root access on my phone..
AzureusPT said:
LOL!
Did you just installed a ROM over another totally different one without deleting it first? xD
If you switch ROMs, you should format /cache /data /system and Dalvik if you want to work correctly. In this case you installed VillainROM over CM7 files so the files in common are overwritten but CM7 specific files are still there and might corrupt the other ROM.
If you still have access to CWM, you can format the above partitions and reinstall VillainROM.
If you don't have access to CWM, I would suggest flashing a Stock and start it over from root.
Click to expand...
Click to collapse
Since I cannot use CWM..I want to flash a stock rom and restart the whole rooting process to get MIUI ROM on my phone..
Can you please point me to a guide or explain me how to do so?
First of all in VR thread it states:
IF YOU THINK THE ROM ISN'T ROOTED, INSTALL SUPERUSER FROM THE MARKET. IF YOU WANT CWM APP, GET IT FROM THE ATTACHMENTS LIST
Click to expand...
Click to collapse
Then in SiyahKernel v2.6 thread it states:
TO FLASH ZIP:
Use CWM Recovery and install zip file. Wiping cache&dalvik cache is recommended for those who use BLN.
if you lose root after flashing the kernel (unlikely), flash http://goo-inside.me/superuser/su-2....fgh-signed.zip in CWM.
Click to expand...
Click to collapse
With them 2 parts of info "first should do it" you'll have ROOT very easily please read the posts from developers!
Thanks everyone for your help
Thanks for your help everyone..I have now successfully flashed 2.3.6 on my s2 from Sammobile having kernel kk5
Then rooted using CFRoot Method and Odin.
Almost done finalising MIUI ROM..
I now have a clearer understanding of android roms
I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery <cwm filename>". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
tbazett said:
I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery ". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
Click to expand...
Click to collapse
Same problem, can't locate an answer. Can someone weigh in, point us to the solution, etc.?
Thanks.
Edit: never mind. Touch removed, issue solved.
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
matrixx333 said:
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
Click to expand...
Click to collapse
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
vladeco said:
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
Click to expand...
Click to collapse
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
Did you try rom manager. download it from the market and flash CWM through it.
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
harishatrix said:
Did you try rom manager. download it from the market and flash CWM through it.
Click to expand...
Click to collapse
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett said:
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
Click to expand...
Click to collapse
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
matrixx333 said:
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
Click to expand...
Click to collapse
If I remember correctly, it just stays at the SOS error message so I had to pull the battery to turn it off. After putting the battery back in I was able to turn it on, access the boot menu (using volume down button), and then boot up to the recovery partition.
I don't know what causes the error, but my guess is there is something at the very end of the process that fails, like a checksum or some sort of signature. The result is that it actually works fine on it's own but the ROM Manager fails to recognize it.
Tbazett,
Do you remember how long you waited before you pulled the battery? Im curious if im just not waiting long enough for the install to complete.
Also, would i access CWM by powering down, holding vol down + power, then use the vol down button to cycle to 'android recovery'?
Sent from my MB860 using xda app-developers app
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
matrixx333 said:
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Cool - check out CM9 from Jokersax. You just download the cm9 zip and the google apps zip and flash both in that order.
Here's the forum for it: http://forum.xda-developers.com/showthread.php?t=1445052
I've been messing around with my x10a and I can't seem to flash any ROMs in xRecovery.
I've been trying to flash Wolfbreak's ROM (http://forum.xda-developers.com/showthread.php?t=1266080) but xRecovery keeps giving me an error saying that it can't update the script or something and that it was changed in Android 1.5.
I searched around and people said to use a lower version of xRecovery, but I installed the recovery through flashtool and it is still not working.
Another problem I've encountered is that data doesn't work anymore for my phone. No clue why.
Here are the steps on what I did.
1. Downloaded Flashtool
2. Rooted and installed xRecovery.
3. Unlocked bootloader
4. Flashed "X10a_3.0.1.G.0.75_AMERICA-US GENERIC 1233-8200.zip " for x10a through Flashtool.
5. Flashed Doom Kernel v06-1113 [medium OVERCLOCK VERSION] through Flashtool
6. Flashed Doom Kernel x10_gb_DooMKernel-v06-1113_wifi modules through xRecovery (worked)
Help is very appreciated! I've installed custom ROM's on my htc, motorola, and tablets but this phone is extremely weird.
Try ref lashing the kernel
z0mghii said:
I've been trying to flash Wolfbreak's ROM (http://forum.xda-developers.com/showthread.php?t=1266080) but xRecovery keeps giving me an error saying that it can't update the script or something and that it was changed in Android 1.5.
Click to expand...
Click to collapse
That's weird. Did You try to flash new ROM via CWM?
jakuburban said:
That's weird. Did You try to flash new ROM via CWM?
Click to expand...
Click to collapse
Yeah, I tried flashing it with CWM and I've been getting the same error about not able to update script
Edit: Data's working now but it keeps cutting in and out. Phone keeps popping out with a notification saying that download settings didn't save. Any ideas?
The error i'm getting in recovery is : amend scripting(update-script) is no longer supported. amend scripting was deprecated by google in Android 1.5. It was necessary to remove it when upgrading to the clockworkmod 3.0 Gingerbread based recovery. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
I have downloaded and tried to install several different ROMs on Vibrant T959 . I recently managed to get back to stock 2.1 ROM with ODIN and it works fine. As I understand it I need an older version of ClockworkMod so I have CWM 2.5.1.2 installed .
All attempts to flash a new ROM fail with "Error.....(Status 0) Installation aborted.
Maybe I am missing a step here? Do I need to go to 2.2 first?
Thanks.
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
markosjal said:
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
Click to expand...
Click to collapse
you might check the build.prop in your/system folder and see what it shows as the device name next to ro.product.model=
some roms change it to i9000 which would not pass the check some flashable zips have to make sure you are flashing them on the right phone.
or in this case it might even be blank or have some odd characters which would cause no name to display.
I would try re-flashing the rom which should replace the build.prop with a clean copy from that rom and then try to flash the new rom.
if that doesn't work it can be edited but I would only do that as a last resort.
on a side note error 0 means the wrong update script type was used (Amend or Edify)
Amend is the older one and Edify the newer.
you either needed a newer or older version of clockworkmod or a rom that used the other type of script.
I know you got that part fixed already by chance but I thought it might help to know what happened just in case it comes up again.
Actually i worked this out , although thanks for the reply. your reply prompted me to post my findings here to help the next poor sap with the same issue.
I installed a bunch of useless efs backup and restore apps which none would work with the efs backup I had previously made . I then installed the original galaxy s unlock app which did restore the efs backup.
Apparently the efs partition was buggered . I had several different backups and found the original locked efs then unlocked it.
I now have omni ROM 5.1.1 installed on my vibrant.
BTW if you install omni ROM 5.1.1 the recommended Google apps packages do not install, but I found another package that did install and also do not use the launcher in omni ROM (launcher 3 ?) It is buggy. The Google launcher was in the Google apps package I installed and it is far better than the omni ROM bundled launcher. I can not say that I like either of them however the seem so ordinary.