Related
Hi guys,
I rooted my arc using gingerbreak just to get rid of some bloatware. Then unrooted. Know I don't know wether I've accidentally deleted something I shouldn't have!?, but now every time I plug my phone into my laptop via usb, Sony pc companion isn't detecting my phone what so ever!
Is there anyway around this? Getting my phone back to factory state? I've tried a factory reset but no joy
Many thanks
you'll need to try to reflash the firmware. either using flash tool or SEUS.
Sent from The Arc!
im_iceman said:
you'll need to try to reflash the firmware. either using flash tool or SEUS.
Sent from The Arc!
Click to expand...
Click to collapse
Is it different the "Factory data reset" from re-flashing the firmware ????
After "Factory data reset" ..... my phone remain rooted (gingerbreak)..... If I re-flash the firmware can I return to "non rooted" mod????
@im_iceman .... Where you found Build 3.0.A.2.184 version???
TIA
yes..re flashing will restore the phone back to it's full out of the box state.. unless you've unlocked your bootloader? it won't do that... but suspect you haven't?
Sent from The Arc!
there are a few .184 firmwares on the dev section..
Sent from The Arc!
im_iceman said:
there are a few .184 firmwares on the dev section..
Sent from The Arc!
Click to expand...
Click to collapse
So if I re-flash the rom.... I will return to "non rooted" mod.... but my boot-loader will remain unlock... (I had unlocked it)....
Correct?
I am asking that because I am trying to find a solution to my problem (HDMI not working)
TIA
nsourtgr said:
So if I re-flash the rom.... I will return to "non rooted" mod.... but my boot-loader will remain unlock... (I had unlocked it)....
Correct?
I am asking that because I am trying to find a solution to my problem (HDMI not working)
TIA
Click to expand...
Click to collapse
My understanding is that you can no longer use SEUS once the bootloader is unlocked, but not entirely sure.
exactly ... once unlocked bootloader, you can not relock ... for now .....
and seus will no longer be able to do an update on it....
@nsourtgr
try to reinstall HDMi.apk packages for solve your problem
I think you should install com.sonyericsson.usbux, I've frozen it and my imac could not see my phone anymore, after I defrosted com.sonyericsson.usbux everything was back to normal again.
alesscam said:
exactly ... once unlocked bootloader, you can not relock ... for now .....
and seus will no longer be able to do an update on it....
@nsourtgr
try to reinstall HDMi.apk packages for solve your problem
Click to expand...
Click to collapse
Thank you my friend.... I tried .... but the problem exists!!!!!
The thing is that I haven't tried HDMI connection before gingerbreak... but I believe that gingerbreak caused the problem....
[Q].... If I flash the rom.... I know that my Arc will remain "bootloader unlocked" but what about "rooted"????
TIA
nsourtgr said:
Thank you my friend.... I tried .... but the problem exists!!!!!
The thing is that I haven't tried HDMI connection before gingerbreak... but I believe that gingerbreak caused the problem....
[Q].... If I flash the rom.... I know that my Arc will remain "bootloader unlocked" but what about "rooted"????
TIA
Click to expand...
Click to collapse
I think that reflashing the firmware, your Arc will not be rooted ...
do not know what does or does not gingerbreak(problem or not) because I've never tried ..... I rooted my Arc with system.img from binary and I never had any problems .....
Anyway make sure that HDMI was not a problem of your Arc ....
for any help we are here
im_iceman said:
you'll need to try to reflash the firmware. either using flash tool or SEUS.
Sent from The Arc!
Click to expand...
Click to collapse
Sorry, I'm a noob lol. How do I reflash the firmware??
Many thanks
gibbo82 said:
Sorry, I'm a noob lol. How do I reflash the firmware??
Many thanks
Click to expand...
Click to collapse
if you have bootloader LOCKED,you can reflash to SEUS from pc..
if you have bootloader UNLOCKED,read here :
http://forum.xda-developers.com/showthread.php?t=1047484
I Gingerbroke my ARC yesterday, and I checked connection to pc moment ago and companion detects it ufff
alesscam said:
if you have bootloader LOCKED,you can reflash to SEUS from pc..
if you have bootloader UNLOCKED,read here :
http://forum.xda-developers.com/showthread.php?t=1047484
Click to expand...
Click to collapse
How would I know if my bootloader was unlocked!?. My arc was sim free, so wasn't locked to any network. All I did was download the gingerbreak apk, which automatically rooted my phone, got rid of some bloatware, and then unrooted it. Now I'm having all these problems
Karooluss said:
I Gingerbroke my ARC yesterday, and I checked connection to pc moment ago and companion detects it ufff
Click to expand...
Click to collapse
I'm not sure wether I uninstalled something by accident when it was rooted via titanium pro. But pc companion isn't detecting my phone what so ever!
Is SEUS different to pc companion??
gibbo82 said:
How would I know if my bootloader was unlocked!?. My arc was sim free, so wasn't locked to any network. All I did was download the gingerbreak apk, which automatically rooted my phone, got rid of some bloatware, and then unrooted it. Now I'm having all these problems
Click to expand...
Click to collapse
Your Arc can only be unlocked if you did ,following the thread in this section ......
bootloader was release directly from Sony ...
... so I think you don't have unlocked...
In this way you can simply updating your Arc with SEUS software
i rooted my arc with gingerbreak. no issues with pc companion et all. but i am getting random frequent reboots. anyone else facing this problem. the reboots happen all the time while making/receiveing calls, browzing etc.
vsinha71 said:
i rooted my arc with gingerbreak. no issues with pc companion et all. but i am getting random frequent reboots. anyone else facing this problem. the reboots happen all the time while making/receiveing calls, browzing etc.
Click to expand...
Click to collapse
same situation till yesterday when i decided to do a factory reset. now my arc is ok.
I managed to do a restore via seus so got that sorted!
I would recommend not to use gingerbreak, as I had loads of problems,
When opening camera I would just get a black screen, I would hav to reboot the device
My lock security option became disabled!!
And.... Pc companion wouldnt recognise my device!
Hello guys! I need some help
I was flashing a stock firmware with kdz updater on my LG E400, following all instructions
Flashing goes through all the way and at the end i get:
Upgrade
error WParam: 100, LParam: 6
Phone boots and all but when i fix in my USB cable i don't see the icon in the status bar hence can't send files from computer or do Adb commands
I guess its USB bricked
Looked for solutions all over but they don't seem device specific and i fear bricking my phone for good
Any help is much appreciated!
Sent from my LG-E400 using xda app-developers app
have you try to do a hard reset after kdz flashing?
Code:
in off position, press n hold home + vol down + power buttons together. be sure you press that power button at the last one...
will be wipe your data, cache and internal sd partitions by doing this. if you have any important files in int-sd, then back it up first ( move it to ext-sd )
let see if it work or not.....
Cool. I'd done a factory reset and didn't fix it, let me the hard reset and see what comes out of it
Sent from my LG-E400 using xda app-developers app
Nah, factory reset doesn't do the trick. I'm stumped ..
Sent from my LG-E400 using xda app-developers app
let's hope that'd software problem. you just install any custom roms you like, and your problem should be fixed. but if it's not, then you have to send it to service center for fix that hardware....
good luck
OK. Thanks
Sent from my LG-E400 using xda app-developers app
Fixed it!
finally managed to fix it. Problem was with the firmware I was installing. I chose a firmware from another country of origin with a version that wasn't released for my phone's country. got the right kdz for my country and flashed it successfully fixing the brick.
I even managed to root it this time round! (the whole reason I flashed a different firmware in thw first place was because of failure to root)
Everything is good now. thanks to all that replied
tarnoldinho said:
finally managed to fix it. Problem was with the firmware I was installing. I chose a firmware from another country of origin with a version that wasn't released for my phone's country. got the right kdz for my country and flashed it successfully fixing the brick.
I even managed to root it this time round! (the whole reason I flashed a different firmware in thw first place was because of failure to root)
Everything is good now. thanks to all that replied
Click to expand...
Click to collapse
Can you elaborate? I am having the exact same problem.
install again the msxml before using kdz.. hope it works
★★★ [jellycast_forever] ★★★
DebanjanSahu said:
Can you elaborate? I am having the exact same problem.
Click to expand...
Click to collapse
if u did what I did and got USB brick, its from flashing the wrong kdz file. there's an app for finding the right kdz file by giving it just your serial number of the phone. it's what I used cause I wasn't sure of the right country of origin of my phone. try using that app, and flash the kdz like before. and make sure its a COMPLETE download. watch it all the way. try that
Using advice from http://forum.xda-developers.com/showpost.php?p=34700586&postcount=4 you can determine which firmware version to use based on your phone IMEI.
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Yorgo1982 said:
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Click to expand...
Click to collapse
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Apra24 said:
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Click to expand...
Click to collapse
wait sammobile if u r with rogers bell telus fido vmc koodo, and if with other carrier contact them with ur phone model and serial num so they will upload it ..
Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
Did you restore from CWM/TWRP?
Pikezer1337 said:
Did you restore from CWM/TWRP?
Click to expand...
Click to collapse
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Apra24 said:
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Click to expand...
Click to collapse
If you restored through TWRP there is a good chance that you are softbricked. There are restoring issues that mess with the system partition.
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Apra24 said:
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Click to expand...
Click to collapse
can u give the file name?
plz
Yorgo1982 said:
can u give the file name?
plz
Click to expand...
Click to collapse
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Apra24 said:
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Click to expand...
Click to collapse
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Yorgo1982 said:
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Click to expand...
Click to collapse
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I'm wondering if the official Bell/Rogers firmware will be available any time soon? Does it typically get released soon after the phone launch, or are they withholding it for some reason?
Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
eklipse1 said:
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
Click to expand...
Click to collapse
I was trying the Peru one for a while, but it kept hanging up during the bootup. The message was in a foreign language, but I'm assuming it was "initializing". It would initialize for about 3 minutes then an error message would pop up saying something is not responding.
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
eklipse1 said:
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I have been trying to. When I flash the firmware in odin, it reinstalls the stock recovery mod. Right after flashing firmware, it won't go into recovery mode on the first boot (first does some android robot install thing, then boots up). I attempted to install the TWRP recovery directly after the firmware, and then booting directly into recovery to factory reset, but I'm still getting a boot loop.
Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Yorgo1982 said:
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Click to expand...
Click to collapse
do they know it's rooted/void? Or did you somehow not trigger the knox/warranty void switch? I may just have to do the same thing...
Hi I'm on 4.4.2 GNG1 with stock rom and kernel on my N9005 rooted!
Today I was trying to set an unlock password without success... when I'm on settings and I wrote the selected password for the 2nd time the phone freeze and after 30 second the sd is unmounted and the phone has not password 4 unlock... I have tried all the option to protect my phone but always freeze and sd unmount... so I can set only swipe to unlock or the "nothing" option...
Anyone can help me?
sarcokiller said:
Hi I'm on 4.4.2 GNG1 with stock rom and kernel on my N9005 rooted!
Today I was trying to set an unlock password without success... when I'm on settings and I wrote the selected password for the 2nd time the phone freeze and after 30 second the sd is unmounted and the phone has not password 4 unlock... I have tried all the option to protect my phone but always freeze and sd unmount... so I can set only swipe to unlock or the "nothing" option...
Anyone can help me?
Click to expand...
Click to collapse
what is ur bootloader and modem version
xinfinityoO said:
what is ur bootloader and modem version
Click to expand...
Click to collapse
Bootloader: UENB4
Modem: UENB1
sarcokiller said:
Bootloader: UENB4
Modem: UENB1
Click to expand...
Click to collapse
well that mite be the problem.
you need to update to latest bootloader and modem.. at your own risk as i am not sure if it can be downgraded or not
but i have come across similar issues when using newer roms on older versions of bootloader and modem and the pin lock does not work
before doing anything make sure you have ur brick image, backup of ur rom, and efs partitions,
and as i said do it at your own risk..
are you rooted ? knox ??
xinfinityoO said:
well that mite be the problem.
you need to update to latest bootloader and modem.. at your own risk as i am not sure if it can be downgraded or not
but i have come across similar issues when using newer roms on older versions of bootloader and modem and the pin lock does not work
before doing anything make sure you have ur brick image, backup of ur rom, and efs partitions,
and as i said do it at your own risk..
are you rooted ? knox ??
Click to expand...
Click to collapse
Knox 0x1 and yes I'm rooted...
I came from two months of continuos flashing and now I'm on the stock rom installed by odin... what are the risks of update boot loader?
sarcokiller said:
Knox 0x1 and yes I'm rooted...
I came from two months of continuos flashing and now I'm on the stock rom installed by odin... what are the risks of update boot loader?
Click to expand...
Click to collapse
well there is no risk ..if you do it properly...but as i said its always good to have backups.. and your brick image on external sd card
its just that some ppl ..i have no idea why .. always want to downgrade to old bootloaders.. if you are not one of them.. then i would say go for it
xinfinityoO said:
well there is no risk ..if you do it properly...but as i said its always good to have backups.. and your brick image on external sd card
its just that some ppl ..i have no idea why .. always want to downgrade to old bootloaders.. if you are not one of them.. then i would say go for it
Click to expand...
Click to collapse
After the update and the reboot it should work fine right?
sarcokiller said:
After the update and the reboot it should work fine right?
Click to expand...
Click to collapse
yes, it should.. check after the update that the boatloader and modem did get updated
xinfinityoO said:
yes, it should.. check after the update that the boatloader and modem did get updated
Click to expand...
Click to collapse
Man thank you for the help! I have updated modem and bootloader and I think that the problem was the modem... because i have flashed first the new BL and the problem was the same... next with the flash of the modem all works fine!
So problem solved! thank you again!
I was installing TWRP and superuser and something failed. Now the phone soft resets and bounces between TWRP and Huawei eRecovery. Does anyone have a L29C567 firmware I can flash? I've done some searching and there doesn't seem to be any sources for the firmware yet. Just trying to get the phone working again.
I think I could use FunkyHuawei if they had the firmware but I don't believe they do yet.
Edit: Looks like I put this in the wrong sub forum, sorry
Please be patient. Soon enough it will be available.
JJBTEXAS said:
I was installing TWRP and superuser and something failed. Now the phone soft resets and bounces between TWRP and Huawei eRecovery. Does anyone have a L29C567 firmware I can flash? I've done some searching and there doesn't seem to be any sources for the firmware yet. Just trying to get the phone working again.
I think I could use FunkyHuawei if they had the firmware but I don't believe they do yet.
Edit: Looks like I put this in the wrong sub forum, sorry
Click to expand...
Click to collapse
When that happened to me I flashed the update_full_hw_spcseas.zip folder through dload (vol up + down + power) to get the phone booting again.
Try this guide,it will change ur region to Asia C636 but the phone will work 100%
You can rebrand later when official USA version is available.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page4
gm007 said:
Try this guide,it will change ur region to Asia C636 but the phone will work 100%
You can rebrand later when official USA version is available.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page4
Click to expand...
Click to collapse
Yes I did this last night but now I'm stuck on B110. When I tried to flash update_full_hw_spcseas.zip my update restore failed and I got stuck in the bootloop again. I was able to dload B110 again so the phone is running but not sure how to get to B136 or B138 or even B158.
JJBTEXAS said:
Yes I did this last night but now I'm stuck on B110. When I tried to flash update_full_hw_spcseas.zip my update restore failed and I got stuck in the bootloop again. I was able to dload B110 again so the phone is running but not sure how to get to B136 or B138.
Click to expand...
Click to collapse
Do you have all apps and themes installed or they are missing?
To update use system update,try with wifi and 4g, there is 3 dots in the upper right click download latest package.
gm007 said:
Do you have all apps and themes installed or they are missing?
To update use system update,try with wifi and 4g, there is 3 dots in the upper right click download latest package.
Click to expand...
Click to collapse
I lost all the google apps and the keyboard when I tried to updated from B110 to B136 using step 7 "flash hw_data" but got it all back when with dloading back to B110.
I'm trying the updater now and it seems to be updating to B158! will update.
Update worked and I'm now on B158 which is awesome! The only thing that's odd now is that my MEID is 000000000000. I'm not sure if that's a big deal.
To update use system update,try with wifi and 4g, there is 3 dots in the upper right click download latest package.
Click to expand...
Click to collapse
Any reason to use steps 5 - 9 instead of doing the update from B110?
JJBTEXAS said:
Update worked and I'm now on B158 which is awesome! The only thing that's odd now is that my MEID is 000000000000. I'm not sure if that's a big deal.
Any reason to use steps 5 - 9 instead of doing the update from B110?
Click to expand...
Click to collapse
Step 5 to 9 is to restore the Missing application and data i recommend do this steps again.
If you have boot loop boot to stock recovery and do factory reset.
gm007 said:
Step 5 to 9 is to restore the Missing application and data i recommend do this steps again.
If you have boot loop boot to stock recovery and do factory reset.
Click to expand...
Click to collapse
Hmm. I don't think I'm missing any applications though. I have all the google apps, which is what I lost last time I tried.
JJBTEXAS said:
Hmm. I don't think I'm missing any applications though. I have all the google apps, which is what I lost last time I tried.
Click to expand...
Click to collapse
Did you tried a factory reset from settings?
If that didn't restore ur meid than maybe you need to flash the public data zip,will give you link later.
JJBTEXAS said:
Hmm. I don't think I'm missing any applications though. I have all the google apps, which is what I lost last time I tried.
Click to expand...
Click to collapse
sorry but can i ask if you have restore the oeminfo to c636?
eddmecha said:
sorry but can i ask if you have restore the oeminfo to c636?
Click to expand...
Click to collapse
Yes. I did the following:
* Unlock bootloader
* install twrp
1- restore oeminfo for C636 http://www.mediafire.com/?szws87sk7rrkqr6
2- download c636 offline firmware,and flash it from an sd card using 3 buttons method by dload folder. https://forum.xda-developers.com/mat...4/post70465883
3- factory reset from settings.
4-use system update to get the latest firmware.
Basically gm007's but skipping a few steps
The end result was a seemingly complete L29C636B158.
gm007 said:
Did you tried a factory reset from settings?
If that didn't restore ur meid than maybe you need to flash the public data zip,will give you link later.
Click to expand...
Click to collapse
Yes, I believe I did. Is there any reason for me to fix the meid?
JJBTEXAS said:
Yes, I believe I did. Is there any reason for me to fix the meid?
Click to expand...
Click to collapse
If everything is working fine no need, maybe later if you decide to rebrand to original usa version.
gm007 said:
If everything is working fine no need, maybe later if you decide to rebrand to original usa version.
Click to expand...
Click to collapse
That's what I was thinking. I might try another factory reset just to test it.
JJBTEXAS said:
That's what I was thinking. I might try another factory reset just to test it.
Click to expand...
Click to collapse
Could be cause u skiped step 5 there is a mismatch in system files.
The update you got via system update is a small update or full firmware?
gm007 said:
Could be cause u skiped step 5 there is a mismatch in system files.
The update you got via system update is a small update or full firmware?
Click to expand...
Click to collapse
Reset didn't solve it. I think the update was over 2gb so full firmware.
ajsmsg78 said:
When that happened to me I flashed the update_full_hw_spcseas.zip folder through dload (vol up + down + power) to get the phone booting again.
Click to expand...
Click to collapse
hi bro how do u manage that can u full explain ?
Sorry to resurrect the old thread but I am having the same problem with meid number all zeros. The phone seems to work fine except that I cannot get LTE or 4G on certain provider's. Mine is also the US version. What did you do to fix this issue?