Hi guys,
i hope somebody can help this Moto E.
I gift this moto E to a lady, and for this i can't do much test. She is in another country, but she is very smart and she can do nearly all
The model is a dual sim bough in Italy from Amazon, version XT1022. Some days ago, it blocked... without reason. It had continusoly "Unfortunately, Google play service stopped". She tried to do simple things, nothing. Than she tried to do an hard reset with the menu in Android, After this, at boot it went directly in the service menu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then she tried factory reset , recovery and some other try and it started asking to put language etc etc, but immediatly get the same error she had from beginning:
Than she give the phone to a general services, cause in Armenia doesen't exist Motorola, and now the situation is as the video.
https://www.youtube.com/watch?v=VeC0TTNOgsU
Please help her, it's so much important this phone for her
Many thanks to all
Ale
Install a custom rom, recomend a cm12, cm13.
Do you think is better than try with a stable original FW?
Thanks
yes
alechef said:
Hi guys,
i hope somebody can help this Moto E.
I gift this moto E to a lady, and for this i can't do much test. She is in another country, but she is very smart and she can do nearly all
The model is a dual sim bough in Italy from Amazon, version XT1022. Some days ago, it blocked... without reason. It had continusoly "Unfortunately, Google play service stopped". She tried to do simple things, nothing. Than she tried to do an hard reset with the menu in Android, After this, at boot it went directly in the service menu
Then she tried factory reset , recovery and some other try and it started asking to put language etc etc, but immediatly get the same error she had from beginning:
Than she give the phone to a general services, cause in Armenia doesen't exist Motorola, and now the situation is as the video.
https://www.youtube.com/watch?v=VeC0TTNOgsU
Please help her, it's so much important this phone for her
Many thanks to all
Ale
Click to expand...
Click to collapse
Based on what I saw in the video, the bootloader is still locked. With the bootloader locked you will not be able to install a customer recovery or a custom ROM. The only way to revive this device is by fastboot flashing the factory stock firmware. You can do this with a locked bootloader because the firmware is signed by Motorola. Give this thread a look through. Looks like pretty solid instructions to unbrick this thing.
Sent from my Nexus 6 using XDA-Developers mobile app
Hi dear, which thread you are speaking about? can you give me link?
Thanks
alechef said:
Hi dear, which thread you are speaking about? can you give me link?
Thanks
Click to expand...
Click to collapse
Sorry, I forgot to post the link. This will be the only way to restore the device. Here ya go.
http://forum.xda-developers.com/showthread.php?t=2759495
Sent from my Nexus 6 using XDA-Developers mobile app
Hi, i just found it before, but the stock FW link is death :'( Any suggestions? She has Xt1022, i don't know which version of Android
Thanks
Those are no the original FW, yes?
http://forum.xda-developers.com/showthread.php?t=2755857
Or this one?
http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
alechef said:
Those are no the original FW, yes?
http://forum.xda-developers.com/showthread.php?t=2755857
Click to expand...
Click to collapse
I do believe this thread contains the factory images signed by Motorola so they can be installed with fastboot with a locked bootloader.
Sent from my Nexus 6 using XDA-Developers mobile app
---------- Post added at 03:52 PM ---------- Previous post was at 03:50 PM ----------
fast69mopar said:
I do believe this thread contains the factory images signed by Motorola so they can be installed with fastboot with a locked bootloader.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just for clarification, this thread does contain the factory image that you will need.
Sent from my Nexus 6 using XDA-Developers mobile app
Thanks much dear
From photo and video you can understand what androd is installed?
Take lollipop from here, http://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111, is bad idea ?
Thanks much
Ale
alechef said:
Those are no the original FW, yes?
http://forum.xda-developers.com/showthread.php?t=2755857
Click to expand...
Click to collapse
Download the stock Motorola firmware from here. I would use this thread.
Sent from my Nexus 6 using XDA-Developers mobile app
Not starting Phone
first i've just flash the stock ROM on my moto e and then install the OTA update of android kitkat 4.4.4 and now phone is not starting what should i do I am in trouble pls help ??
whenever i press button there's no response but when i switch it to charging then i press button then notification pulse light start blinking only device is not starting pls help me pls ??
KayneXDA said:
first i've just flash the stock ROM on my moto e and then install the OTA update of android kitkat 4.4.4 and now phone is not starting what should i do I am in trouble pls help ??
whenever i press button there's no response but when i switch it to charging then i press button then notification pulse light start blinking only device is not starting pls help me pls ??
Click to expand...
Click to collapse
Have you tried to use the correct button combination to enter recovery or to enter the bootloader? Also, I'm assuming that you have unlocked the bootloader since you said you flashed the stock firmware. Did you flash the stock firmware using fastboot?
Next question, have you ever rooted or installed a custom recovery on this device?
Use these steps to see if you can enter recovery:
Turn off your Moto E.
Press power + volume up and volume down keys at the same time.
Keep pressing the buttons for about 3 or 4 seconds.The boot menu should be then displayed on your device.
Use the volume down button in order to scroll down until you highlight the recovery option and then press volume up key once.
You should see the Android logo displayed on your Moto E.
At that point press Volume Up and Volume Down buttons for about 5 seconds and press power button once.
In the end the recovery mode menu should be displayed on your phone.
Once you are in recovery mode select wipe data/factory reset.
Then select the reboot option and see if your phone will boot normally.
If for some reason you cannot enter the bootloader menu to select any of the options, connect your Moto E to your PC and look at the device manager to see what your PC recognizes your device as?
Let me know how it goes. Try to be as specific as possible in your next post if you see an error or something happen on the screen. Try to give as much detail as possible.
@KayneXDA - You have completely killed the phone. There are threads warning never to do what you just did.
http://forum.xda-developers.com/moto-e/general/warning-downgrading-information-moto-e-t3062859 @alechef - Download latest Factory Firmware Image for that Model of Moto E. Bootloader can be locked. Your making this more complicated than it needs to be.
Firmware Images: http://forum.xda-developers.com/showthread.php?t=2755857
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2759495
fast69mopar said:
Have you tried to use the correct button combination to enter recovery or to enter the bootloader? Also, I'm assuming that you have unlocked the bootloader since you said you flashed the stock firmware. Did you flash the stock firmware using fastboot?
Next question, have you ever rooted or installed a custom recovery on this device?
Use these steps to see if you can enter recovery:
Turn off your Moto E.
Press power + volume up and volume down keys at the same time.
Keep pressing the buttons for about 3 or 4 seconds.The boot menu should be then displayed on your device.
Use the volume down button in order to scroll down until you highlight the recovery option and then press volume up key once.
You should see the Android logo displayed on your Moto E.
At that point press Volume Up and Volume Down buttons for about 5 seconds and press power button once.
In the end the recovery mode menu should be displayed on your phone.
Once you are in recovery mode select wipe data/factory reset.
Then select the reboot option and see if your phone will boot normally.
If for some reason you cannot enter the bootloader menu to select any of the options, connect your Moto E to your PC and look at the device manager to see what your PC recognizes your device as?
Let me know how it goes. Try to be as specific as possible in your next post if you see an error or something happen on the screen. Try to give as much detail as possible.
Click to expand...
Click to collapse
I insalled the CM 4.4.4 first then i install CM 13 marshmallow then again i install CM 11 (4.4.4) cz marshmallow is lagging so much then i just flash my phone in stock ROM 4.4.2 via fastboot then i just updated the phone to 4.4.4 now m stuck.
there is no response from the phone i've tried every key combination nothing nothing NO RESPONSE :crying::crying:
what should i do pls ??
lost101 said:
@KayneXDA - You have completely killed the phone. There are threads warning never to do what you just did.
http://forum.xda-developers.com/moto-e/general/warning-downgrading-information-moto-e-t3062859 @alechef - Download latest Factory Firmware Image for that Model of Moto E. Bootloader can be locked. Your making this more complicated than it needs to be.
Firmware Images: http://forum.xda-developers.com/showthread.php?t=2755857
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2759495
Click to expand...
Click to collapse
Is there anything i can do ??
KayneXDA said:
Is there anything i can do ??
Click to expand...
Click to collapse
Moto G (1st Gen) got a 5.0 unbrick method recently. Nothing for Moto E (1st Gen) at this time - that I'm aware of.
Follow this thread for developments: http://forum.xda-developers.com/moto-e/general/unbricking-hard-bricked-moto-e-t3306809
Related
Hello, my phone is stuck ath the sony logo, when I restart it it just stays there. What should I do to make my phone work again?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the last working picture of my phone
mrdjibrilo said:
Hello, my phone is stuck ath the sony logo, when I restart it it just stays there. What should I do to make my phone work again?
Click to expand...
Click to collapse
Stock, no root or recovery?
Have you used flashtool before?
EDIT: First of all turn it off: hold power | volume up untill you feel 3 vibrations. and charge.
ChikeD said:
Stock, no root or recovery?
Have you used flashtool before?
EDIT: First of all turn it off: hold power | volume up untill you feel 3 vibrations. and charge.
Click to expand...
Click to collapse
thanks I did that, the power/volume combo, and it turned off, and then I used this http://talk.sonymobile.com/t5/Xperi...ctions-using-Pc-Companion-Windows/td-p/249946, if anyone has the same problem this will solve it!
mrdjibrilo said:
thanks I did that, the power/volume combo, and it turned off, and then I used this http://talk.sonymobile.com/t5/Xperi...ctions-using-Pc-Companion-Windows/td-p/249946, if anyone has the same problem this will solve it!
Click to expand...
Click to collapse
Now I would recommend building your flashtool flashable firmware file from PCC/SUS files.
flashtool: http://www.flashtool.net/
Guides:
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
http://forum.xda-developers.com/showthread.php?t=2188129
ChikeD said:
Now I would recommend building your flashtool flashable firmware file from PCC/SUS files.
flashtool: http://www.flashtool.net/
Guides:
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
http://forum.xda-developers.com/showthread.php?t=2188129
Click to expand...
Click to collapse
i was trying to put cyanogenmod's kitkat4, but it failed, and started showing only the sony logo, while trying to fix it(before i saw this thread), i flashed the c-mod's kernel onto my phone, that didnt help, and now i'm not able to update my phone using the sony site link which is given above, it says, "unkown software is present in the phone, so cant install". Somebody please help!! :crying::crying:
dont panic bro
lalithesh said:
i was trying to put cyanogenmod's kitkat4, but it failed, and started showing only the sony logo, while trying to fix it(before i saw this thread), i flashed the c-mod's kernel onto my phone, that didnt help, and now i'm not able to update my phone using the sony site link which is given above, it says, "unkown software is present in the phone, so cant install". Somebody please help!! :crying::crying:
Click to expand...
Click to collapse
stay calm i know how u feel.flashing kernel wont help u cus u missing some system file that why your phone won't boot.Just do as i say
1.download flashtool here the link http://www.flashtool.net/download.php
2.download xperia p stock firmware jb or ics or gb(i recommend jb this link http://forum.xda-developers.com/showthread.php?t=2322163 )
3.learn how to use flashtool (i think already know how to use it but if u dont try to search google)
4.flash it done
work or not please tell me maybe i can help u more
flashtool is ur last option, 1st u need to repair using SUS. since u can open ur phone so its not going to be any problem in repair it using SUS. just open sus, close ur phone and press power and up down button and plug the usb to enter flashmode.
1st of ll power off your phone bu presiing power & Vol+button ubtill you feel 3 vibrations,then Charge your phone for atleast 1 hr.Then flash the stock JB/ICS/GB firmware (ftf(including kernel)),whichever you want.Thats it!
dara007_168 said:
stay calm i know how u feel.flashing kernel wont help u cus u missing some system file that why your phone won't boot.Just do as i say
1.download flashtool here the link http://www.flashtool.net/download.php
2.download xperia p stock firmware jb or ics or gb(i recommend jb this link http://forum.xda-developers.com/showthread.php?t=2322163 )
3.learn how to use flashtool (i think already know how to use it but if u dont try to search google)
4.flash it done
work or not please tell me maybe i can help u more
Click to expand...
Click to collapse
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
lalithesh said:
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
Click to expand...
Click to collapse
good to hear that bro
Sent from my Xperia U using xda app-developers app
Same problem on my XU with Honami
I have been facing the same problem with Honami on my Xperia U. I used the experimental v12 kernal. DO not reboot your phone (eihter in cwm or normal reboot). I was switching my sim and I forgot that the phone would reboot. It got stuck and I had to use flashtool, reroot and go thru the pain. This has happened thrice to me now. Dont let your phone reboot, restart. If you want to restart, then power off and then power on.
I am kinda scared that if this happens when I am away, I wont be able to repair the phone without a computer, flashtool, stock kernal, firmware. Even cwm is not accessible when this happens and its very scary.
The Rom otherwise is the smoothest JB you'll find, everything works well. I have already put in all the usual apps like whatsapp, gmail, hangout, stock fm radio from xperia, maps etc. No facebook - it is process and memory hogger.
I want to build a flashable ftf of my current setup of honami so I can flash it using flashtool. How do I do that. I dont want to flash the stock firmware and then restore the honami everytime. Is it possible to build an ftf and a boot.img kernal of your custom rom and kernal to flash with flashtool?
lalithesh said:
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
Click to expand...
Click to collapse
hi,
when you downloaded the rom from the link,
was is in *.tar format?
how did you manage to use it in flashtool?
thanks in advance.
Edits...
google-ed & got the full rom in *.tff format from the following link:
h t t p:// android.sc/install-official-jelly-bean-4-1-2-6-2-a-1-100-firmware-on-sony-xperia-p/
booting into 6.2.A.0.400
Stuck at Sony Logo
Heres the entire story which i posted as question but havent recieved a reply yet. Hope someone checks this and helps
OK i ve been trying to flash a new custom rom on my Xperia P, i looked at a number of guidelines and doing things step by step.
Since im very new to this i downloaded a few Roms. I was following the guide "http://droidors.com/2014/07/08/update-xperia-p-lt22i-to-android-4-4-4-kitkat-with-slimkat-custom-rom/2/" and everything was going fine. I reached the step to "fastboot flash boot boot.img", i did that and then went on the next step to boot in CWM Recovery and install the zip rom and the Gapps. During the Zip Rom install i got status 7 error.
Now, i noticed that i might have flashed the wrong Rom so rechecked the guide and installed the correct Rom which is mentioned in "http://forum.xda-developers.com/xperia-u/p-development/rom-slimkat-4-4-2-release-candidate-t2657795" and installed it through Fastboot. But now THE PROBLEM IS, AFTER I FLASHED THE INCORRECT IMG, MY PC IS NOT RECOGNISING THE XPERIA P SAYING IT DOESNOT RECOGNISE THE DRIVERS, therefore im not able to copy the ROM Zip on the SDcard, to then run it from CWM.
Please help.
After sometime i tried the below
After I flashed the SlimKat Rom, and things went out of hand ( till this point i could see Slimkat logo at boot and could also go in CWM Recovery ), I tried to restore through Nandroid Backup i had done. As soon i selected the restore option and then the backup file, within 2-3 seconds the phone went off, and then on boot all i can do is see "SONY" on screen. Nothing else happens.
Ok, now i tried to flash the stock Rom through this link "http://forum.xda-developers.com/xperia-u/p-development/ftf-firmware-xperia-p-generic-world-t2322163", through flashtool to bring my phone back to life. I installed the drivers as per instructions from drivers folder, but for some reason the pc is just not accepting. I did install through this exact method yesterday night and it worked perfectly.
Please suggest. I hope im asking at the right place.
Urgent help please
Kindly advise, im stuck with no spare phone.
OK, the flashing tool from Sony, EMMA enabled me to flash the jb firmware (it recognised my xperia p ) . once I got that working I managed to flash Cm11 on my device, with assistance from another user..
Thanks.. Hope it helps someone
General info on how to come out of soft brick, or bootloop, or status 7 error.
What you did is the right thing.
For someone who might experience the same thing ( flashed the kernel, got some error, and is stuck at bootloop), or has got the status 7 error, follow the below steps:
1) Download the LT22i_6.2.A.1.100.ftf file from the net, google a bit and u will find a download link.
1) Press and hold the power button + Vol Up. The phone vibrates once, and then after about 2 seconds, vibrates thrice, only then leave the keys. IT IS IMPORTANT TO WAIT FOR 3 VIBRATES. The phone is powered off now.
2) Hold the vol Up key and connect to the pc, it will connect in the fastboot mode, indicated by a violet notification light. If u dont get the violet light, you have not connected in the fast boot mode. remove the connection and repeat the above steps if necessary.
3) In flashtool, select the ftf file and carry on with the next instructions.
4) When it asks you to disconnect the phone and connect by holding menu key, disconnect the phone, hold the vol down key and connect it back. The flashing process will continue.
5) Disconnect once its done. Start the phone, wait till it loads up, Restart again, let it settle for about 5 min, you are good to go.
For status 7 error:
It is usually caused because of the kernel and rom not being compatible, or if the kernel is not compatible with the phone.., Follow the above steps to come out of it, find the right kernel and proceed as usual.. Hope this will help someone, Press thanks if it did.., Cheers.
I have a sony v3+ when i start it,it has stucked on the sony logo. what do i do
Hi All,
I have an Xperia Z2 D6503 South Africa (Vodacom) .402
I would like to de-brand it and possibly root it (will think on this).
Currently I am downloading D6503_17.1.2.A.0.314_Generic CA.ftf. Is this the right thing to do?
I am looking at XperiFirm but I am not sure how to find generic firmware there. I do get an option for 1281-8114/South Africa/Customized ZA (ver 314). What is this Customized operator? Is it essentially generic?
Currently I really hate Vodacom's customization. had them on my S3, S4 and now Z2 and they just break all the time. Plus I can barely use my dialer/contacts/call log so just want to reload but preferably sans operator crap.
I know there are plenty of threads out there that may possibly answer this question for me but I have not been able to find much regarding South African firmware and I am loath to just wing it without a little info from someone in the know.
Any help would be much appreciated!
Many Thanks
Tarn
tarnalcock said:
Hi All,
I have an Xperia Z2 D6503 South Africa (Vodacom) .402
I would like to de-brand it and possibly root it (will think on this).
Currently I am downloading D6503_17.1.2.A.0.314_Generic CA.ftf. Is this the right thing to do?
I am looking at XperiFirm but I am not sure how to find generic firmware there. I do get an option for 1281-8114/South Africa/Customized ZA (ver 314). What is this Customized operator? Is it essentially generic?
Currently I really hate Vodacom's customization. had them on my S3, S4 and now Z2 and they just break all the time. Plus I can barely use my dialer/contacts/call log so just want to reload but preferably sans operator crap.
I know there are plenty of threads out there that may possibly answer this question for me but I have not been able to find much regarding South African firmware and I am loath to just wing it without a little info from someone in the know.
Any help would be much appreciated!
Many Thanks
Tarn
Click to expand...
Click to collapse
Yes, "Customized" firmwares are those debranded ones.
You'll be fine with the Customized ZA.
Jackos said:
Yes, "Customized" firmwares are those debranded ones.
You'll be fine with the Customized ZA.
Click to expand...
Click to collapse
Thank you Jackos! Wasn't expecting such a fast response! I really appreciate it! :good:
BRICKED!
So I managed to brick my Z2 using the latest version of FlashTool/Xperifirm.
I upgraded it to 4.4.4, using a Generic UK variant as it is not yet available in my country, and my battery started draining tons faster and half of my apps would just close randomly (no errors) almost as if the back button was being pushed so much so that I could not type any messages or anything.
I tried to re-flash the previous 4.4.2 version (RSA Generic) and that just resulted in a boot loop. So I am back up and running using 4.4.4 but it is not going too well. Could anyone please give me some advice on the best step forward?
tarnalcock said:
So I managed to brick my Z2 using the latest version of FlashTool/Xperifirm.
I upgraded it to 4.4.4, using a Generic UK variant as it is not yet available in my country, and my battery started draining tons faster and half of my apps would just close randomly (no errors) almost as if the back button was being pushed so much so that I could not type any messages or anything.
I tried to re-flash the previous 4.4.2 version (RSA Generic) and that just resulted in a boot loop. So I am back up and running using 4.4.4 but it is not going too well. Could anyone please give me some advice on the best step forward?
Click to expand...
Click to collapse
Let me get a few screen shots ready then I'll help... I bricked mine last week - no issues...
---------- Post added at 03:13 PM ---------- Previous post was at 02:54 PM ----------
Here is what you should do:
01] Install the following drivers (assuming that flashtool is already installed) C:\Flashtool\drivers\Flashtool-drivers.exe and select the first two boxes as shown and the Z2 boxes at the bottom:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
01] Load Flashtool
02] Turn off the phone
03] Hold down the Vol-down button (and keep it down) and plug in the USB (hold the buttol will you see some output in Flashtool). You should see Windows install the Flashmode drivers in your taskbar if it has not done so yet. Flashtool should also show that the device is in flashmode. It is crusial that these flashmode drivers are installed before flashing. Just to make sure that the flashmode drivers are installed, remove the USB and repeat the pressing of Vol-Down whilst plugging the USB.
If all seems fine with flashmode in flashtool, remove device and go on to selecting the shown FTF, double click it after it is queried from the server and build the FTF ON YOUR OWN PC. Do not download an FTF from a site. They could be damaged. When selecting the files to build the FTF, select all files EXCEPT the *.ta ones. They should NOT be selected.
Then flash with the following boxes ticked and unticked:
Puffin617 said:
Let me get a few screen shots ready then I'll help... I bricked mine last week - no issues...
---------- Post added at 03:13 PM ---------- Previous post was at 02:54 PM ----------
Here is what you should do:
01] Install the following drivers (assuming that flashtool is already installed) C:\Flashtool\drivers\Flashtool-drivers.exe and select the first two boxes as shown and the Z2 boxes at the bottom:
01] Load Flashtool
02] Turn off the phone
03] Hold down the Vol-down button (and keep it down) and plug in the USB (hold the buttol will you see some output in Flashtool). You should see Windows install the Flashmode drivers in your taskbar if it has not done so yet. Flashtool should also show that the device is in flashmode. It is crusial that these flashmode drivers are installed before flashing. Just to make sure that the flashmode drivers are installed, remove the USB and repeat the pressing of Vol-Down whilst plugging the USB.
If all seems fine with flashmode in flashtool, remove device and go on to selecting the shown FTF, double click it after it is queried from the server and build the FTF ON YOUR OWN PC. Do not download an FTF from a site. They could be damaged. When selecting the files to build the FTF, select all files EXCEPT the *.ta ones. They should NOT be selected.
Then flash with the following boxes ticked and unticked:
Click to expand...
Click to collapse
Wow! Thank you for the informative post there Puffin. This is the same process I used to unbrick it but I had to stick with the newer ftf (4.4.4). Supposedly something to do with partitioning. Will ticking the boxes as you have done allow me to switch back to 4.4.2?
tarnalcock said:
Wow! Thank you for the informative post there Puffin. This is the same process I used to unbrick it but I had to stick with the newer ftf (4.4.4). Supposedly something to do with partitioning. Will ticking the boxes as you have done allow me to switch back to 4.4.2?
Click to expand...
Click to collapse
I did. I was on 4.4.4. I bricked my device by trying to install the TWRP recovery 2.8. I flashed the 314 (4.4.2) build to get my phone unbricked and started over...
PS: This does a full wipe of internal sdcard
Puffin617 said:
I did. I was on 4.4.4. I bricked my device by trying to install the TWRP recovery 2.8. I flashed the 314 (4.4.2) build to get my phone unbricked and started over...
PS: This does a full wipe of internal sdcard
Click to expand...
Click to collapse
I will try that. Thank you. Initially 4.4.4 seemed to be behaving but it has started doing random things again. Which is sad. I like the new look. And there are some nice little features I could get used to. Really don't know how they could release it so buggy. Then again I am way ahead of my country's release cycle. By the time we get 4.4.4, Lollipop will be old news already hahaha.
del.
Thanks Puffin617!
Thank you Puffin617. I was able to restore my phone as described.
I think the trick was ultimately ticking the 'Data' box which then overwrote the partition as I had previously left this un-ticked to preserve my data.
tarnalcock said:
Thank you Puffin617. I was able to restore my phone as described.
I think the trick was ultimately ticking the 'Data' box which then overwrote the partition as I had previously left this un-ticked to preserve my data.
Click to expand...
Click to collapse
Yip. Appart from the /data partition, that /sdcard/Android/data folder on the internal sd card is a poison when updating/changing between ROMs. I delete that folder EVERY time I flash a ROM.
Puffin617 said:
Yip. Appart from the /data partition, that /sdcard/Android/data folder on the internal sd card is a poison when updating/changing between ROMs. I delete that folder EVERY time I flash a ROM.
Click to expand...
Click to collapse
Good to know! Do you think that is what may have caused all of my problems with 23.0.1.A.0.32 in the first place? Was such weird behavior!
Volume button never worked
keyboards kept collapsing as if the back button was pushed (stock android/minuum/swiftkey all did the same)
apps would close randomly
Google Play Music would pause every time the screen orientation changed or if I turned a page too fast in Play Books.
Battery drain was significantly faster (10% passive drain in about 1.5 hours)
4k recording would not open, nor would the camera stay open for more than a few seconds (this was very intermittent)
In fact I eventually became convinced that there was a physical fault with the phone, but this is not the case (thank God!).
tarnalcock said:
Good to know! Do you think that is what may have caused all of my problems with 23.0.1.A.0.32 in the first place? Was such weird behavior!
Volume button never worked
keyboards kept collapsing as if the back button was pushed (stock android/minuum/swiftkey all did the same)
apps would close randomly
Google Play Music would pause every time the screen orientation changed or if I turned a page too fast in Play Books.
Battery drain was significantly faster (10% passive drain in about 1.5 hours)
4k recording would not open, nor would the camera stay open for more than a few seconds (this was very intermittent)
In fact I eventually became convinced that there was a physical fault with the phone, but this is not the case (thank God!).
Click to expand...
Click to collapse
23.0.1.A.0.32 was a test build - not an official release. You should've flashed 23.x.x.x.167
Puffin617 said:
23.0.1.A.0.32 was a test build - not an official release. You should've flashed 23.x.x.x.167
Click to expand...
Click to collapse
Ah. My bad I just Googled the version number quickly while posting to be accurate (fail!). haha! I did do 23***167_R2B (Generic UK)
Hi gang!
I have a Moto E 2nd Generation here that was having some issues, browser crashing, slow downs, overheating issues due to multiple apps running, etc. So I decided to log into TWRP and attempt to do a factory reset. After this factory reset was done now I attempt to log into fastboot, which gives me the options of start, restart, factory, etc. I am just receiving a boot loop and nothing more. The steps to get this corrected is a bit jumbled and confusing, I must admit. I have installed ADB on my computer in hopes that this will be straightforward. I have downloaded some system images which I thought would help the process, negative. So if someone could help me this would be greatly appreciated.
- John
CheapStudent
cheapstudent said:
Hi gang!
I have a Moto E 2nd Generation here that was having some issues, browser crashing, slow downs, overheating issues due to multiple apps running, etc. So I decided to log into TWRP and attempt to do a factory reset. After this factory reset was done now I attempt to log into fastboot, which gives me the options of start, restart, factory, etc. I am just receiving a boot loop and nothing more. The steps to get this corrected is a bit jumbled and confusing, I must admit. I have installed ADB on my computer in hopes that this will be straightforward. I have downloaded some system images which I thought would help the process, negative. So if someone could help me this would be greatly appreciated.
- John
CheapStudent
Click to expand...
Click to collapse
Heyo John!
I can try to help since I have managed to overcome my bootloop issue and flash a custom ROM into my phone. Could I ask, are you trying to also install a custom ROM? And what version of TWRP do you have?
I had the bootloop issue because of an outdated TWRP and had to flash the latest one, which thankfully worked!
Let me know! ^_^
testerexp345 said:
Heyo John!
I can try to help since I have managed to overcome my bootloop issue and flash a custom ROM into my phone. Could I ask, are you trying to also install a custom ROM? And what version of TWRP do you have?
I had the bootloop issue because of an outdated TWRP and had to flash the latest one, which thankfully worked!
Let me know! ^_^
Click to expand...
Click to collapse
Hello testerexp345,
Thank you for the reply and the assistance, I am not sure if TWRP is installed anymore as I can't get passed the bootscreen on the phone. I hold down the volume down and power button to get the options of factory reset, shut down, restart, etc. However all these options lead back to the boot screen looping over. The ROM that I had installed on the phone was from an online seller that paired the phone with a SIM card that allowed unlimited data service, which was great for my business since I am out much of the week traveling. Any insight would help, as when it comes to flashing devices and cell phones... let's just say I am a newbie still
John C.
cheapstudent said:
Hello testerexp345,
Thank you for the reply and the assistance, I am not sure if TWRP is installed anymore as I can't get passed the bootscreen on the phone. I hold down the volume down and power button to get the options of factory reset, shut down, restart, etc. However all these options lead back to the boot screen looping over. The ROM that I had installed on the phone was from an online seller that paired the phone with a SIM card that allowed unlimited data service, which was great for my business since I am out much of the week traveling. Any insight would help, as when it comes to flashing devices and cell phones... let's just say I am a newbie still
John C.
Click to expand...
Click to collapse
To boot in bootloader while you stuck on bootlogo
Press and hold power button and volume button , and when screen goes off, quickly release power button only . don't release volume down button . now you will boot in bootloader
hamxa266 said:
To boot in bootloader while you stuck on bootlogo
Press and hold power button and volume button , and when screen goes off, quickly release power button only . don't release volume down button . now you will boot in bootloader
Click to expand...
Click to collapse
Hello hamxa266, okay I was able to get into the bootloader. All the options I choose restart the phone and put it back it back into a bootloop. I am not very familiar when it comes to using ADB.
John C.
cheapstudent said:
Hello hamxa266, okay I was able to get into the bootloader. All the options I choose restart the phone and put it back it back into a bootloop. I am not very familiar when it comes to using ADB.
John C.
Click to expand...
Click to collapse
I guess now you need to flash stock frimware using fastboot. if you are not familiar with then go and get familiar with it . It is not too hard just read few posts and thats it ..
If you need any help i am here!
Hi, I have the same issue, but I can't get it into recovery, but... Can I use "fastboot boot recovery.img"? for go into recovery for a factory reset and solve it, or I need to do something more, I have the same Moto, surnia with the bootloader locked, please I need help
testerexp345 said:
Heyo John!
I can try to help since I have managed to overcome my bootloop issue and flash a custom ROM into my phone. Could I ask, are you trying to also install a custom ROM? And what version of TWRP do you have?
I had the bootloop issue because of an outdated TWRP and had to flash the latest one, which thankfully worked!
Let me know! ^_^
Click to expand...
Click to collapse
Can u provide link for latest TWRP...??
mkranthikmr said:
Can u provide link for latest TWRP...??
Click to expand...
Click to collapse
This is the link for official twrp website
http://twrp.me/motorola/motorolamotoelte.html
Or you could use squid's twrp from here:
https://forum.xda-developers.com/mo.../twrp-squid-twrp-recovery-moto-e-lte-t3137649
shreyas_123 said:
This is the link for official twrp website
http://twrp.me/motorola/motorolamotoelte.html
Or you could use squid's twrp from here:
https://forum.xda-developers.com/mo.../twrp-squid-twrp-recovery-moto-e-lte-t3137649
Click to expand...
Click to collapse
Thank you bro... Got it already...:good:
Hello guys,
Yesterday i received an OTA Update to 7.1.1 and downloaded it and beggining the installation.
After that my phone doesnt boot anymore and keep appearing the message:
AP Fastboot Flash Mode (Secure)
failed to validate recovery image
ERROR: Failed to pass validation, backup to fastboot
I tried to install RSD Lite but my pc doesnt recognize my phone as "connected".
Please give me some help.
Reflashing a factoty image via fastboot could help. There are already some threads here, which will help you.
I followed this and got 7.1.1 by OTA right after installing. Using minimal ADB and fastboot to flash it worked fine.https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
supacrazyguy42 said:
I followed this and got 7.1.1 by OTA right after installing. Using minimal ADB and fastboot to flash it worked fine.https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Click to expand...
Click to collapse
Thanks my friend, I'll try this.
Is there a way to unlock my bootloader without enable the oem unlock on the phone?
My phone is stucked on 'AP Fastboot Flash Mode (secure)'.
Please give me some light guys.
Maybe there's an issue with the ota for 7.1.1. I got it here in the UK last night. It was working fine on 7.1.1 from what I could tell until the phone died later on the phone now will only boot to the no command screen. Tried hard reset but it doesn't help. Motorola have requested it sent for repair. Is this the same issue?
I have exactly the same darned problem!!! Motorola chat are worse than useless, simply following a flow chart with no knowledge.
bakerboy said:
I have exactly the same darned problem!!! Motorola chat are worse than useless, simply following a flow chart with no knowledge.
Click to expand...
Click to collapse
Yes the chat is like any other companies non tech savvy person following a script in fact it could quite easily be a bot haha. Anyway I got through the process and received a prepaid DHL label and have sent the phone for repair. Luckily my phone is under warranty I feel sorry for anyone with this problem and out of warranty I'm not sure how that would work even though the problem has arisen through Motorola's update.
Anyway I'll keep you updated on the outcome.
boromat said:
Maybe there's an issue with the ota for 7.1.1. I got it here in the UK last night. It was working fine on 7.1.1 from what I could tell until the phone died later on the phone now will only boot to the no command screen. Tried hard reset but it doesn't help. Motorola have requested it sent for repair. Is this the same issue?
Click to expand...
Click to collapse
Any solution? just one hour ago after power off and power on my phone it does not boot any more, only the same no command screen. I just updated to 7.1.1 the last thursday and all worked very well until today. Ha ha ha O just jumped from LG for the infamous boot loop problem with my G4 and now this. RETMX moto z.
Sent from my Redmi Note 4 using XDA-Developers Legacy app
---------- Post added at 10:44 AM ---------- Previous post was at 10:21 AM ----------
This working for me, enter into recovery Mode: press power and volume down at the same time then select recovey and you will see the same no command screen, then press power and volume up Keys at the same time, you will be enter in recovery mode, select mount system wait until complete, then select clean cache and wait until complete, now select power off, then try to power up your phone. If it does not result at the first time, try again. With this steps my phone turn on again.
Sent from my Redmi Note 4 using XDA-Developers Legacy app
the problem persist if I turn off the phone, unable to boot the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wtf with Lenovo / Motorola really is so dificult to they make something good? , this phone is crap.
Sent from my Redmi Note 4 using XDA-Developers Legacy app
pacherecords said:
the problem persist if I turn off the phone, unable to boot the phone.
Wtf with Lenovo / Motorola really is so dificult to they make something good? , this phone is crap.
Click to expand...
Click to collapse
Try this at the screen shown in your post :
1 press AND HOLD the power button
2 press the volume up button
You should see the recovery menu below
The volume buttons navigate the menu
3 First try Mount /system
4 Then try Wipe cache partition
5 Then Reboot
It worked for me once
lollyjay said:
Try this at the screen shown in your post :
1 press AND HOLD the power button
2 press the volume up button
You should see the recovery menu below
The volume buttons navigate the menu
3 First try Mount /system
4 Then try Wipe cache partition
5 Then Reboot
It worked for me once
Click to expand...
Click to collapse
I think that the problem is related to the micro sd card, just a few minutes ago I can reboot my phone but without the card. This problem begin after the ota update. I made a backup of the card and format it but the problem persist, trying to reboot with the card inserted im the phone but it enter into bootloop, I make some test to the card with my pc and other phone and the card is ok.
Sent from my Redmi Note 4 using XDA-Developers Legacy app
pacherecords said:
I think that the problem is related to the micro sd card, just a few minutes ago I can reboot my phone but without the card. This problem begin after the ota update. I made a backup of the card and format it but the problem persist, trying to reboot with the card inserted im the phone but it enter into bootloop, I make some test to the card with my pc and other phone and the card is ok.
Click to expand...
Click to collapse
That's good to know. What is the exact information on the SD card? Maybe we should not use it.
I am aware of some 128GB cards causing problems with booting
lollyjay said:
That's good to know. What is the exact information on the SD card? Maybe we should not use it.
I am aware of some 128GB cards causing problems with booting
Click to expand...
Click to collapse
I use a 128 gb Samsung evo select UHS-1, but I use this card with my Moto Z since october with Android 6.0 without problems.
Sent from my Redmi Note 4 using XDA-Developers Legacy app
pacherecords said:
I use a 128 gb Samsung evo select UHS-1, but I use this card with my Moto Z since october with Android 6.0 without problems.
Click to expand...
Click to collapse
Yes I think 7.1.1 has a problem with that one
lollyjay said:
Yes I think 7.1.1 has a problem with that one
Click to expand...
Click to collapse
Hi, only an update, after a little investigation a lot of Moto G4 plus had the same problem just after nougat update, all of them use Samsung evo 128gb cards and format the card using the phone does not make the things better. The last night I perform a format process to my sd card using my Windows 10 lap top , but I select long format (well uncheck the quick format box). I insert the card to the phone and the phone ask to format the card, I select as external storage after complete I turn off the phone and it boot without problems, I power off the phone a cuple of times and Works good.
Maybe this is the solution.
Sent from my Redmi Note 4 using XDA-Developers Legacy app
Hi all..
Same issue here.. Moto Z Droid.. updated to 7.1.1 via OTA yesterday... things were OK... saw some weird issues (not sure if they were related or just issues in general).... I decided to reboot my phone... and I can no longer boot.
Every boot results in the "No command" screen. Clicking "Volume Up + Power" for a few seconds (then releasing volume, then power) drops me into Android Recovery....
I've tried clearing cache .. "Mount /system" .. everything short of factory reset.
I don't currently have access to a SIM-eject tool to try booting up the phone without SD card. Will do this once I get home. Looking back into my order history, my SD card is: Samsung Evo Plus mc128d 128gb Uhs-i Class 10 Micro SD Card
I've tried scanning the logs from "View recovery logs", but didn't see anything that stood out.
amcq1010 said:
Hi all..
Same issue here.. Moto Z Droid.. updated to 7.1.1 via OTA yesterday... things were OK... saw some weird issues (not sure if they were related or just issues in general).... I decided to reboot my phone... and I can no longer boot.
Every boot results in the "No command" screen. Clicking "Volume Up + Power" for a few seconds (then releasing volume, then power) drops me into Android Recovery....
I've tried clearing cache .. "Mount /system" .. everything short of factory reset.
I don't currently have access to a SIM-eject tool to try booting up the phone without SD card. Will do this once I get home. Looking back into my order history, my SD card is: Samsung Evo Plus mc128d 128gb Uhs-i Class 10 Micro SD Card
I've tried scanning the logs from "View recovery logs", but didn't see anything that stood out.
Click to expand...
Click to collapse
Your SD card is almost certainly the problem. I think that after you remove the SD card you will be able to boot.
lollyjay said:
Your SD card is almost certainly the problem. I think that after you remove the SD card you will be able to boot.
Click to expand...
Click to collapse
I'll attempt to read through this thread again.. but, after removing SD and booting successfully (in the process now)... can I expect to be able to put it back in and be ok? Or, does it seem that this specific type of card will "never" work with 7.1.1?
I really wish I could boot it up far enough to be able to decrypt that SD to see exactly what is on it.
And lastly, is there any evidence as to which 128GB cards work on 7.1.1 with the Moto Z's?
lollyjay.. thanks for your quick reply.
amcq1010 said:
I'll attempt to read through this thread again.. but, after removing SD and booting successfully (in the process now)... can I expect to be able to put it back in and be ok? Or, does it seem that this specific type of card will "never" work with 7.1.1?
I really wish I could boot it up far enough to be able to decrypt that SD to see exactly what is on it.
And lastly, is there any evidence as to which 128GB cards work on 7.1.1 with the Moto Z's?
lollyjay.. thanks for your quick reply.
Click to expand...
Click to collapse
I can't say since I have my SD card as external storage
I don't like to use removable storage as extended internal
This is not anything new for experienced users, but it will help the newbies.
NOTE: This is, still, the standard process to flash stock ROMs on ANY Samsung running Android, you can use the same drivers, software and key combo for Download mode on other variant or model, what you need to change is the firmware file of course. So feel free to use this guide as reference.
The Stock ROM or Stock Firmware is the software that comes preinstalled in your phone when is brand new, in this case is Samsung's own modification of Android called TouchWiz. If you ran into problems like system apps FCs all the time, bootloops, softbricks,etc... Or if you adventure on the "custom world" (Root, Xposed, aftermarket roms, etc) and things go south, it happens... The stock rom can be flashed to fix those problems and/or get your phone back to a working state again, hence the importance of this procedure.
The tool to flash firmwares on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
Now you need the firmware for your SPECIFIC MODEL, country and carrier are not important, but model IS, deadly. So, don't even try to flash another variant stock rom in you phone, you can and will end up with a hard brick, and good luck fixing that.
Sammobile is the biggest repository for Samsung firmwares, so use that.
J320F and DS - J320F and J320F/DS (Dual SIM) are the same.
J320FN
J320H
J320M
J320FXXU0AQL1 Mirror on MEGA (Netherlands) - I downloaded it from Sammobile and re-uploaded to MEGA. Same .RAR5 stuff and Tecnoriales password.
For any other variant or any Samsung phone for that matter, use the search tool with your model: https://www.sammobile.com/firmwares/
How to flash the Stock ROM using OdinBefore you star please charge your battery to 100%.
1. Install the Samsung Drivers
2. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. Youll see a warning in the screen, accept it pressing Vol+.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
4. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
5. Click the AP button and load the *.tar file you downloaded from sammobile. i. e.: J320FXXU0AQL1_J320FDBT0AQK1_J320FXXU0AQI1_HOME.tar.md5 - At this point Odin will hang (stop responding) for some time while it loads the firmware file, that will depend on your PC, from some seconds to a couple of minutes. Be patient.
6. Once Odin un-freezes, go to Options Tab and make sure Re-Partition is unchecked.
7. Press Start to initiate the flashing process, it will take a while. The phone will reboot and when you see a green Pass in Odin it will be safe to unplug your phone..
First boot might take some time depending on the condition of your phone. That's it, your phone should be working again as intended (by Samsung).
Extra: Recovery Mode key combo with phone turned off is Vol+, Home and Power, from here you can perform a Factory Reset.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
Does this apply to the SM-J327P? It would greatly help newer users
Sent from my Samsung SM-J327P using XDA Labs
Sands207 said:
Does this apply to the SM-J327P? It would greatly help newer users
Sent from my Samsung SM-J327P using XDA Labs
Click to expand...
Click to collapse
For any Samsung running Android, since idk, the original Galaxy S? The process has not changed. Of course youll need to download the SPECIFIC Rom for your J327P.
mauriciognr said:
For any Samsung running Android, since idk, the original Galaxy S? The process has not changed. Of course youll need to download the SPECIFIC Rom for your J327P.
Click to expand...
Click to collapse
Thank you i appreciate it ?
Does this also restore stock recovery too?
I'm trying to avoid flashing twrp so that I can backup stock recovery but I can't get fastboot to work so my only option would be to flash the custom recovery onto the phone.
I don't want to be stuck without a way to restore stock recovery in case something goes wrong.
CyberZot said:
Does this also restore stock recovery too?
I'm trying to avoid flashing twrp so that I can backup stock recovery but I can't get fastboot to work so my only option would be to flash the custom recovery onto the phone.
I don't want to be stuck without a way to restore stock recovery in case something goes wrong.
Click to expand...
Click to collapse
Yes it restores stock recovery ,when flashing with Odin it will always flash stock recovery
Scorpionea said:
Yes it restores stock recovery ,when flashing with Odin it will always flash stock recovery
Click to expand...
Click to collapse
Thank you very much!
Thank you. Your post hepled me.
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Thank you for your help.
Bests regards.
Christophe
tof225391 said:
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Thank you for your help.
Bests regards.
Christophe
Click to expand...
Click to collapse
This is the wrong turtorial for you it is to get your phone back to your original software and thats 5.1.1
J320 to Android 7.1
tof225391 said:
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Click to expand...
Click to collapse
Even though it was mentioned this is the wrong page I don't see why you can't be given some helpful info. The firmware you're looking for to get Android 7.1 is, J320W8VLU2BQK1 J320W8OYA2BQK1 (Its listed for Canada) search for it online.
**Note
If you cant get through the welcome screen. Reset data on recovery
I can't get Odin to work on my SM-J320A (ATT version)
its running this firmware i think: J320AUCS3BQL2
and nougat 7.1.1
holding volume down + home + power. Odin mode starts and asks for confirmation. (volume up to continue, volume down to restart) But nothing happens. LOL All i can do is pull the battery and if i try recovery mode it says "No command", hangs for awhile then goes into recovery mode.
Is USB debugging on, required?
Odin mode works fine on my other Galaxy phones. Anyone have this issue before? thanks
CLovecraft said:
I can't get Odin to work on my SM-J320A (ATT version)
its running this firmware i think: J320AUCS3BQL2
and nougat 7.1.1
holding volume down + home + power. Odin mode starts and asks for confirmation. (volume up to continue, volume down to restart) But nothing happens. LOL All i can do is pull the battery and if i try recovery mode it says "No command", hangs for awhile then goes into recovery mode.
Is USB debugging on, required?
Odin mode works fine on my other Galaxy phones. Anyone have this issue before? thanks
Click to expand...
Click to collapse
Try to turn on usb debbuging and oem unlock
2gg1 said:
Try to turn on usb debbuging and oem unlock
Click to expand...
Click to collapse
Thanks.
Update: my soft brick issue is fixed now. (it was stuck on a boot loop for awhle but seems to have fixed itself after 20 reboots)
So i can boot into operating system.
Next i turned on OEM unlock and USB debugging but Odin mode still doesn't work, though.
Now, another minor problem. The home button doesn't work, but seems physically okay (this phone has barely been used and looks pristine) Could be a firmware issue related to Dalvik Cache. but without being able to flash firmware i cannot confirm. Recovery mode still shows a "No command" screen, dead robot, and 50 seconds later goes into what looks like stock recovery.
Update 2. Tried factory reset which seems to have helped. it boots faster into the operating system now. :good:
so i did this now i wanted to install touchwiz rome on 6,0,1 android but it bootloops i hear i need some baseband but what baseband i need someone can help pls
Looking for J320A
CLovecraft said:
Thanks.
Update: my soft brick issue is fixed now. (it was stuck on a boot loop for awhle but seems to have fixed itself after 20 reboots)
So i can boot into operating system.
Next i turned on OEM unlock and USB debugging but Odin mode still doesn't work, though.
Now, another minor problem. The home button doesn't work, but seems physically okay (this phone has barely been used and looks pristine) Could be a firmware issue related to Dalvik Cache. but without being able to flash firmware i cannot confirm. Recovery mode still shows a "No command" screen, dead robot, and 50 seconds later goes into what looks like stock recovery.
Update 2. Tried factory reset which seems to have helped. it boots faster into the operating system now. :good:
Click to expand...
Click to collapse
What did you end up doing to pull this off? I've got the exact same model phone, but cannot seem to find the firmware on Sammobile.