Post Reply

[Guide] Bootloader and kernel guide | X8 | W8 | X10 mini | X10 mini pro |

23rd September 2011, 11:48 AM   |  #321  
SpyderX's Avatar
OP Senior Member
Flag Singapore
Thanks Meter: 840
 
924 posts
Join Date:Joined: Mar 2011
More
Quote:
Originally Posted by andy_dunlop

Nice, but when I download it, it downloads as .txt and not .ftf is this normal?

Sent from my U20i using xda premium

Nope. But I think renaming it to a .ftf file will do the trick. Mediafire has this problem occasionally from what I've heard. Make sure that the downloaded file size is the same as the size listed on mediafire. I'll see if I can upload the file to Dropbox .

EDIT: Added links to 2 stock kernels, does anyone have a link for X10 mini (E10) stock kernel?

X8 (E15) and W8 stock kernel:

Download link: http://www.mediafire.com/?zb3zhdkodgy55ch#1

Direct download link: http://db.tt/gg2jJVZi

X10 mini pro (U20) stock kernel:

Direct download link: http://db.tt/S7Nm4WZx

X10 mini (E10) stock kernel:

-Will be added at a later date-
Last edited by SpyderX; 23rd September 2011 at 02:57 PM.
The Following 2 Users Say Thank You to SpyderX For This Useful Post: [ View ]
24th September 2011, 01:42 PM   |  #322  
chequebo1's Avatar
Senior Member
Flag Valencia
Thanks Meter: 23
 
119 posts
Join Date:Joined: Dec 2010
More
ok

1/ CM7 Backup 2.0.7
2/ I'm back to Stock SE
3/ Root (now if I could)
4/ Crack bootloader (now if I could)
5/ installed Xrecovery
6/ CWM-installed recovery
7/ Installed backup CM7 2.0.7

But now to put a SIM from another provider I get the message "Press unlock code." Is this normal?
24th September 2011, 01:56 PM   |  #323  
SpyderX's Avatar
OP Senior Member
Flag Singapore
Thanks Meter: 840
 
924 posts
Join Date:Joined: Mar 2011
More
Quote:
Originally Posted by chequebo1

ok

1/ CM7 Backup 2.0.7
2/ I'm back to Stock SE
3/ Root (now if I could)
4/ Crack bootloader (now if I could)
5/ installed Xrecovery
6/ CWM-installed recovery
7/ Installed backup CM7 2.0.7

But now to put a SIM from another provider I get the message "Press unlock code." Is this normal?

It means that your phone has been sim-locked. Looks like you have to unlock it again. I did warn you about this being able to restore the sim lock on your phone.
24th September 2011, 02:28 PM   |  #324  
chequebo1's Avatar
Senior Member
Flag Valencia
Thanks Meter: 23
 
119 posts
Join Date:Joined: Dec 2010
More
Quote:
Originally Posted by SpyderX

It means that your phone has been sim-locked. Looks like you have to unlock it again. I did warn you about this being able to restore the sim lock on your phone.


Thank you for your attention, but do not quite understand what I mean ...


Edit:
Sorry, I understood that this method also release the SIM lock ... ok sorry, thanks.
Last edited by chequebo1; 24th September 2011 at 05:58 PM. Reason: sorry
24th September 2011, 02:41 PM   |  #325  
Senior Member
Flag Łódź
Thanks Meter: 236
 
703 posts
Join Date:Joined: Jan 2011
More
Ok, unlocked successfully, now I've a question - since bootloader unlocking interfers with simlock unlocking, is it safe now to get rid of simlock with any method?
25th September 2011, 02:12 AM   |  #326  
SpyderX's Avatar
OP Senior Member
Flag Singapore
Thanks Meter: 840
 
924 posts
Join Date:Joined: Mar 2011
More
Quote:
Originally Posted by Graveir

Ok, unlocked successfully, now I've a question - since bootloader unlocking interfers with simlock unlocking, is it safe now to get rid of simlock with any method?

For this I'm not too sure, some users in here reported that they have sim-unlocked their phones after bootloader unlocking their phones. I suggest that if you want to try this, it is best to try unlocking using the IMEI code unlocking method.
25th September 2011, 02:23 AM   |  #327  
charos's Avatar
Senior Member
Flag Budapest
Thanks Meter: 26
 
166 posts
Join Date:Joined: Nov 2010
More
Somehow it seems that semcboot is write-protected :

Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
2803 KB/s (585731 bytes in 0.204s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
376 KB/s (3087 bytes in 0.008s)
[1]   Segmentation fault      /data/local/tmp/...
Waiting ...
Getting ROOT rights.
error: protocol fault (no status)
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
715 KB/s (8064 bytes in 0.011s)
Second, we need to write semcboot ;)
1655 KB/s (596916 bytes in 0.352s)
Error, cannot erase device
: Input/output error
Press any key to continue . . .
Also "Segmentation fault /data/local/tmp/ " seems to be a weird error... any ideas (x10 mini pro)?
25th September 2011, 03:24 AM   |  #328  
angel08's Avatar
Member
Thanks Meter: 2
 
31 posts
Join Date:Joined: Apr 2008
I have the phone unlocked or released by IMEI by the operator. I can safely modify the bootloader? thanks
25th September 2011, 03:59 AM   |  #329  
SpyderX's Avatar
OP Senior Member
Flag Singapore
Thanks Meter: 840
 
924 posts
Join Date:Joined: Mar 2011
More
Quote:
Originally Posted by charos

Somehow it seems that semcboot is write-protected :

Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
2803 KB/s (585731 bytes in 0.204s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
376 KB/s (3087 bytes in 0.008s)
[1]   Segmentation fault      /data/local/tmp/...
Waiting ...
Getting ROOT rights.
error: protocol fault (no status)
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
715 KB/s (8064 bytes in 0.011s)
Second, we need to write semcboot ;)
1655 KB/s (596916 bytes in 0.352s)
Error, cannot erase device
: Input/output error
Press any key to continue . . .
Also "Segmentation fault /data/local/tmp/ " seems to be a weird error... any ideas (x10 mini pro)?

SEMCboot is not write-protected for us, have you missed 33 pages worth of
Code:
unlocked bootloader successfully
messages? Retry unlocking your bootloader, remember to follow all the steps and read carefully.

Maybe you could make a backup in CWM recovery, reflash to stock, root your device, unlock the bootloader and then restore the CWM backup?

__________________________________________________ _____

@Angel08

If you had used the search tool or read the first post carefully perhaps you wouldn't ask such a question.

Yes, you can safely modify the bootloader but remember to follow ALL instructions carefully. Read carefully too. As I said, the process MIGHT restore the sim-lock on your phone so do this at your own risk. I think you can sim-unlock it again after bootloader-unlocking it though.
The Following User Says Thank You to SpyderX For This Useful Post: [ View ]
25th September 2011, 04:29 AM   |  #330  
charos's Avatar
Senior Member
Flag Budapest
Thanks Meter: 26
 
166 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by SpyderX

SEMCboot is not write-protected for us, have you missed 33 pages worth of

Code:
unlocked bootloader successfully
messages?

Well, apparently I was only referring to my case. It was a statement for "cannot erase device" of MY issue. I've read very carefully all instructions and went by the book. I'll reflash to get rid of the recovery if that causes the issue.

Post Reply Subscribe to Thread

Tags
bootloader, guide, info, msm7227, unlock
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes