Hello guys,
I have a problem with my phone. I cannot install the correct firmware, I can only install the firmware (Orange Hi 4G) but it's not compatible with my phone, so the phone bootloops and doesn't go into the system.
I cannot install the firmware for my device because it's not signed with the orange's certificate and key, my phone has the orange's recovery and fastboot is disabled on the rom so I cannot use that. I have the certificate and key but I cannot get the key in a .pem file, the certificate is already in one.
Phone: ZTE Blade Apex 2
Recovery in Phone: Orange recovery
Recovery: Stock recovery
Certificate:
MIIErjCCA5agAwIBAgIJAOuCYND5gmZOMA0GCSqGSIb3DQEBBQUAMIGWMQswCQYD
VQQGEwJDTjERMA8GA1UECBMIU2hhbmdoYWkxETAPBgNVBAcTCFNoYW5naGFpMQww
CgYDVQQKEwNaVEUxIjAgBgNVBAsTGVNtYXJ0cGhvbmUgU29mdHdhcmUgRGVwdC4x
DDAKBgNVBAMTA1pURTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEB6dGUuY29tLmNu
MB4XDTExMDMwODA3MTM0M1oXDTM4MDcyNDA3MTM0M1owgZYxCzAJBgNVBAYTAkNO
MREwDwYDVQQIEwhTaGFuZ2hhaTERMA8GA1UEBxMIU2hhbmdoYWkxDDAKBgNVBAoT
A1pURTEiMCAGA1UECxMZU21hcnRwaG9uZSBTb2Z0d2FyZSBEZXB0LjEMMAoGA1UE
AxMDWlRFMSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QHp0ZS5jb20uY24wggEgMA0G
CSqGSIb3DQEBAQUAA4IBDQAwggEIAoIBAQC6XMcxr5zlAnZfYCeKPgt+w4y/fmB7
SzZSJvCx4hFKKq6m9CHg60vhlVQ4gLkuKb1l+pFbJdrP8yL1YKQqSrWWDAhPcuIl
Lj3UcmzfbMRQhM4mrXf49ees2xyVZO38KjtSSBw/ygvH5PSrX6KFUqQdxVeciLga
tYYoOEpRGKZdeL+HAI0EMFssOow00jPP44IB9Vi9UiEHOqvTHVmDIdQWOmAgWXlA
36sdWsSebLzWXjm2vB6OJaPV93zxy+tym33mkduc2DHQiH6TFUr4YmtDOZJ7y3jZ
2VzJU3VViYNunm/Da0NAPYwtbyeOgr+5npV7CfzY436lqLYaAlHJjx37AgEDo4H+
MIH7MB0GA1UdDgQWBBS6NVREsJ5wGdTi/26mEwf8h2KDfzCBywYDVR0jBIHDMIHA
gBS6NVREsJ5wGdTi/26mEwf8h2KDf6GBnKSBmTCBljELMAkGA1UEBhMCQ04xETAP
BgNVBAgTCFNoYW5naGFpMREwDwYDVQQHEwhTaGFuZ2hhaTEMMAoGA1UEChMDWlRF
MSIwIAYDVQQLExlTbWFydHBob25lIFNvZnR3YXJlIERlcHQuMQwwCgYDVQQDEwNa
VEUxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAenRlLmNvbS5jboIJAOuCYND5gmZO
MAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADggEBAKSJA12gqyhorPk0EkHN
gUTLJoytol5SHPksdhbMjTOTEsaPiOVQZ0sHk9JDPoXRJlZvLXIvZCtzG+YCjpF8
Gv/uK47jHJsBG5L9LyI/LNctPOTefj3aBQklLxUgeblaaK2AFGb+ygmX8plGSwOz
9p4mgr8UQtPsdXP6gxEejI3oZ8Bz4HmttL+GwabCZAxuF9O2Z4vX1oCYbAVLAKz+
SUoMVXY9hzSa/Ttx+HeH0oHPXdZ0A2VyxpLiFIXdbdC9zWjB8AGQgmYINDHlQRG4
hPH9+NppDljxd19T1cEzkFERFEI8dWkTCaE8mRNQfShSt7N3vW+kfELq8rlkvDMW
9JM=
Key:
AAAAAQAAABSR52UCnjiSFiwLKyzthZxY4sJ0ZQAABdEBAAh2ZXJpc2lnbgAAASw2
S2EsAAAAAAAFWC41MDkAAAMGMIIDAjCCAmsCEH3Z/gfPqB63EHln+6eJNMYwDQYJ
KoZIhvcNAQEFBQAwgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwg
SW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0
aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwg
SW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2ln
biBUcnVzdCBOZXR3b3JrMB4XDTk4MDUxODAwMDAwMFoXDTI4MDgwMTIzNTk1OVow
gcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UE
CxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0
eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBh
dXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMXtERXVxp0KvTuWpMmR9Z
mDCOFoUgRm1HP9SFIIThbbP4pO0M8RcPO/mn+SXXwc+EY/J8Y8+iR/LGWzOOZEAE
aMGAuWQcRXfH2G71lSk8UOg013gfqLptQ5GVj0VXXn7F+8qkBOvqlzdUMG+7AUcy
M83cV5tkaWH4mx0ciU9cZwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAFFNzb5cy5gZ
nBWyATl4Lk0PZ3BwmcYQWpSkU01UbSuvDV1Ai2TT1+7eVmGSX6bEHRBhNtMsJzzo
KQm5EWR0zLVznxxIqbxhAe7iF6YM40AIOw7n60RzKprxaZLvcRTDOaxxp5EJb+Rx
BrO6WVcmeQD2+A2iMzAo1KpYoJ2daZH9AQAKb3JhbmdlX3R0ZwAAASw2S6sfAAAA
AAAFWC41MDkAAAOaMIIDljCCAv+gAwIBAgIJAOzGENAox4zdMA0GCSqGSIb3DQEB
BQUAMIGPMQswCQYDVQQGEwJGUjEWMBQGA1UECBMNSWxlIGRlIEZyYW5jZTEOMAwG
A1UEBxMFUGFyaXMxFzAVBgNVBAoTDkZyYW5jZSBUZWxlY29tMSgwJgYDVQQLEx9G
VC1PRi1EVEYtREVYLURFQ0ktRUVEQVRBLU9TQ1BTMRUwEwYDVQQDEwxPcmFuZ2VU
VEctQ0EwHhcNMTAxMTEwMTAzNDQ5WhcNMzAxMTA1MTAzNDQ5WjCBjzELMAkGA1UE
BhMCRlIxFjAUBgNVBAgTDUlsZSBkZSBGcmFuY2UxDjAMBgNVBAcTBVBhcmlzMRcw
FQYDVQQKEw5GcmFuY2UgVGVsZWNvbTEoMCYGA1UECxMfRlQtT0YtRFRGLURFWC1E
RUNJLUVFREFUQS1PU0NQUzEVMBMGA1UEAxMMT3JhbmdlVFRHLUNBMIGfMA0GCSqG
SIb3DQEBAQUAA4GNADCBiQKBgQC+MWWiupCgPdKl2jH2dl2HZ5VzzZPc+T/teetD
qdme17tDAbzEEKc6bf/WB3bUY4qgS2sbB8Gz/jMekfmJ3tLpW93WOwpnmaGAY0+Z
dZylacejycAdOeiPS8bq9zUlfYGPi0MvaPcAoSO75hkV/14xLLKjGY7aCNMC4Ws1
+0PqSQIDAQABo4H3MIH0MB0GA1UdDgQWBBTbMtaQXxFEPq1PYFCzwRirTy6+qzCB
xAYDVR0jBIG8MIG5gBTbMtaQXxFEPq1PYFCzwRirTy6+q6GBlaSBkjCBjzELMAkG
A1UEBhMCRlIxFjAUBgNVBAgTDUlsZSBkZSBGcmFuY2UxDjAMBgNVBAcTBVBhcmlz
MRcwFQYDVQQKEw5GcmFuY2UgVGVsZWNvbTEoMCYGA1UECxMfRlQtT0YtRFRGLURF
WC1ERUNJLUVFREFUQS1PU0NQUzEVMBMGA1UEAxMMT3JhbmdlVFRHLUNBggkA7MYQ
0CjHjN0wDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQBuShubIhCowVw5
e/Zx4O/2es78YXMJBXVQ/7bhM4sGZ6HAsahIXg0l6aP8xROGsfofetz+9WjRMyeU
MzsovcdNnNR/ge0nr5BQb7Ef/4N6DNbd6t0u1InNSRIXemwPI/77ggVf8XgW24Jg
fSb5CwqSq4adfev5K4IUBeQeQmnNMQEAD3ZlcmlzaWduX3NlcnZlcgAAASxVM/4G
AAAAAAAFWC41MDkAAAYwMIIGLDCCBZWgAwIBAgIQbk/6s8XmacTRZ8mSq+hYxDAN
BgkqhkiG9w0BAQUFADCBwTELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMTwwOgYDVQQLEzNDbGFzcyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IC0gRzIxOjA4BgNVBAsTMShjKSAxOTk4IFZlcmlTaWdu
LCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmswHhcNMDkwMzI1MDAwMDAwWhcNMTkwMzI0MjM1OTU5
WjCBtTELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEvMC0GA1UE
AxMmVmVyaVNpZ24gQ2xhc3MgMyBTZWN1cmUgU2VydmVyIENBIC0gRzIwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDUVo9XOzcopkBj0pXVBXTatRlqltZx
Vy/iwDSMoJWzjOE3JPMu7UNFBY6J1/raSrX4Po1Ox/lJUEU3QJ90qqBRVWHxYISJ
pZ6AjS+wIapFgsTPtBR/RxUgKIKwaBLArlwH1/ZZzMtiVlxNSf8miKtUUTovStoO
mOKJcrn892g8xB85essXgfMMrQ/cYWIbEAsEHikYcV5iy0PevjG6cQIZTiapUdqM
ZGkD3pz9ff17Ybz8hHyIXLTDe+1fK0YS8f0AAZqLW+mjBS6PLlve8xt4+GaRCMBe
ztWwNsrUqHugffkwer/43RlRKyC6/qfPoU6wZ/WAqiuDLtKOVImOHikLAgMBAAGj
ggKpMIICpTA0BggrBgEFBQcBAQQoMCYwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3Nw
LnZlcmlzaWduLmNvbTASBgNVHRMBAf8ECDAGAQH/AgEAMHAGA1UdIARpMGcwZQYL
YIZIAYb4RQEHFwMwVjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24u
Y29tL2NwczAqBggrBgEFBQcCAjAeGhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhMDQGA1UdHwQtMCswKaAnoCWGI2h0dHA6Ly9jcmwudmVyaXNpZ24uY29tL3Bj
YTMtZzIuY3JsMA4GA1UdDwEB/wQEAwIBBjBtBggrBgEFBQcBDARhMF+hXaBbMFkw
VzBVFglpbWFnZS9naWYwITAfMAcGBSsOAwIaBBSP5dMahqyNjmvDz4Bq1EgYLHsZ
LjAlFiNodHRwOi8vbG9nby52ZXJpc2lnbi5jb20vdnNsb2dvLmdpZjApBgNVHREE
IjAgpB4wHDEaMBgGA1UEAxMRQ2xhc3MzQ0EyMDQ4LTEtNTIwHQYDVR0OBBYEFKXv
CxHOwEEDo0plkEiyHOBXLX1HMIHnBgNVHSMEgd8wgdyhgcekgcQwgcExCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3Mg
MyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTow
OAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk
IHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrghB92f4H
z6getxB5Z/uniTTGMA0GCSqGSIb3DQEBBQUAA4GBAGN0Lz1Tqi+X7CYRZhr+8d5B
JxnSf9jBHPniOFY6H5CuOcUgdav4bC1nHynCIdcUiGNLsJsnY5H48KMBJLb7j+M9
AgtvVP7UzNvWhb98lR5eYhHB2QmcQrmy1KotmDojYMyimvFu6M+O0Ro8XhnF15s1
sAIjJOUFuNWI4+D6ufRfAF0Slrj4O266ePon5MC54zEX3hju
I don't know what to do anymore. I tried to get the certificate and key.pk8 to sign the other firmware but no luck. If anyone could help me I would appreciate it. Thank you in advance!
You gotta be kidding me!!! No one helps around here?
Helppppppppppppppppppppppppp!
Helpppppppppppppppppppppppppppppppppppp!!!!!!!!!!!!!!!!!!!!!!!!!!!
Helllllllllllllllllllllllllllllppppppppppppppppppppppp
HEeeeeeeeeeeeeeeeeeeeeeeeeeeelllllllllllllllllllppppppppppppppppppppppppppppppppp :crying:
I'm not familiar with this phone, but I'm sure that a ROM can't disable fastboot. Try to install the previous firmware, if it exists (if it does not, then try a custom firmware.)
Hope this helps,
Drew
Sent from my Nexus 4 using XDA Free mobile app
@drew1ind - Thanks for replying.
The issue is that it doesn't let me enter fastboot mode. I flashed the recovery witch is found in the rom and the phone got stuck in bootloop. And it doesn't let me install any other firmwares but the orange rom or pretty much do anything.
SickAttack said:
@drew1ind - Thanks for replying.
The issue is that it doesn't let me enter fastboot mode. I flashed the recovery which is found in the rom and the phone got stuck in bootloop. And it doesn't let me install any other firmwares but the orange rom.
Click to expand...
Click to collapse
How different is your phone compared to the one which can use the ROM you're trying to install? Only ever install a ROM if it's for your specific phone. An example would be for Samsung phones; some carriers make different versions for some Samsung phones, which require different ROMS. If you installed the bootloader from that phone's ROM, then you probably hard bricked your phone, meaning it's gone for good. How did you flash the recovery if you couldn't access fastboot? Also, why can you only install the orange rom? I would recommend staying with the orange ROM if it's the only one that works. You might not be able to access the fastboot/recovery because you're using the wrong key combination. If nothing else works, I would recommend a nexus phone as they're easily moddable, and almost impossible to brick.
Best of luck,
Drew
drew1ind said:
How different is your phone compared to the one which can use the ROM you're trying to install? Only ever install a ROM if it's for your specific phone. An example would be for Samsung phones; some carriers make different versions for some Samsung phones, which require different ROMS. If you installed the bootloader from that phone's ROM, then you probably hard bricked your phone, meaning it's gone for good. How did you flash the recovery if you couldn't access fastboot? Also, why can you only install the orange rom? I would recommend staying with the orange ROM if it's the only one that works. You might not be able to access the fastboot/recovery because you're using the wrong key combination. If nothing else works, I would recommend a nexus phone as they're easily moddable, and almost impossible to brick.
Best of luck,
Drew
Click to expand...
Click to collapse
The rom is from the same phone, but it's from a different carrier. I think the reason that it just restarts over and over is because my phone only has 4GB and that one has 8GB and the partitions are messed up or not compatible with my phone's storage.
I had access to fastboot mode the first time I flashed it, but I can't access it now or I don't know how to.
SickAttack said:
The rom is from the same phone, but it's from a different carrier. I think the reason that it just restarts over and over is because my phone only has 4GB and that one has 8GB and the partitions is messed up or not compatible with my phone's storage.
I had access to fastboot mode the first time I flashed it, but I can't access it now.
Click to expand...
Click to collapse
It has to be with the same carrier. As for fastboot, either something happened to your volume rockers/power button, or it somehow changed it the combination. Also, is 4GB available for the other phone's carrier? If not, that *may* be the problem. One thing it might have done is flash a different broadband from what your carrier gives you (a broadband is basically a .img file that is also called a radio which dictates how your cellular functions handle). Some phones are known to brick from bad radio files (I think, atleast).
drew1ind said:
It has to be with the same carrier. As for fastboot, either something happened to your volume rockers/power button, or it somehow changed it the combination. Also, is 4GB available for the other phone's carrier? If not, that *may* be the problem. One thing it might have done is flash a different broadband from what your carrier gives you (a broadband is basically a .img file that is also called a radio which dictates how your cellular functions handle). Some phones are known to brick from bad radio files (I think, atleast).
Click to expand...
Click to collapse
The buttons still work, if I press all of the buttons it will bring me to download mode, I assume. It's a black screen with the led always on, but I don't know what I can do there.
What I need to do is either edit the current rom of orange and sign it with the certificate and key, but I need to put the key in a .pem file (the key and certificate is on the main post) but I cannot do it. Or I could flash the recovery of the other rom that works on my phone which is for 4gb phones, but I need to flash the recovery for that rom but I can't seam to do it.
SickAttack said:
The buttons still work, if I press all of the buttons it will bring me to download mode, I assume. It's a black screen with the led always on, but I don't know what I can do there.
What I need to do is either edit the current rom of orange and sign it with the certificate and key, but I need to put the key in a .pem file (the key and certificate is on the main post) but I cannot do it. Or I could flash the recovery of the other rom that works on my phone which is for 4gb phones, but I need to flash the recovery for that rom but I can't seam to do it.
Click to expand...
Click to collapse
I can't help you with that, as I don't have your phone. Also, it doesn't have a sub-forum on the main page, meaning that this phone isn't very popular. Sadly, all I can say for you is to get a new phone. What to learn from this:
Only flash files that are for your specific phone, and possibly carrier
Look through multiple guides, and double-check everything.
Best of luck,
Drew
drew1ind said:
I can't help you with that, as I don't have your phone. Also, it doesn't have a sub-forum on the main page, meaning that this phone isn't very popular. Sadly, all I can say for you is to get a new phone. What to learn from this:
Only flash files that are for your specific phone, and possibly carrier
Look through multiple guides, and double-check everything.
Best of luck,
Drew
Click to expand...
Click to collapse
I just bought this phone, how could I buy a new one?
SickAttack said:
I just bought this phone, how could I buy a new one?
Click to expand...
Click to collapse
Save money, I guess? I would recommend that you get a phone that much more people use.
help!!!!!
Please send a dump of the firmware, for 2 months can't repair hard brick(((( zte blade apex 2
help!!!!!help!!
Please send a dump of the firmware, for 2 months can't repair hard brick(((( zte blade apex 2
Try with voldown +power as you see the logo
Conmect your phone to PC and run "adb devices" if it detects then type "adb reboot bootloader"
When u run adb devices it may show the device I'd like "?" This (in my case it showed like this)
I think it may help
U can try digitel rom for u r device it may work
http://playdroidv.blogspot.in/2015/07/rom-stock-digitel-zte-blade-apex-2.html?m=1
send me the rom of this phone (zte blade apex 2 ) and i show you how to flash
Related
Bell (canada) calls it Vibrant, but it's really I9000 with NAM.
anyways, I prepared some tutorial based on MODACA, Paul's JP3 rom (prerooted)
(Paul's original thread can be found here. http://alturl.com/bu6qh)
Before I begin, I would like to warn you.
I initially bought 2 phones but only one of the phone was able to go into "download mode"
this is very important because in case of emergency, this is the only way to revive the phone.
if your phone can't get into "download mode" by pressing "pwr, vol down, home" simultaneously, then
I advise you to
go back to the store and have it exchanged
go back to the store and have it exchanged
go back to the store and have it exchanged
When I went to the futureshop to excahnge the phone, I tried the phone right on the spot after the payment.
put the battery in, three button, if you see the download mode.
Take the phone.
Another way of quickly checking if the phone can go into download mode by pressing buttons vol down home pwr to turn on and see if it goes into the DL mode
IF your phone can't be in download mode and you don't feel like exchanging the phone.
please proceed to ALLGAMER's post
http://forum.xda-developers.com/showpost.php?p=7538723&postcount=2
===============One shot BETA froyo JP3 FW pre root===================
pre req, <samsung kies installed> <win7 64bit adb usb driver>
Steps: (download the link: http://www.megaupload.com/?d=9J6TYUKF unzip with 7zip)
1. put the battery into the galaxy S
2. Go into the download mode (mentioned above)
3. run Odin
4. select PIT 512 (included) chose radio, PDA, CSC and check repartition
5. connect the phone
6. FLASH!!!!!!
7. done
your phone is now rooted with latest JP3 FROYO.
I will post the video tutorial soon
I am currently using this phone on FIDO with sim unlocker that I bought 2 years ago from
dealextreme.com
it works with data, SMS, outbound calls
but I am having trouble receiving calls. (8outof 10 times, it goes directly into the voicemail)
this is not realated to the firmware but my faulty sim adapter.
I ordered an unlock code from unlockgenie (for 26$)
I will report once I get the unlock code.
========ROOT for STOCK ROM===========
(if you would rather wait for the real Froyo from samsung)
the attachment is the modified version for 2.1
I simply changed i9000 to i9000M
put the file in the SDCARD (not external SD card)
do vol up, home, pwr
chose to run update.zip
now you have rooted I9000M
===========tweak=================
do the following tweak
http://forum.xda-developers.com/showthread.php?t=749495
My score went up from 900~ to 1700~ woot!!!!
========AUG10th===================
Been using JP3 last couple of days with above once click patch.
the patch made huge difference.
Browser crashes time to time where there's heavy flash video.
missing incoming calls due to the unlock sim adapter,
outgoing and 3G works great
===========================================
Latest Adobe Flash
http://www.megaupload.com/?d=NT2ER7HX
websites tend to crash less with the latest Flash beta 3
=====================================
64bit driver for ADB
http://www.megaupload.com/?d=K5458W3G
Use drop box if you want to share your android phone with PC
http://db.tt/pGyW1E
for those who are worried about losing WCDMA850 band (850 3G frequency)
I can confirm that with JP3 rom, you will get the band depending on the area.
Although in the service menu, 850 band is not picked, my phone was on 850 3G band.
yes, like many others, i've found out my version of Bell, does not allow you to do the 3 button recovery mode
now i've to do it the long way via adb, but even so it's not showing up in the list of usb devices in adb.
but it works fine in win7 x64 + Kies and as a Mass Storage
not sure if it's something in Bell firmware did to block the phone to make it harder to hack
I cant extract the zip with winrar, it says its broken...
audino said:
I cant extract the zip with winrar, it says its broken...
Click to expand...
Click to collapse
try 7zip, or you need to download it again, most likely your download was incomplete
AllGamer said:
try 7zip, or you need to download it again, most likely your download was incomplete
Click to expand...
Click to collapse
Downloaded 2times, and tried 7zip -> same problem...
does this unlock the phone by any chance?
Mine just keeps rebooting when I hold down by pressing "pwr, vol down, home" simultaneously. I must be doing something wrong.. but I can get in download mode when connect to my computer and I use the Android development tools
I don't think swaping the phone is going to work for most people since the phone a store has are likey from the same lot.
audino said:
Downloaded 2times, and tried 7zip -> same problem...
Click to expand...
Click to collapse
can anyone repack this?
Ive downloaded the file 3 times on 2 pc and the same issue with 7zip/winrar...
TriC_101 said:
Mine just keeps rebooting when I hold down by pressing "pwr, vol down, home" simultaneously. I must be doing something wrong.. but I can get in download mode when connect to my computer and I use the Android development tools
I don't think swaping the phone is going to work for most people since the phone a store has are likey from the same lot.
Click to expand...
Click to collapse
I got the Vibrant from Bell and have the same problem as you. I can't get into Download Mode not matter what I try. I can get the phone into Recovery Mode using the Android SDK though. How do you get into Download Mode using the SDK?
I successfully rooted my phone but now I am trying to get Froyo on it. Is it possible to use Rom Manager to flash to Android 2.2? I tried using the rom you linked but the file cannot be unzipped as others have mentioned.
Thanks
"adb reboot download" does the trick.
Thanks Now I just need the the rom... does anyone know if the phone can be flashed with the firmwares listed on samsung-firmware.webs.com?
I will re up the file.
Btw if you still have the stock rom and it doesnt go into download mode
i insist that you get your phone exchanged
what if it gets bricked? Then you cant restore it anymore because you need debug mode for adb
leegoon84 said:
it works with data, SMS, outbound calls
but I am having trouble receiving calls. (8outof 10 times, it goes directly into the voicemail)
this is not realated to the firmware but my faulty sim adapter.
Click to expand...
Click to collapse
I'm betting it's not your "faulty SIM adaptor" but rather you not having the 850 HSPA band with the I9000 firmware.
And good luck with that unlock code, but it's not going to happen any time soon. Trust me, I've been through this with the Captivate.
Croak said:
"adb reboot download" does the trick.
Click to expand...
Click to collapse
i'm way past that already, but the update.zip says it's not good as reported on another topic.
it's weird, trying other methods as we speak
Croak said:
I'm betting it's not your "faulty SIM adaptor" but rather you not having the 850 HSPA band with the I9000 firmware.
And good luck with that unlock code, but it's not going to happen any time soon. Trust me, I've been through this with the Captivate.
Click to expand...
Click to collapse
I doubt that it's 850mhz issue
because the phone has physical hardware to support 850 and when I did the test on JP3
I didn't update the radio (baseband) and I was having the same issue.
however when I'm on a call with someone( I already called the other person) I do get an incoming call.
AllGamer said:
i'm way past that already, but the update.zip says it's not good as reported on another topic.
it's weird, trying other methods as we speak
Click to expand...
Click to collapse
the reason why update doesn't work is because you need to change the model number to i9000M
I will also post the modified version of update.zip
btw this version of update.zip only works if you have stock rom.
leegoon84 said:
the reason why update doesn't work is because you need to change the model number to i9000M
I will also post the modified version of update.zip
btw this version of update.zip only works if you have stock rom.
Click to expand...
Click to collapse
I have the stock rom of the i9000 euro version, could I update it with the update.zip and how do I that?
ThX
audino said:
I have the stock rom of the i9000 euro version, could I update it with the update.zip and how do I that?
ThX
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=728754
I would try root for 2.1 (if your stock rom is 2.1)
leegoon84 said:
I will re up the file.
Btw if you still have the stock rom and it doesnt go into download mode
i insist that you get your phone exchanged
what if it gets bricked? Then you cant restore it anymore because you need debug mode for adb
Click to expand...
Click to collapse
I went back.. and tried 5 phones they have in stock non of them will go into the download mode well doing holding down the power,volume,home combination.
Hey,
I recently bought this phone Huawei U8500, and I had a long search on the net where can I get a working recovery, finally I found a modified clockworkmod recovery.
It seems that this phone is highly unpopular.
I just wanted to share my finding.
Here you can download this modified version: Download
Steps to install recovery:
1. Download the clockworkmod
2. Unrar it somewhere on your computer
3. Turn off your phone
4. Press & Hold volume down key + call end (red) key and then press power key.
5. Launch the .bat file on your computer + connect your phone via USB
6. When it's finished, take out the battery and wait 5 seconds before putting it back in
7. Then you can access the recovery by holding volume up key + call(green) key
---------------------------------------------------------------------------------------
One thing I can recommend If your phones android build version doesn't end with "712", I suggest you to update it to the beta release, you'll have more functional dual-touch.
Here is the beta froyo update: Download
To install it:
1. Unrar it to your computer, and find a folder named "dload" with the biggest size.
2. Copy that "dload" filder to root of your SD card
3. turn off phone
4. Hold volume up key + end call (red) key and the press power key. Wait for it to load, it will say something like "Updating system" Wait for it to finish, if it says fail, just try again
5. After it says "Update complete" or "Update successful" just restart your phone and you'll have the new beta firmware.
--------------------------------------------------------------------------------------
In the Russian site I found some unofficial ROM's too.
I haven't tried them yes but if someone is willing here you can download them:
Firmware 2.2 29.01.2011 by Pavlo78
u8500_mao_rls7b2
u8500_mao_rls7++by_march_2
u8500_mao_rls8_by_march
u8500_mao_rls8_by_march
To install one of these ROM's do the following:
1. Copy the ZIP file on root of your SD card, the ZIP file, not RAR.
2. Boot up your phone in recovery mode (by holding volume up key + call(green) key)
3. With your optical trackpad select "Install zip from sd card"
4. From the list choose your ZIP file
5. And then just wait till the installation is complete and then just restart the phone!
------------------------------------------------------------------------------------------
I highly recommend you to back up the original firmware before installing new ROM's
You can do that in recovery mode, just click on nandroid and follow the on screen instructions it will backup your current firmware + your currently installed apps.
I'm not responsible for bricking your phone, if something doesn't go well. By doing the things I wrote, you may void your phones warranty.
Don't forget to thank me
Kind regards
xcoder_123
Bro, may i have to wipe all data via recovery like slash,cache and dalvik cache before i install froyo beta?
This is really helpful...a lot of Bangladeshis will be needing this. Telenor just launched this phone here.
I am using Huawei U8500 (Local branded as GrameenPhone Crystal). I have backed up my current ROM using ROM Manager. Can anyone confirm that the back-up ROM contains all the information including the Customized Branding???
Grameenphone Crystal Firmware U8500
In case You messed up
U8500 V100R001BGDC128B277 (Bengal GP)
Code:
//huaweidevice.com/worldwide/downloadCenter.do?method=downloadFile&flay=software&fileName=38766&attachmentName=U8500V100R001BGDC128B277.zip
monirr said:
In case You messed up
U8500 V100R001BGDC128B277 (Bengal GP)
Code:
//huaweidevice.com/worldwide/downloadCenter.do?method=downloadFile&flay=software&fileName=38766&attachmentName=U8500V100R001BGDC128B277.zip
Click to expand...
Click to collapse
Hi Monirr,
Can u confirm whether the link u provided is for only software upgrade or I can use it as a complete ROM backup (So that I can use it later in case of any failure to Upgrade the OS)
SAJUSIGMA said:
Hi Monirr,
Can u confirm whether the link u provided is for only software upgrade or I can use it as a complete ROM backup (So that I can use it later in case of any failure to Upgrade the OS)
Click to expand...
Click to collapse
Yah This one is the complete stock rom. I checked and found gps preloaded rom and this one is identical.
So no worry about Warranty. just load it when you need to go to gps Customer care.
monirr said:
In case You messed up
U8500 V100R001BGDC128B277 (Bengal GP)
Code:
//huaweidevice.com/worldwide/downloadCenter.do?method=downloadFile&flay=software&fileName=38766&attachmentName=U8500V100R001BGDC128B277.zip
Click to expand...
Click to collapse
10x a lot, monirr, I waz searchin this stock rom ... & do u kno if itz upgradeable 2 Android 2.3.4 or any1 upgraded?
hey im thinking bout buying this phone as i live in bangladesh... can anyone confirm me about the froyo upgrade does it work???
I did download the beta firmware.
And updated the phone's firmware a few minutes ago.
I have the dual touch now, yay (and a little better keyboard).
Many thanks from a Droid noob.
This should be enough for all your stock rom needs.
http://wiki.modaco.com/index.php/Huawei_Firmware_U8500
BTW: If you install the clockwordmod, you will lose the GP stock bootup screen (not the boot animation). So if you are going to claim warranty make sure you flash the GP firmware before you go to the GP centre.
Someone was asking how this phone is...the only issue I have is knowing that I'll never have flash on this thanks to the arm6 processor.
monirr said:
In case You messed up
U8500 V100R001BGDC128B277 (Bengal GP)
Code:
//huaweidevice.com/worldwide/downloadCenter.do?method=downloadFile&flay=software&fileName=38766&attachmentName=U8500V100R001BGDC128B277.zip
Click to expand...
Click to collapse
To upgrade my gp crystal to 2.2 , which one is best rom to download?
or can this model is upgradable to 2.3?pl help.
taavu said:
I did download the beta firmware.
And updated the phone's firmware a few minutes ago.
I have the dual touch now, yay (and a little better keyboard).
Many thanks from a Droid noob.
Click to expand...
Click to collapse
which version you download in which model
taavu said:
I did download the beta firmware.
And updated the phone's firmware a few minutes ago.
I have the dual touch now, yay (and a little better keyboard).
Many thanks from a Droid noob.
Click to expand...
Click to collapse
which beta firmware you download in which model?
ROBINGAZI said:
This should be enough for all your stock rom needs.
http://wiki.modaco.com/index.php/Huawei_Firmware_U8500
BTW: If you install the clockwordmod, you will lose the GP stock bootup screen (not the boot animation). So if you are going to claim warranty make sure you flash the GP firmware before you go to the GP centre.
Someone was asking how this phone is...the only issue I have is knowing that I'll never have flash on this thanks to the arm6 processor.
Click to expand...
Click to collapse
in gp crystal, through rom manager, if i install clockwordmod then a phone list appear , but there no option of this model(u8500). How can i install?
mostafiztuhin said:
in gp crystal, through rom manager, if i install clockwordmod then a phone list appear , but there no option of this model(u8500). How can i install?
Click to expand...
Click to collapse
see the first post of this thread.
mostafiztuhin said:
To upgrade my gp crystal to 2.2 , which one is best rom to download?
or can this model is upgradable to 2.3?pl help.
Click to expand...
Click to collapse
There is a thread in the port section of the Cyanogenmod forum. It started with a lame question but later a lot was discussed about gingerbread 2.3.4. There is a Chinese developer (Slax) who has been working on the rom. However, this rom does have a few issues.
I don't know Chinese and google translate is incomprehensible. You should be able to find all the links needed in the cyanogenmod forum.
here is the link.
http://forum.cyanogenmod.com/topic/21467-huawei-u8500/
for froyo try trial and error with all the official roms. if you don't like one change it. eventually you will find one that meets your need.
monirr said:
In case You messed up
U8500 V100R001BGDC128B277 (Bengal GP)
Code:
//huaweidevice.com/worldwide/downloadCenter.do?method=downloadFile&flay=software&fileName=38766&attachmentName=U8500V100R001BGDC128B277.zip
Click to expand...
Click to collapse
Dear bro,
This link doesn't work. Pls, help me with a active link.
Thanks in advance.
Hello XCoder, and all!
I try this steps, but i stopped after 4th step...
I get a boot logo, and the XP can't recognize droid, unknown device.
than the .bat file just wait for connection.
i try lot of drivers (original U8500, Original Android, and the SDK's driver too) and still "unknown Andoid device"
If i get out battery, take back, and standard Power On, the XP recognize the "Android Composite ADB" device, and bind the SD card, and CDROM image, and works perfectly.
but i can't upgrade in Standard Mode
can anyone have an idea, how i can access the Droid under Recovery Mode?
and all links of huaweidevice.com are unavailable
have new link?
regards, QSoft
qsoft73 said:
Hello XCoder, and all!
I try this steps, but i stopped after 4th step...
I get a boot logo, and the XP can't recognize droid, unknown device.
than the .bat file just wait for connection.
i try lot of drivers (original U8500, Original Android, and the SDK's driver too) and still "unknown Andoid device"
If i get out battery, take back, and standard Power On, the XP recognize the "Android Composite ADB" device, and bind the SD card, and CDROM image, and works perfectly.
but i can't upgrade in Standard Mode
can anyone have an idea, how i can access the Droid under Recovery Mode?
and all links of huaweidevice.com are unavailable
have new link?
regards, QSoft
Click to expand...
Click to collapse
I have same problem here
As I wrote the guide I realized the files, scripts, and images are scattered through multiple threads, which makes finding what you need difficult, even from a main thread (the guide for example). This was compounded even more when I was writing the CM9 Install Guide for the CyanogenMod Wiki and listed the commands themselves, it became huge, intimidating, and looks extremely daunting, I can only imagine what a new flasher must think seeing it! And and so I decided perhaps I can fix this, and with that I present to you...
The A100 Flashing Toolkit!
What is it?
A single zip file that, when unzipped, contains EVERYTHING you need, ADB, fastboot, scripts, CWM recovery image, everything you need to take your stock ICS A100 through rooting, unlocking the bootloader, and flashing CWM recovery (twrp coming soon)!
How is it used?
Its a set of 6 PC scripts, 3 for windows users (.bat) and 3 for linux users (.sh). Run in order from the same folder, and you can just click and run, reboot, click and run, reboot, click and run, install custom rom, done!
You MUST already be on ICS! This is not for HC, if you are on HC update to ICS FIRST!
Instructions
Make sure you are on ICS! Read the bold red letters above! You have been warned! You should already have installed the Acer USB drivers for ADB to work.
Ok, now you're on ICS....right?
Download and unzip the file to whatever folder you can remember, for example c:\acer or ~/acer.
Open your file manager of choice and browse on over to where you unzipped the files, and get ready.
Windows
Right click on A100-root-win.bat and select Run as Adminitrator.
Once that is finished, let your tablet reboot.
Once it's rebooted, right click on A100-unlock-win.bat and select Run as Administrator.
Once this finishes, let the tablet reboot again (the script will tell you what's happening)
Once it's rebooted, right click on A100-recovery-win.bat and select Run as Administrator.
Allow it to finish, it'll reboot a couple times.
Half the time it reboots into recovery, other reboots into system, not sure why it happens.
If it boots into recovery, go ahead and make a full backup, might as well.
If it boots into system, reboot into recovery and make a full backup, might as well.
At this point, you can now wipe and install a custom ROM, see the A100 Guide in General for ROMs and instructions on this.
Linux
Execute A100-root-linux.sh and allow it to run.
Once that is finished, allow tablet to reboot.
Exectute A100-unlock-linux.sh and allow it to run.
Let the tablet reboot
Execute A100-recovery-linux.sh and allow it to run.
It'll either reboot into recovery, or system, it does one or the other for some reason.
If rebooted into recovery, make a full backup.
If rebooted into system, reboot into recovery and make a full backup.
Wipe and install a new custom ROM, see the A100 Guide in General for ROMs and instructions on this.
How to boot into recovery
There's a few ways, 1 way is an app like quick boot, you can use adb by typing adb reboot recovery or you can do it manually.
Power off the tablet.
Press and hold the volume - button, closest to power and lock switch.
Holding volume - press and hold Power.
Hold until the screen says Booting recovery kernel then let go.
You should be in recovery, either CWM, TWRP, or stock, whatever you have installed.
As always I am open to suggestions, advice, or reports! Feel free to post up or PM me with any issues, questions, bugs, or ideas!
Download
A100 Flash Toolkit 1.1 7-16-12
Now featuring the correct bootloader!
Thanks to smokku for pointing this out.
Who do we thank for this package?
ZeroNull: Alot of the scripting is based on his work, and borrows his ADB and fastboot executables.
ptesmoke: Uses his CWM recovery.img file
CyanogenMod Iconia Team: For allowing me the chance to write for the Wiki, and realizing this NEEDED to be done.
Anyone else I'm forgetting, I'm sorry I will add you as soon as I remember (feel free to drop me a note!)
Sounds great, many thanks.
Thanks for all you hard work and patience.
a100 flash program
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Birbey said:
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Click to expand...
Click to collapse
Oh wow OK I'll take a look I must have mixed everything up. My desktop is littered with files from all these projects. I'm sorry about that I should have double checked everything before I uploaded it. If the called files are different then the scripts it must be the old version mixed with new scripts or something. I should have it squared away sometime tonight/tomorrow morning.
Edit: I'm assuming by saying command prompt you use windows, the a100-root-win.bat file looks fine, was this one giving any issues?
I'm checking the second and third now for whatever is going on.
Tapatalked from my Galaxy S II.
Fixed.
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
diegof18 said:
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
Click to expand...
Click to collapse
You have to be FAST when it gets there, it times out in like half a second it seems.
When you run it, have the tab in your hand, fingers on volume - and volume + (volume - is next to the lock switch). As soon as you see the screen change, hit volume - then volume +. It takes a few tries usually. It'll just sit there until you reboot afterwards.
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
elander said:
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
Click to expand...
Click to collapse
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
thanks for the info.
pio_masaki said:
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
elander said:
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
Click to expand...
Click to collapse
I'm not sure, but I don't think resetting these puts them back to 100% if rooted, the root stays since it sits in /system. You'll have to manually remove SU then reset to get rid of the root, I think. Other option is restore through the update.zip method which should wipe /system. You could try a hard reset and see if it removes SU or not, it might.
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
NeO_CooL said:
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
Click to expand...
Click to collapse
Not quite clear on what you're asking, but as far as I know it should work on any version bootloader unless they changed it on some update, which wouldn't surprise me.
What is the whole message, and when is it occuring?
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
NeO_CooL said:
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
Click to expand...
Click to collapse
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Forgot to say i´m using the windows version.
Thanks
pio_masaki said:
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Click to expand...
Click to collapse
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 (not unlockable) bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
smokku said:
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 not unlockable bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
Click to expand...
Click to collapse
It's just labeled a100, it isn't the actual a100 blob. But go ahead and use that link until I get the chance to go back through it, I'm obviously messing it all up somewhere, I may have used the a100 blob and gotten it mixed up with the a200 blob when I was renaming and shifting things around. I'll pull the download for now until I get the chance to get it all sorted out, sorry guys.
Edit OK its back up with the proper boot loader for unlocking. I can't believe I did that. Huge thanks to smokku for pointing that out!
No worries.
And yeah, you have to be quick when it asks to toggle unlock, like half a second quick.
Hello.
So my N7100 doesn't connect to mobile network. No voice calls, text messages or mobile internet. Wifi works just fine, although signal seems to be a little weaker (maybe just my imagination).
What I did and how it happened:
I got sick of Samsung being assholes and not pushing out software updates, so I decided to flash some custom ROM. I choose CM, because they had that "one click installation", so I didn't have to do a lot of work. After a week of using CM I decided that it sucks and wanted back my original android with all gimmicks from Samsung, mostly because battery life with CM was terrible, not even one day. And that's when everything went downhill. I downloaded and installed firmware for Baltic region, because I live here and I bought my phone here. From that moment my phone stopped being phone and evolved into wifi only tablet. After being very pissed and trying to flash couple different roms I gave up. Found my phones original box user manual and other papers. It turns out that my phone is made for Hungary region. So shop where I bought it must have imported wrong models (most likely cheaper for bigger profit). Flashing original for Hungary made firmware doesn't resolve this issue.
Guys, I really need help. I just want to return to stock - original firmware and reset flashing counter. Please help, and if possible in layman's terms...
EddsLV said:
Hello.
So my N7100 doesn't connect to mobile network. No voice calls, text messages or mobile internet. Wifi works just fine, although signal seems to be a little weaker (maybe just my imagination).
What I did and how it happened:
I got sick of Samsung being assholes and not pushing out software updates, so I decided to flash some custom ROM. I choose CM, because they had that "one click installation", so I didn't have to do a lot of work. After a week of using CM I decided that it sucks and wanted back my original android with all gimmicks from Samsung, mostly because battery life with CM was terrible, not even one day. And that's when everything went downhill. I downloaded and installed firmware for Baltic region, because I live here and I bought my phone here. From that moment my phone stopped being phone and evolved into wifi only tablet. After being very pissed and trying to flash couple different roms I gave up. Found my phones original box user manual and other papers. It turns out that my phone is made for Hungary region. So shop where I bought it must have imported wrong models (most likely cheaper for bigger profit). Flashing original for Hungary made firmware doesn't resolve this issue.
Guys, I really need help. I just want to return to stock - original firmware and reset flashing counter. Please help, and if possible in layman's terms...
Click to expand...
Click to collapse
Press *#06# and see if your EMEI is fine... If it says something like 000000000049 it seems to be bugged and you can try this solution:
I flashed the firmware N7100XXDMF2_N7100OLBDMD2_XME using ODIN PC and follow the below using root explorer:
- copy /efs/ to the sdcard
- delete /efs/
- reboot (after reboot I got the yellow recovery mode window floating over, no lock screen, and pressing power button turns the phone off directly)
- /efs/ will be autocreated again. copy the efs folder from the sd card to / (root explorer will tell you that the folder already exists and it will merge them)
- reboot
PS: I did not have an /efs/ backup before applying the above.
Click to expand...
Click to collapse
I saw from another post. Im going to try this too since Im having the same problem as you.
Find your ROM here: http://www.sammobile.com/firmwares/1/?model=GT-N7100&pcode=CHE#firmware I selected Chile Entel, but you can choose your country and company, it is the original ROM and it should fix our problem, Im downloading the ROM by now.
To use Odin, just put your phone in download mode (vol up/down + home + power) and then plug in to your PC, open Odin and at "PDA" select your ROM, then put start and just wait a few minutes and it should be working again...
After this, you should make a back up of your EFS file using a root explorer and then flash with any ROM you want (Im trying Ditto 3, it seems to be a cool jelly bean) and after this flash, you should put your new EFS file... Just the problem that Im facing is how to put this backup since the EFS is a folder being readed all the time, so there should be a program to do this, but I cant figure this out yet.
My phone doesn't have any IMEI any more. "null/null" is value given by my phone after requesting IMEI. I already flashed original ROM, problem is still here.
About /efs/ I could backup it with "File Manager"app from google play, but I can't delete it, because it is in read only.
EddsLV said:
My phone doesn't have any IMEI any more. "null/null" is value given by my phone after requesting IMEI. I already flashed original ROM, problem is still here.
About /efs/ I could backup it with "File Manager"app from google play, but I can't delete it, because it is in read only.
Click to expand...
Click to collapse
Somehow you will have to access to edit it and you will be able to solve that problem... Otherwise go to technical service.
kito2 said:
Somehow you will have to access to edit it and you will be able to solve that problem... Otherwise go to technical service.
Click to expand...
Click to collapse
In order to delete /efs/ you have to be rooted, when you flash factory rom you loose root privileges.
EddsLV said:
In order to delete /efs/ you have to be rooted, when you flash factory rom you loose root privileges.
Click to expand...
Click to collapse
After flash factory rom is easy to make root again hehe.. Anyways keep reading and maybe you will find another solution, you can't be the only one who had that problem... Good luck my friend.
Try this link http://forum.xda-developers.com/showthread.php?t=1896696
kito2 said:
After flash factory rom is easy to make root again hehe.. Anyways keep reading and maybe you will find another solution, you can't be the only one who had that problem... Good luck my friend.
Click to expand...
Click to collapse
Thanks. So I rooted my phone and did all than you wrote above - copied, deleted, replaced. It didn't helped and now I have that yeleow recovery window all the time :/
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy