need a help here please ! - Moto Maxx Q&A, Help & Troubleshooting

i have a moto maxx xt1225 brazilian model , bought it from a trusted Brazilian seller on the net , the phone came with the version 5.0.2 from the box , my phone keeps restart randomly many times a day with a normal terms of use like whatsapp and facebook , no odd applications or heavy games at all . i entered the bootloader and everything seems to be normal but the software status said it is ( modified ) . what i need to do to solve this problem please ? i cant stand this phone anymore and i am considering return it . if i unlocked the bootloader and flashed a custom rom can i return the phone to its stock status again without the seller notice that i changed something in the software ? i saw some pics taken by members here said that the software status is official but the bootloader is unlocked and the status number indicated to 3 .

Someone has certainly "messed" with the phone if it shows modified. I would perform a complete reflash of the 5.0.2 firmware using RSDlite.

Steve-x said:
Someone has certainly "messed" with the phone if it shows modified. I would perform a complete reflash of the 5.0.2 firmware using RSDlite.
Click to expand...
Click to collapse
now the device is locked and status code refered to zero . . . if i did a complete reflash of the 5.0.2 firmware using RSDlite would this change these facts ? ( device is locked . status code : 0 ).

Dark Obsessions said:
if i unlocked the bootloader and flashed a custom rom can i return the phone to its stock status again without the seller notice that i changed something in the software ? i saw some pics taken by members here said that the software status is official but the bootloader is unlocked and the status number indicated to 3 .
Click to expand...
Click to collapse
IF you unlock the bootloader and flash a custom ROM, why would you want to return it? Are you thinking it has defective hardware? And that is causing the random rebooting?
If you re-flash stock 5.0.2 without unlocking the bootloader, it might fix the issue. The status of the booloader will not change. But flashing anything without unlocking the bootloader is a risk. Make sure you have the right image, etc.

i bought this phone as a new unused device from a famous hypermarket here in brazil , and i think finding what is supposed to be a new device with a software modified in bootloader not a thing to be forgiven , so i reported that to procon here , and i am waiting for their respond .
if i do the flash with the locked bootloader , would this change the status code from 0 to 1 ?

Dark Obsessions said:
i bought this phone as a new unused device from a famous hypermarket here in brazil , and i think finding what is supposed to be a new device with a software modified in bootloader not a thing to be forgiven , so i reported that to procon here , and i am waiting for their respond .
if i do the flash with the locked bootloader , would this change the status code from 0 to 1 ?
Click to expand...
Click to collapse
No you can flash stock XML rom on a bootloader locked phone, is the stock ROM made by motorola for the phone doesn't need to the bootloader be unlocked, and that doesn't change anything to the bootloader.
But make a factory reset first...
fallow this instructions:
Para restaurar o dispositivo:
That will erase everything on the device and make a fresh install of the OS that is already in the device, so backup any photo file that you not wanna to loose.
Yours problem seems a bad update, did you update the OS after receiving it, there is a small update for 5.0.2 my came with 5.0.2 but not with the last update i did a OTA after receiving it...
If that doesn't help you can try to flash a stock XML ROM... But if you thinking in returning it do not unlock the bootloader, and try to contact motorola in that link that i share, i had a Hardware problem with my moto G and motorola Help, help me...

thanks for your respond ... i dont know how to explain the case well , but having a sealed new bought phone with a software statued to be modified out of the box is somthing uncommon i believe . when i checked for a new software update it says that mine is up to date ... anyway , i reported the case to procon and motorola ... motorola said that they wont sell a device with such state and the problem is for sure from the retailer .

Related

[Q]

Hello if someone could help me with my sch-i535 I would appreciate it soooo much. I bricked my phone by trying to flash cyanogenmod after taking the 4.3 update... Obviously I am new. I tried everything , lots of tries with Odin , I made an image on my sd card with win32 disc imager , I tried a bootloader unlock code with Odin...nothing worked. Then I went onto a Verizon forum , and the very thing that hurt me , the Verizon update assistant , un-bricked my sch-i535. The update assistant has an option "Repair Assistant" I ran this as the instructions said ...connected my phone to my laptop , and unbelievably an hour or so later it finished , and my phone just booted up. I had almost given up...I was ready to do a JTAG. Also my phone was updated to 4.4.2 Kit Kat.
So , my question is: Is there any way to flash cyanogenmod , on the sch-i535 after the 4.3 update ? I read somewhere in the forums that the Firmware can be changed , so that the bootloader is not locked.....or am I doomed to use the Verizon , bloated , battery stealing software ?
williamacker said:
Hello if someone could help me with my sch-i535 I would appreciate it soooo much. I bricked my phone by trying to flash cyanogenmod after taking the 4.3 update... Obviously I am new. I tried everything , lots of tries with Odin , I made an image on my sd card with win32 disc imager , I tried a bootloader unlock code with Odin...nothing worked. Then I went onto a Verizon forum , and the very thing that hurt me , the Verizon update assistant , un-bricked my sch-i535. The update assistant has an option "Repair Assistant" I ran this as the instructions said ...connected my phone to my laptop , and unbelievably an hour or so later it finished , and my phone just booted up. I had almost given up...I was ready to do a JTAG. Also my phone was updated to 4.4.2 Kit Kat.
So , my question is: Is there any way to flash cyanogenmod , on the sch-i535 after the 4.3 update ? I read somewhere in the forums that the Firmware can be changed , so that the bootloader is not locked.....or am I doomed to use the Verizon , bloated , battery stealing software ?
Click to expand...
Click to collapse
Nope. Once you've taken the OTA to 4.3 ML1 your stuck on a locked bootloader permanently
There is no way to downgrade or flash custom roms. Your limited to TW(Touchwiz) based only and anything other than those is out of the question
Sent from my Nexus 5
Hard to understand
ShapesBlue said:
Nope. Once you've taken the OTA to 4.3 ML1 your stuck on a locked bootloader permanently
There is no way to downgrade or flash custom roms. Your limited to TW(Touchwiz) based only and anything other than those is out of the question
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for replying ... That is hard for me to understand , my phone was bricked ... and obviously Verizon has a line or two of code , that unlocked my bootloader , inside their "Repair assistant". The repair assistant then installed Kit Kat on my phone. If the bootloader can be unlocked by code ... and Kit Kat installed , then it stands to reason that other ROM's could be downloaded , if someone could figure out the code that Verizon uses to unlock the sch-i535. I know that this would help more than one or two people , from reading the forums.
williamacker said:
Hello if someone could help me with my sch-i535 I would appreciate it soooo much. I bricked my phone by trying to flash cyanogenmod after taking the 4.3 update... Obviously I am new. I tried everything , lots of tries with Odin , I made an image on my sd card with win32 disc imager , I tried a bootloader unlock code with Odin...nothing worked. Then I went onto a Verizon forum , and the very thing that hurt me , the Verizon update assistant , un-bricked my sch-i535. The update assistant has an option "Repair Assistant" I ran this as the instructions said ...connected my phone to my laptop , and unbelievably an hour or so later it finished , and my phone just booted up. I had almost given up...I was ready to do a JTAG. Also my phone was updated to 4.4.2 Kit Kat.
So , my question is: Is there any way to flash cyanogenmod , on the sch-i535 after the 4.3 update ? I read somewhere in the forums that the Firmware can be changed , so that the bootloader is not locked.....or am I doomed to use the Verizon , bloated , battery stealing software ?
Click to expand...
Click to collapse
williamacker said:
Thanks for replying ... That is hard for me to understand , my phone was bricked ... and obviously Verizon has a line or two of code , that unlocked my bootloader , inside their "Repair assistant". The repair assistant then installed Kit Kat on my phone. If the bootloader can be unlocked by code ... and Kit Kat installed , then it stands to reason that other ROM's could be downloaded , if someone could figure out the code that Verizon uses to unlock the sch-i535. I know that this would help more than one or two people , from reading the forums.
Click to expand...
Click to collapse
The bootloader used to be able to be unlocked on this phone prior to the 4.3 ML1 update. Just because the firmware can be changed by Verizon does not mean the bootloader is unlocked. If it were as simple as figuring out the code Verizon used, then the bootloaders on all the locked phones on Verizon would have been unlocked by now. The problem is there is a security key and signature verification that is found in several partitions on the phone. The signatures must match or the phone will not boot up. The repair assistant was using official Verizon firmware which contained all the proper signature verifications. That is why it was able to install Kit Kat on your phone. A lot of smart people have been trying for several years now to find or crack the signature verification checks on quite a few phones without success. On Verizon, once you have a phone with a locked bootloader, you are stuck with that and their bloated software.

S6- SM-G920F firmware upgrade --hang @ logo screen --please help urgent

Hi All,
Have s6 SM-G920F international model. now my brother accidentally try wrong attempts in pin to unlock the phone. so phone got locked. and i give to guy who unlock the phone and after that i am not able to get official update . so have decided to install official stock firmware. details are below. when phone is return back to me have below version.
Old firmware :-
G920FXXU1AOCY 5.0.2 Lollipop, Initial release on 3/29/2015 for EE only.
New firmware which i try using ODIN :-
G920FXXU3QOJF Galaxy S6 SM-G920F 5.1.1 Stock Firmware -- This firmware is officially released on November 2015 for EE UK Galaxy S6 alone.Build date: October 12, 2015.
Got success in above firmware , PASS is result in ODIN.
But when phone reboot after this ,after erasing screen appear then it hang on logo screen. have waited around 20 mins but nothing happen. Have tried recovery mode also via wipe cache / factory reset , no change in result.
Have again try to install G920FXXU1AOCY but got sof rev fail in ODIN .
Have tried samsung switch for software update it's successful but when phone reboot it again stop there at logo screen.
In recovery mode -- G920FXXU3QOJF this show on top.
I don't whether phone was root or not as guy says he just unlock the phone. got this from UK .
Can anyone please help which firmware will now work on this case ? how to solve this issue.
Please help me as i mess up with my phone which work great before .
Tons of thanks to all.
Is there any firmware which work on all unlock or root phone for this model ? the above step from 5.0.2 have installed 5.1 is correct step ? i am working this phone from india,before doing this firmware update my sim card work properly. as phone was already unlock or rooted (not sure here whether it's rooted or not but sure as it's unlocked phone) as i can see EE apps in phone. please help me . it's hurt me on my decision to do this upgrade and create mess. :crying:
Can anyone pls help.. Thanks
dbarot87 said:
Can anyone pls help.. Thanks
Click to expand...
Click to collapse
have you solved this yet?
this helped me:
http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395

MOTO G 2015 XT1544 , Bricked ?

Hi, guys
i have a MOTO G 2015, model XT1544 , and i would like some help with some issues i'm suffering .
First i got the startup blocked from google account ( i forgot the email ), so to solve this i think i could reinstall the stock rom on it, but after trying for a few hours i didnt get any results. The bootloader was blocked and did not knew that , the rom never got installed sucessfully.
So now the phones starts normally, but i cant find any wifi connections, i think the wifi stopped working.
I need the wifi working to insert my google account on the device , or at least try to remember it .
Is there any way i could unlock oem from fastboot ? Or at least reinstall the stock rom on it with bootloader blocked ? i downloaded a few stock roms to the XT1544 model but they cannot be installed successfully, is this normal ?
PS. I really cant send it to motorola , i've lost the box of the phone and with it, the invoice and all documents.
Sorry for my bad english , im from Brazil , and thanks for your help
4652 said:
Hi, guys
i have a MOTO G 2015, model XT1544 , and i would like some help with some issues i'm suffering .
First i got the startup blocked from google account ( i forgot the email ), so to solve this i think i could reinstall the stock rom on it, but after trying for a few hours i didnt get any results. The bootloader was blocked and did not knew that , the rom never got installed sucessfully.
So now the phones starts normally, but i cant find any wifi connections, i think the wifi stopped working.
I need the wifi working to insert my google account on the device , or at least try to remember it .
Is there any way i could unlock oem from fastboot ? Or at least reinstall the stock rom on it with bootloader blocked ? i downloaded a few stock roms to the XT1544 model but they cannot be installed successfully, is this normal ?
PS. I really cant send it to motorola , i've lost the box of the phone and with it, the invoice and all documents.
Sorry for my bad english , im from Brazil , and thanks for your help
Click to expand...
Click to collapse
Make an account with Motorola.
Request bootloader unlock from Motorola.
Unlock bootloader.
Profit.
You really have no reason not too at this point.
Edit - but if you're trying to just fastboot a stock image it should work regardless if bootloader is unlocked or not so it sounds like you've used the wrong device image. If you don't want to reset anything find the boot.IMG of the correct image and fastboot that.
Your radio is not correct, that's what boot.IMG is.

How to actualy archive a nearly stock situation?

Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device

Someone HELP!!!

Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number

Categories

Resources