Related
I installed a bad apk (rc from a developer) and now even after uninstall and clearing the data the phone keeps on stuttering and hanging, freezing, ...
I fear a factory reset won't be enough to fix this. Also to be sure I would like to do a factory format instead.
I already tried the *2767*3855# dial code, but this doesn't work for the P880.
Anyone knows how to reflash (factory format) the ROM? But from within the phone.
Preferably not by flashing the kdz files, looks to risky to me.
Arne_B said:
I installed a bad apk (rc from a developer) and now even after uninstall and clearing the data the phone keeps on stuttering and hanging, freezing, ...
I fear a factory reset won't be enough to fix this. Also to be sure I would like to do a factory format instead.
I already tried the *2767*3855# dial code, but this doesn't work for the P880.
Anyone knows how to reflash (factory format) the ROM? But from within the phone.
Preferably not by flashing the kdz files, looks to risky to me.
Click to expand...
Click to collapse
RuedasLocas said:
What is your problem @Arne_B ?
If you're having problems with some apps or settings of the latest version, its enough when you downgrade to the earlyest one and do the factory reset.
The phone will reset everything from the latest version.
After that, you can upgrade again to the latest having a clean install, the phone will overwrite the files from the earlier version.
Click to expand...
Click to collapse
Also...
RuedasLocas said:
Its very easy to flash the phone, the thread is a little confuse cause a lot of users have different problems and doubts.
The steps are easy.
Download the "kdz-update" folder from the link on that thread
Download the FW version that you want.
Install "msxml" (from the kdz-update folder)
Run and turn ON the "Windows Enabler" (from the kdz-upload folder)
Take out the battery
Press "Vol-" and while pressing connect phone to computer untill you see on the phone screen "FW update"
Run "UpTestEX_mod2_marwin". Settings:
"Select type">>>>>>>>>>>CDMA - SmartPhone(WM)
"Work Directory">>>>>>>> The kdz-upload folder where is better to put the kdz FW files inside
"Select model.dll">>>>>>>>Choose from the kdz-upload folder ther file "X3_2008_v0.0.6.9.dll" or "P880.dll", both of them work fine
"PhoneMode">>>>>>>>>>>EMERGENCY
"Select kdz file">>>>>>>>> Choose the V10x that you download
Click on "Start Upgrade"
The program will start with the kdz file extraction, after a few seconds you'll see on the log that it start to write on the phone, thats when you need to put back the battery on the phone.
Just need to wait about 3-5 minutes and its done :victory:
The other way is using the Official tool but latest FW for Turkey is V10C soo, its useless for you...
Click to expand...
Click to collapse
RuedasLocas said:
What is your problem @Arne_B ?
If you're having problems with some apps or settings of the latest version, its enough when you downgrade to the earlyest one and do the factory reset.
The phone will reset everything from the latest version.
After that, you can upgrade again to the latest having a clean install, the phone will overwrite the files from the earlier version
Click to expand...
Click to collapse
I did install an earlier version, cleared data and uninstalled, rebooted the phone and installed the newest Play Store version (not the rc version) again but still had the problems.
Anyways, I tried to fix it manually by first uninstalling the app again. Then went to my root explorer and search in my phone (/ folder) for files related to the app name and deleted all those. Rebooted the phone, installed the latest app version from play store and for now all works well again. But didn't test the phone completely yet.
RuedasLocas said:
Also...
Click to expand...
Click to collapse
I know, but I read somewhere that LG checks your phone when flashing the Firmware, and doing it that way they know the phone was bricked due to rooting or other 'out of warranty' things..
Or am I totally wrong on this aspect?
Arne_B said:
I did install an earlier version, cleared data and uninstalled, rebooted the phone and installed the newest Play Store version (not the rc version) again but still had the problems.
Anyways, I tried to fix it manually by first uninstalling the app again. Then went to my root explorer and search in my phone (/ folder) for files related to the app name and deleted all those. Rebooted the phone, installed the latest app version from play store and for now all works well again. But didn't test the phone completely yet.
I know, but I read somewhere that LG checks your phone when flashing the Firmware, and doing it that way they know the phone was bricked due to rooting or other 'out of warranty' things..
Or am I totally wrong on this aspect?
Click to expand...
Click to collapse
Flashing or rooting the phone (like we explain!!!) don't brick your phone.
Forget about what you read.
And if you have some problem and need to go to LG warranty, just need to flash the phone with the Official Tool.
RuedasLocas said:
Flashing or rooting the phone (like we explain!!!) don't brick your phone.
Forget about what you read.
And if you have some problem and need to go to LG warranty, just need to flash the phone with the Official Tool.
Click to expand...
Click to collapse
Plus, modifying the software doesn't void your warranty; there was some new EU ruling about that, i read it a few weeks ago. The KDZ flashing method isn't even something inofficial, as it is also used by LG. So just fix it that way.
RuedasLocas said:
Flashing or rooting the phone (like we explain!!!) don't brick your phone.
Click to expand...
Click to collapse
I know. But LG can start lacking in support of they know the phone is or was rooted in the past.
muellersmattes said:
it is also used by LG.
Click to expand...
Click to collapse
Ok didn't know that.
I'll just do it that way than when the phone keeps on acting weird.
Hi everyone.
I've got to this bad situation where I wiped my IMEI. I was trying to flash CyanogenMod, and it flashed fine except that IMEI was turning into zeroes and radio did not worked. Reverting back to stock ROM helped pretty much, it worked there. So, I decided to back up EFS prior to flashing again. I did it on a rooted stock firmware using online nandroid backup from market. It told me that backup was done fine, and I did not actually check, which was a huge mistake. I reflashed CM, gapps, and then that backup. Obviously, as that backup did not really contain anything, CM did not start. Original firmware flashed by Odin starts up, however, I immediately get "blahblah.gapps failed to start", I cannot connect to wifi because I cannot enter my password for Wifi - kayboard doesn't show up (if I remove the password on router, it connects fine). If I proceed, SetupWizard just crashes.
So, without backup, the only thing I can do is possibly flash EFS from another S Advance i9070P. I know that it would contain others' IMEI, but I can swear I fist change it before flashing. Or, if anybody's willing to help, you can just replace your IMEI with something generic but recognizable, as 123456789012345 for example. I'd try to deal with it.
Or, if there's any other suggestion, I'd gladly listen.
Venseiiz said:
Hi everyone.
I've got to this bad situation where I wiped my IMEI. I was trying to flash CyanogenMod, and it flashed fine except that IMEI was turning into zeroes and radio did not worked. Reverting back to stock ROM helped pretty much, it worked there. So, I decided to back up EFS prior to flashing again. I did it on a rooted stock firmware using online nandroid backup from market. It told me that backup was done fine, and I did not actually check, which was a huge mistake. I reflashed CM, gapps, and then that backup. Obviously, as that backup did not really contain anything, CM did not start. Original firmware flashed by Odin starts up, however, I immediately get "blahblah.gapps failed to start", I cannot connect to wifi because I cannot enter my password for Wifi - kayboard doesn't show up (if I remove the password on router, it connects fine). If I proceed, SetupWizard just crashes.
So, without backup, the only thing I can do is possibly flash EFS from another S Advance i9070P. I know that it would contain others' IMEI, but I can swear I fist change it before flashing. Or, if anybody's willing to help, you can just replace your IMEI with something generic but recognizable, as 123456789012345 for example. I'd try to deal with it.
Or, if there's any other suggestion, I'd gladly listen.
Click to expand...
Click to collapse
Did you do factory reset and wipe cache? Go back to stock with flashing stock firmware. That: "blahblah.gapps failed to start" is because of wrong version of GAPPS installed.
shut_down said:
Did you do factory reset and wipe cache? Go back to stock with flashing stock firmware. That: "blahblah.gapps failed to start" is because of wrong version of GAPPS installed.
Click to expand...
Click to collapse
Oh but I did, maybe 5 times already... Stock recovery shows: E: failed to mount /efs (Invalid argument)
I had this problem once. Took a downgrade to gingerbread to fix mine. May wwant to try that.
Sent from my S Advance because I can
bobfrantic said:
I had this problem once. Took a downgrade to gingerbread to fix mine. May wwant to try that.
Sent from my S Advance because I can
Click to expand...
Click to collapse
Hm, tried this today. It won't start at all. Showing just its logo all the time.
Venseiiz said:
Hm, tried this today. It won't start at all. Showing just its logo all the time.
Click to expand...
Click to collapse
With a guide to downgrade, not just flash any GB firmware.
http://forum.xda-developers.com/showthread.php?t=2100642
shut_down said:
With a guide to downgrade, not just flash any GB firmware.
http://forum.xda-developers.com/showthread.php?t=2100642
Click to expand...
Click to collapse
I was going to show that guide, thanks for beating me to it LOL
Wow, guys, thank you very much! It worked! Many-many thanks :laugh::good:
Venseiiz said:
Wow, guys, thank you very much! It worked! Many-many thanks :laugh::good:
Click to expand...
Click to collapse
Glad to read that... and this is my 1000th post, LOL.
bobfrantic said:
Glad to read that... and this is my 1000th post, LOL.
Click to expand...
Click to collapse
Hey, time to rise the topic again. After I repaired my phone, after some time I decided to flash a rom for a different region, 2.3.6 also (i did not update it to 4.1.2 anymore). I used ODIN 3.07. But now it does not turn on. At all. It does not react to the power button. No vibration, nothing. No recovery mode, no odin mode. Looks like a complete brick. Why the hell is that?!
Ah, by the way, as I stated in my first post, it's NFC model. The downgrade guide was for non-NFC. So I did not have any NFC functionality after downgrade. Here I wanted to return it as well, so I used a FW for i9070P version. Never had an idea it wouldn't turn on after that.
What can I do?
is it possible???
Hi. I ve experienced the same problem, except tht I ve completely lost IMEI and baseband. Sent it for repair.the person said 1st we ll recover the baseband then IMEI would b recovered. Blv me its been 2 weeks now. I ve read every possible solution I could find but it didnt help. As far as i could understand, IMEI has to b there for baseband to recover. Tried efs pro. Tried 9 steps for IMEI recovery but nothing helped. Tried to downgrade to GB acc to the guide but repartition fails on ODIN 1.85. Used triangle away to reset counter.the counts turn 0 with device status 'samsung official' but as soon as I flash stock JB, the current binary shows custom. IMEI folder in efs is empty. Tried to do the complex methods but got scared coz rest of the fone is f9. Is it possible tht it will be repaired or not. Is there a way out?
I'm requesting someone find the Odin files to flash to an i537 model for KitKat 4.4.2, as I can't find it anywhere. If I can't, I'll go to Samsung at Best Buy and uh..... Ask for the Odin files(they use Odin there XD)
Please help as ODIN is the only way I have been able to update, OTAs fail and recovery install from cache, external SD fails. Everything but Odin fails, so anybody help?
Device details-
SGH-i537 AT&T running 4.3 Official Unrooted Stock
Thanks!!!
Have you tried flashing the 4.3 firmware then flashing the OTA? At this time I don't think they have released a full Odin 4.4.2
popfan said:
Have you tried flashing the 4.3 firmware then flashing the OTA? At this time I don't think they have released a full Odin 4.4.2
Click to expand...
Click to collapse
Yeah, I tried it all my friend, I need the Odin files.
yes i too in fact need the odin files asap. I know nobody likes being asked for ETA's but how long does it usually take to get the ODIN files?
jimmietilt said:
yes i too in fact need the odin files asap. I know nobody likes being asked for ETA's but how long does it usually take to get the ODIN files?
Click to expand...
Click to collapse
Considering we never got the Odin files for MF2 or MF3, we may never get Odin files for NC9.
Just do a hard reset (VOL+/HOME/POWER), boot your phone then do a Factory reset from within the phone with selecting format SD card option (back your stuff up!). Then go back, enable USB debugging and flash the stock ML2 firmware EXCEPT for the BL file! then re-enable USB debugging and download the 2400258.cfg file from here, rename it to update.zip and flash it via stock recovery, problem solved. As for the ODIN files, here's a good read on why @Devo7v is right with his assessment on not ever seeing them. More info on the stock SGH-i537 firmware here.
jkeuclid said:
Just do a hard reset (VOL+/HOME/POWER), boot your phone then do a Factory reset from within the phone with selecting format SD card option (back your stuff up!). Then go back, enable USB debugging and flash the stock ML2 firmware EXCEPT for the BL file! then re-enable USB debugging and download the 2400258.cfg file from here, rename it to update.zip and flash it via stock recovery, problem solved. As for the ODIN files, here's a good read on why @Devo7v is right with his assessment on not ever seeing them. More info on the stock SGH-i537 firmware here.
Click to expand...
Click to collapse
I tried that. Didn't work XD The only thing that works for me is forcing the update through ODIN.
Devildude24 said:
I tried that. Didn't work XD The only thing that works for me is forcing the update through ODIN.
Click to expand...
Click to collapse
How are you forcing the update through Odin? We don't have the Odin files for 4.4.2, so I'm not sure what you mean. Do you mean you can only flash the 4.3 files with Odin and you cannot get the cfg file to flash through stock recovery?
Devo7v said:
How are you forcing the update through Odin? We don't have the Odin files for 4.4.2, so I'm not sure what you mean. Do you mean you can only flash the 4.3 files with Odin and you cannot get the cfg file to flash through stock recovery?
Click to expand...
Click to collapse
Yes, sorry for the confusion. I forced 4.3 through ODIN and the cfg file doesn't work, in all possible ways. And it won't work when renamed to update.zip either.
Devildude24 said:
Yes, sorry for the confusion. I forced 4.3 through ODIN and the cfg file doesn't work, in all possible ways. And it won't work when renamed to update.zip either.
Click to expand...
Click to collapse
Did you check the MD5 to make sure that it downloaded properly? My suggestion would be to download it with a computer, rename it to "update.zip" on a computer, copy it to your internal memory on the phone, and flash it through stock recovery. This should work, what errors do you get when you try to flash it? You're on stock 4.3 when you try to update, correct? In order to flash the OTA you cannot be rooted or have modified the system in any way.
Devo7v said:
Did you check the MD5 to make sure that it downloaded properly? My suggestion would be to download it with a computer, rename it to "update.zip" on a computer, copy it to your internal memory on the phone, and flash it through stock recovery. This should work, what errors do you get when you try to flash it? You're on stock 4.3 when you try to update, correct? In order to flash the OTA you cannot be rooted or have modified the system in any way.
Click to expand...
Click to collapse
Good advice and I'll further add make sure when you rename the 2400258.cfg that you have known file extensions enabled and then right click and highlight the entire file "2400258.cfg" and then rename that to "update.zip"
Trust us, this will work.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
jkeuclid said:
Good advice and I'll further add make sure when you rename the 2400258.cfg that you have known file extensions enabled and then right click and highlight the entire file "2400258.cfg" and then rename that to "update.zip"
Trust us, this will work.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, I tried that. I tried everything, literally everything. Like Samsung told me they couldn't help me unless I sent it in. (Probably just send a replacement or do a full reset with a new partition and data)
Devildude24 said:
Yeah, I tried that. I tried everything, literally everything. Like Samsung told me they couldn't help me unless I sent it in. (Probably just send a replacement or do a full reset with a new partition and data)
Click to expand...
Click to collapse
I'm almost positive you're doing something wrong since you're the only one that is having this problem. I know @jkeuclid has already walked one person through this process step-by-step, I don't want to speak for him but he'd probably be willing to do the same for you.
Devo7v said:
I'm almost positive you're doing something wrong since you're the only one that is having this problem. I know @jkeuclid has already walked one person through this process step-by-step, I don't want to speak for him but he'd probably be willing to do the same for you.
Click to expand...
Click to collapse
Thank you. UPDATE-
I checked, my Baseband version and Build Number don't match.... MF1 vs. ML2. So that could be presenting some of the problem. I'm going to try to find a partition file for stick 4.3 then rehash everything through ODIN and attempt an update. Any other suggestions anyone?
Devildude24 said:
Thank you. UPDATE-
I checked, my Baseband version and Build Number don't match.... MF1 vs. ML2. So that could be presenting some of the problem. I'm going to try to find a partition file for stick 4.3 then rehash everything through ODIN and attempt an update. Any other suggestions anyone?
Click to expand...
Click to collapse
Did you ever figured this out? I'm having the same issue. Can't update using the cfg file.
Just my quess but the OP and others in this thread have possibly problem understanding relationship of Odin with Stock Recovery
If your phone is stock 4.3 and you have the 444 MB update renamed to update.zip already moved over to microSD card.....
See if this little video helps you
https://www.youtube.com/watch?v=B8TOJkBOZfs
Please Help
Devildude24 said:
I'm requesting someone find the Odin files to flash to an i537 model for KitKat 4.4.2, as I can't find it anywhere. If I can't, I'll go to Samsung at Best Buy and uh..... Ask for the Odin files(they use Odin there XD)
Please help as ODIN is the only way I have been able to update, OTAs fail and recovery install from cache, external SD fails. Everything but Odin fails, so anybody help?
Device details-
SGH-i537 AT&T running 4.3 Official Unrooted Stock
Thanks!!!
Click to expand...
Click to collapse
Please I need your help, I was trying to upgrade to 4.4 from 4.3 ML2, on i537, but when i did, I lost my wifi and camera and media, (I mean , I cant play any song, show me a message that cant play, "File not Suppoted') anyways, the help that I need is if you can help me with your stock rom, so I can flash my phone with your files, please. Im downgrade to 4.3 again and I used one backup that I did before upgrade, but still not work wifi and media, I already flashed the moden.bin from xda to fix wifi, but still not work, I want to try to flash a Real stock rom, and see what happen, cause Im very stress...
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
HomeWipe cache/dalvik Robot System
Liooh said:
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
HomeWipe cache/dalvik Robot System
Click to expand...
Click to collapse
Sorry, I didn't mark the Q question.
Liooh said:
Sorry, I didn't mark the Q question.
Click to expand...
Click to collapse
Are you sure of the file your attempting to use.? Maybe you have an FXZ zip file, and you would need to flash with RSDLite or adb..not TWRP..double check what you are attempting..
Also..make sure you are using the correct file for your device..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
Are you sure of the file your attempting to use.? Maybe you have an FXZ zip file, and you would need to flash with RSDLite or adb..not TWRP..double check what you are attempting..
Also..make sure you are using the correct file for your device..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
I've wondered that too but I'm using the one that was recommended. The one with the Lite I already did and it proceeded well.
Do you know where I can find more files like that then ? (not firmwares)
Liooh said:
I've wondered that too but I'm using the one that was recommended. The one with the Lite I already did and it proceeded well.
Do you know where I can find more files like that then ? (not firmwares)
Click to expand...
Click to collapse
OMGoodness.. I'm not really sure Sir..I have a XT1060 DEV..but I haven't kept up with the Moto X lately (in the past month)..So..I'm not really the one to help you with newer versions..Are you sure 4.4.3 is right for your device.?
I'd suggest do research in here (XDA) and know what is the latest..I'm assuming that you are trying to flash an OTA..but if you have a file someone has "ported" or something of that nature..go back to where you downloaded the file and research..
Even if you have an OTA zip..I'd suggest maybe know the file more, maybe it should be unzipped and run an XML file..I honestly am not familiar with the file you are attempting to use..
Maybe post a link to where you found the file and myself and others can go look at what file and its purpose..then maybe we can assist you more..Sorry I can't help you more at this time..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
OMGoodness.. I'm not really sure Sir..I have a XT1060 DEV..but I haven't kept up with the Moto X lately (in the past month)..So..I'm not really the one to help you with newer versions..Are you sure 4.4.3 is right for your device.?
I'd suggest do research in here (XDA) and know what is the latest..I'm assuming that you are trying to flash an OTA..but if you have a file someone has "ported" or something of that nature..go back to where you downloaded the file and research..
Even if you have an OTA zip..I'd suggest maybe know the file more, maybe it should be unzipped and run an XML file..I honestly am not familiar with the file you are attempting to use..
Maybe post a link to where you found the file and myself and others can go look at what file and its purpose..then maybe we can assist you more..Sorry I can't help you more at this time..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
It was an youtube video, his device is the same as mine XT1058, his device went perfectly.
Liooh said:
It was an youtube video, his device is the same as mine XT1058, his device went perfectly.
Click to expand...
Click to collapse
Oh..OK..maybe contact that one to help you..go back to the video and post a comment/question..maybe someone there can help..
Also maybe post a link here..and we can go look ourselves and maybe help you.?
Also..make sure you have a good download..not corrupted..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Whatever you are trying to flash can't be flashed with twrp so there's problem number one...
Sent from my XT1060
Liooh said:
It's already rooted/unlocked bootloader but, I did everything alright and this is what happened.
can someone help me get if fixed ? thanks
obs: it didn't brick or anything.. just fails when I try to upgrade.
This is what's written:
Updating partition details...
Installing '/sdcard/Blur_Version.212.44.22.ghost
checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of motorola/gh
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/Blur_Version.212.44.
Updating partition details...
FAILED.
HomeWipe cache/dalvik Robot System
Click to expand...
Click to collapse
Yep, @rocketsaucev2 is right. You appear to be attempting to flash the update.zip from custom recovery. It is well documented that you must have STOCK recovery in order to flash an official update.zip
samwathegreat said:
Yep, @rocketsaucev2 is right. You appear to be attempting to flash the update.zip from custom recovery. It is well documented that you must have STOCK recovery in order to flash an official update.zip
Click to expand...
Click to collapse
It's already STOCK.
Isn't the 4.4.2 you're talking about ?
Liooh said:
It's already STOCK.
Isn't the 4.4.2 you're talking about ?
Click to expand...
Click to collapse
No, it isn't. The screenshots you uploaded CLEARLY show custom recovery. You need to flash stock recovery back before you can take any updates.
If you don't know the difference between stock and custom recovery, you aren't ready to update. You need to Read, Read, Read....
This would be a good start: http://mark.cdmaforums.com/MotoX-OTA.html (Thanks @KidJoe for the well-written documentation)
samwathegreat said:
No, it isn't. The screenshots you uploaded CLEARLY show custom recovery. You need to flash stock recovery back before you can take any updates.
If you don't know the difference between stock and custom recovery, you aren't ready to update. You need to Read, Read, Read....
This would be a good start: http://mark.cdmaforums.com/MotoX-OTA.html (Thanks @KidJoe for the well-written documentation)
Click to expand...
Click to collapse
Hi friend..
Yes I did everything.
Here me explaining everything: http://forum.xda-developers.com/and...ns-problem-t2810890/post54034992#post54034992
Liooh said:
Hi friend..
Yes I did everything.
Here me explaining everything: http://forum.xda-developers.com/and...ns-problem-t2810890/post54034992#post54034992
Click to expand...
Click to collapse
I'm trying really hard to explain it to you but you just aren't getting it....
This is what you wrote in the post you linked:
1- Return to STOCK(Mine is 4.4.2) But I did stock it to 4.4.2. OK!
2- Install the TWRP to install the SuperSU. OK, Everything's fine.
3- After it, my dev is already rooted.
OK, look at step number 2: YOU INSTALLED TWRP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
When you flashed TWRP, you REPLACED stock recovery with custom recovery (TWRP).
As I've been trying to make you understand, OTAs will -----ONLY----- install if you have STOCK RECOVERY.
You will need to flash stock recovery BACK (replacing TWRP), THEN you can accept the update!!!!
Afterwards, you can flash TWRP back.
This is well documented everywhere.....you will have to do this EVERYTIME a new OTA comes out.
You can NOT accept an OTA if you have TWRP installed.
Do you understand now?
samwathegreat said:
I'm trying really hard to explain it to you but you just aren't getting it....
This is what you wrote in the post you linked:
1- Return to STOCK(Mine is 4.4.2) But I did stock it to 4.4.2. OK!
2- Install the TWRP to install the SuperSU. OK, Everything's fine.
3- After it, my dev is already rooted.
OK, look at step number 2: YOU INSTALLED TWRP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
When you flashed TWRP, you REPLACED stock recovery with custom recovery (TWRP).
As I've been trying to make you understand, OTAs will -----ONLY----- install if you have STOCK RECOVERY.
You will need to flash stock recovery BACK (replacing TWRP), THEN you can accept the update!!!!
Afterwards, you can flash TWRP back.
This is well documented everywhere.....you will have to do this EVERYTIME a new OTA comes out.
You can NOT accept an OTA if you have TWRP installed.
Do you understand now?
Click to expand...
Click to collapse
But I did STOCK and no updates came up.
Liooh said:
But I did STOCK and no updates came up.
Click to expand...
Click to collapse
I'm convinced that you aren't even reading what I'm writing......
Let me make this easy for you:
Do this:
1. Return to Stock 4.4.2
2. Accept the OTA (DO NOT FLASH TWRP)
3. After you accept the OTA, and you are running 4.4.3, NOW you can install TWRP
YOU CANNOT ACCEPT THE OTA IF TWRP IS INSTALLED!!!!! I've told you this SO many times now.....
TWRP is your problem. You must NOT install TWRP and root (supersu) until AFTER you accept the OTA.
It has ALWAYS been like this. This is nothing new.
Please read my posts carefully. If you follow those instructions, it WILL work.........
samwathegreat said:
I'm convinced that you aren't even reading what I'm writing......
Let me make this easy for you:
Do this:
1. Return to Stock 4.4.2
2. Accept the OTA (DO NOT FLASH TWRP)
3. After you accept the OTA, and you are running 4.4.3, NOW you can install TWRP
YOU CANNOT ACCEPT THE OTA IF TWRP IS INSTALLED!!!!! I've told you this SO many times now.....
TWRP is your problem. You must NOT install TWRP and root (supersu) until AFTER you accept the OTA.
It has ALWAYS been like this. This is nothing new.
Please read my posts carefully. If you follow those instructions, it WILL work.........
Click to expand...
Click to collapse
When I go back to STOCK doesn't the TWRP break ? Because whenever I go back to stock and try to click on "Recovery" Dev stops working. That's what I did man..
1- Back to STOCK perfectly.
2- No Updates comes up. What's this OTA update you're talking about ? where does it pops up ? I'M SURE I DIDN'T RECEIVE ANY right after I stock it... I even checked it in the System Updates...
Liooh said:
When I go back to STOCK doesn't the TWRP break ? Because whenever I go back to stock and try to click on "Recovery" Dev stops working. That's what I did man..
1- Back to STOCK perfectly.
2- No Updates comes up. What's this OTA update you're talking about ? where does it pops up ? I'M SURE I DIDN'T RECEIVE ANY right after I stock it... I even checked it in the System Updates...
Click to expand...
Click to collapse
YES, you do NOT want TWRP (or you can't accept the update).
OTA = "Over the air update" = update to 4.4.3
What method are you using to return to stock? Tell me you aren't just doing a "factory reset". How exactly are you "returning to stock"?
If you install TWRP = updates DISABLED.
samwathegreat said:
YES, you do NOT want TWRP (or you can't accept the update).
OTA = "Over the air update" = update to 4.4.3
What method are you using to return to stock? Tell me you aren't just doing a "factory reset". How exactly are you "returning to stock"?
If you install TWRP = updates DISABLED.
Click to expand...
Click to collapse
I tried many.. RSDLite, Manual flashing and that one that is recommended for people with problems with "boot loop" and the first I tried two days ago that erased all my data, cache, everything..
The thing is, is that every method seems to work fine but I just don't receive the update '-'
Actually I receive that upgrade that is something that pops up for 3 seconds saying "Upgrading android, installing apps." Then my Dev initializes normal but still dealing with the 4.4.2...
Liooh said:
I tried many.. RSDLite, Manual flashing and that one that is recommended for people with problems with "boot loop" and the first I tried two days ago that erased all my data, cache, everything..
The thing is, is that every method seems to work fine but I just don't receive the update '-'
Click to expand...
Click to collapse
Please just try.
1. Return to Stock (just use RSD Lite) YES, this will erase EVERYTHING.
2. Go to settings > About Device > System Update
3. Update to 4.4.3 will install.
4. After 4.4.3 successfully installs, NOW you can flash TWRP (ONLY after you are on 4.4.3)
Please just try it.....
---------- Post added at 08:21 PM ---------- Previous post was at 07:36 PM ----------
Liooh said:
Actually I receive that upgrade that is something that pops up for 3 seconds saying "Upgrading android, installing apps." Then my Dev initializes normal but still dealing with the 4.4.2...
Click to expand...
Click to collapse
That is because you flashed TWRP, as I've been trying to make you understand.....
Is Spanish your native language?
If so, perhaps this page will explain it better than I can:
http://getmovil.com/motorola/instalar-android-4-4-3-moto-x-root/
samwathegreat said:
Please just try.
1. Return to Stock (just use RSD Lite) YES, this will erase EVERYTHING.
2. Go to settings > About Device > System Update
3. Update to 4.4.3 will install.
4. After 4.4.3 successfully installs, NOW you can flash TWRP (ONLY after you are on 4.4.3)
Please just try it.....
Click to expand...
Click to collapse
See now ?
I went to codeworks page:
There are 4 files for the x522 in firmware and 4 in modems. I am assuming the "19s" firmware is for India so is the "20s" for the US?
But the 4 files in the modem section is confusing, which one/one's are for the US model x522? here is the link for the modems https://host.llamasweet.tech/codeworkx/lineage/s2/
Thanks
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
leo221 said:
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
Click to expand...
Click to collapse
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
veda1 said:
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
Click to expand...
Click to collapse
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
leo221 said:
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
Click to expand...
Click to collapse
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
veda1 said:
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
Click to expand...
Click to collapse
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now?
Click to expand...
Click to collapse
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
Click to expand...
Click to collapse
Yep its still happening. Tried to flash it right now and it says "can't read" error.
veda1 said:
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
Click to expand...
Click to collapse
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
leo221 said:
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
Click to expand...
Click to collapse
Updated script according to the video, still not flashing, says "cannot read error"
veda1 said:
Updated script according to the video, still not flashing, says "cannot read error"
Click to expand...
Click to collapse
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
leo221 said:
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
Click to expand...
Click to collapse
Unbelievable! It actually worked after the 2nd attempt. Even got the 21s update. Thanks :good:
The original question is still unanswered about which one is the correct firmware for the US model amng the firmware provided by codeworks, hopefully someone knows that and will share in interest of others that might have the same problem.
Thanks again @leo221 for providing a clear and easy solution.