semi unlock

[odystyle]

i just wonder....if there are semi unlock
coz i found that my phone has been locked back by flashing sbf and didnt brick
i brought my atrix back in 2012. and the time i was buy this phone the android version are 2.3.4 stock
so after get bored with stock rom,i decided to unlock my phone. and get the job done so my phone has been unlock
after month of experiment with the custom rom. i decided to return stock, i been google that since coz they said that you will brick if you flash sbf on unlocked phone until i find this thread http://forum.xda-developers.com/showthread.php?t=1014964
so i try to download full sbf and flash it and got it boot up without any damage. one i just notice that when my phone start there are no unlocked write on the top of red logo anymore

 

[palmbeach05]

i just wonder....if there are semi unlock
coz i found that my phone has been locked back by flashing sbf and didnt brick
i brought my atrix back in 2012. and the time i was buy this phone the android version are 2.3.4 stock
so after get bored with stock rom,i decided to unlock my phone. and get the job done so my phone has been unlock
after month of experiment with the custom rom. i decided to return stock, i been google that since coz they said that you will brick if you flash sbf on unlocked phone until i find this thread http://forum.xda-developers.com/showthread.php?t=1014964
so i try to download full sbf and flash it and got it boot up without any damage. one i just notice that when my phone start there are no unlocked write on the top of red logo anymore

Find a pudding sbf file, flash it via rsd, go through the steps to unlock, and you'll be good to go

Sent from my MB860 using xda app-developers app

 

[odystyle]

Find a pudding sbf file, flash it via rsd, go through the steps to unlock, and you'll be good to go

Sent from my MB860 using xda app-developers app

what i mean after i flash my phone with full sbf, my phone been locked back
i just wonder if somebody experience the same like i did....
coz people say it will brick your phone if you flash a full sbf

 

[palmbeach05]

what i mean after i flash my phone with full sbf, my phone been locked back
i just wonder if somebody experience the same like i did....
coz people say it will brick your phone if you flash a full sbf

I understood what you meant. Its not necessarily true that you will brick your device. If you have a device on 2.3.6, don't go flashing a 2.3.4 sbf. The pudding files are not full sbfs, and are designed to unlock the device, just follow the directions on the threads and you'll be fine. Myself, i've locked and unlocked mine several times since Oct 2012 when the ICS leak hit the internet. I've even done it on a replacement hardware (i had a lagging cpu and a cracked screen, thats why it was a replacement).

Sent from my MB860 using xda app-developers app

 

[odystyle]

I understood what you meant. Its not necessarily true that you will brick your device. If you have a device on 2.3.6, don't go flashing a 2.3.4 sbf. The pudding files are not full sbfs, and are designed to unlock the device, just follow the directions on the threads and you'll be fine. Myself, i've locked and unlocked mine several times since Oct 2012 when the ICS leak hit the internet. I've even done it on a replacement hardware (i had a lagging cpu and a cracked screen, thats why it was a replacement).

Sent from my MB860 using xda app-developers app

so the fuse that keep our bootloader locked not really been blown away right
its just open the gate for us
By the way are u already try the new kernel 3.1

 

[palmbeach05]

so the fuse that keep our bootloader locked not really been blown away right
its just open the gate for us
By the way are u already try the new kernel 3.1

It is blown. To quote a dev who's name i forget at the moment, this is the best way to describe what happens. When you flash a full sbf, you cause the device to "forget" that the fuse is blown. When you re-flash the pudding sbf, you make the device remember that it is unlocked.

I've been trying it out here and there, but just because i've been dealing with errands and some personal drama, i haven't been able to fully sit down and take the new kernel for a spin. From what little i've seen so far, it does seem to be much better than the old kernel

Sent from my MB860 using xda app-developers app

 

[odystyle]

It is blown. To quote a dev who's name i forget at the moment, this is the best way to describe what happens. When you flash a full sbf, you cause the device to "forget" that the fuse is blown. When you re-flash the pudding sbf, you make the device remember that it is unlocked.

I've been trying it out here and there, but just because i've been dealing with errands and some personal drama, i haven't been able to fully sit down and take the new kernel for a spin. From what little i've seen so far, it does seem to be much better than the old kernel

Sent from my MB860 using xda app-developers app

ok now that i fully understand with fuse thing thnks to you explanation about it...
yeah..... you were right about the new kernel , i have been try countless time to make my phone boot up with the new kernel, but it wont boot up
mybe my phone like to stay stable bulid lol

 

[ravilov]

coz people say it will brick your phone if you flash a full sbf

No they don't. Nobody said that. You will only brick the phone if you flash a wrong SBF. What you have (apparent relocking) is perfectly normal and expected and discussed before.

 

[palmbeach05]

ok now that i fully understand with fuse thing thnks to you explanation about it...
yeah..... you were right about the new kernel , i have been try countless time to make my phone boot up with the new kernel, but it wont boot up
mybe my phone like to stay stable bulid lol

Odd, might be a device issue.

Install steps should be like this

-Make nandroid backup of current rom
-Wipe system, data, cache, osh (webtop), and dalvik
-install rom
-install recommended gapps
-reboot and enjoy

Typically that is the norm, but there are some roms that change up the install instructions. I know that the beanstalk rom instructions are like that.

Sent from my MB860 using xda app-developers app

 

[odystyle]

Odd, might be a device issue.

Install steps should be like this

-Make nandroid backup of current rom
-Wipe system, data, cache, osh (webtop), and dalvik
-install rom
-install recommended gapps
-reboot and enjoy

Typically that is the norm, but there are some roms that change up the install instructions. I know that the beanstalk rom instructions are like that.

Sent from my MB860 using xda app-developers app

but i didn't have problem when boot up MROM ICS with leaked kernel
i always do a full wipe before flashing rom

 

[palmbeach05]

but i didn't have problem when boot up MROM ICS with leaked kernel
i always do a full wipe before flashing rom

Ok, well thats good. Which rom are you trying to use right now? Are you trying to use it with the old kernel or the new kernel?

Sent from my MB860 using xda app-developers app

 

[odystyle]

right now i try to use the new rom with the new kernel.... made by krystianp
i have been try countless time to make it boot up but nothing work

Sent from my MB860 using xda app-developers app

 

[palmbeach05]

right now i try to use the new rom with the new kernel.... made by krystianp
i have been try countless time to make it boot up but nothing work

Sent from my MB860 using xda app-developers app

Ok. I was able to get that to work for me. I wiped it down, flashed the rom, then rebooted and flashed gapps. Odd that its not working for you.

Sent from my MB860 using xda app-developers app

 

[odystyle]

yeah....well its only me stay on GB forever

Sent from my MB860 using xda app-developers app

 

[krystianp]

yeah....well its only me stay on GB forever

Sent from my MB860 using xda app-developers app

Did you try installing some other non GB rom but with old kernel?

Edit: I just read that you tried MROM ICS. Do you have sdcard inserted?

Edit2: Get this info from your phone:
- memory type:
- panel_size:
- sdcard present:
- atag revision:
- tegrapart:
- radio:

 

[odystyle]

delete

 

[odystyle]

Did you try installing some other non GB rom but with old kernel?

Edit: I just read that you tried MROM ICS. Do you have sdcard inserted?

Edit2: Get this info from your phone:
- memory type:
- panel_size:
- sdcard present:
- atag revision:
- tegrapart:
- radio:

1.after i unlock my phone i only use MROM 7 AND MROM ICS with leaked kernel

2.when i try to get the new cm9 with 3.1 kernel. i put the rom,gapps and facelock on internel memory i didnt use memory card coz before flashing i always read instruction before flashing just to be clear what im doing.

3.phone info
memory type HYNIX
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR5: 0x0006 (0x0606)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR6: 0x0000 (0x0000)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR7: 0x0000 (0x0000)
<6>[ 0.000000] parse_tag_motorola: LPDDR2 MR8: 0x0054 (0x5454)
Panel size
[ 0.000000] parse_tag_motorola: panel_size: 80000740
Sdcard present
16GB class 10
Atag revision
<4>[ 0.000000] mot_fixup: atag_revision=83f0
Tegrapart
tegrapart=mbr:d00:100:800,kpanic:2100:400:800