Database Info

need a help here please !

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 .

Converting P907 to P905

Hi all,
I own a P907 for several months. When purchasing I thought I can flash a custom recovery and flash any rom I want.
It seems the AT&T Bootloader is unchangeable.
I had an idea…
I hard briked my LG D855 (G3) and brought it back to life with a procedure I found on the XDA forums, JTAG, writing directly to the board (needed to open the device).
Is it possible to write directly to the board and then it will be possible to flash a custom recovery?
Thank you.

yuval gur said:
Hi all,
I own a P907 for several months. When purchasing I thought I can flash a custom recovery and flash any rom I want.
It seems the AT&T Bootloader is unchangeable.
.
Click to expand...
Click to collapse
P907A and P905V acutually are identical tablets but bootloader is locked by provider, P907A is from AT&T, P905V is from Verizon.
As long as bootloader is locked, you cannot flash different firmware to your tablet. Try to flash by Odin, you'll see it fails immediately.
I can swap mainboard of P907A to a P905V tablet or vice versa without any problem because the hardware is identical.
The P900 Wifi version, bootloader is not locked, you can flash whatever firmware you want.

I was wondering the same thing about my P905V. Would a hardware flasher work to write the P905 bootloader to it? It's such a shame that this very expensive tablet is stuck on a bloated and outdated Android version. At this point, it's so slow I wouldn't mind risking destroying it to try to get CM14.1.
Has anyone tried this conversion?

any updates on this matter ? as i would like to install any ROM with android 7 / 8 or 9

T-Mobile S4 - Accept OTA Update or Root first?

I am a newbie to GSM, so bear with me
T-Mobile is offering me an OTA update to M919UVUFOK3 every 24 hours. Is it too late already to keep EFuses from blowing, since KNOX came with the MK2 on my motherboard? In which case have I got nothing to lose by accepting the OTA update? This would be the most stable, OR
Should I root the MK2, install TWRP, and upgrade via ODIN? I'm not sure if they have OK3 for modded firmware yet, at the moment, all I want to do is upgrade to the latest, most stable firmware / kernel / modem I can while keeping as many E-Fuses intact (knox bit, anything that keeps me from being able to downgrade, root, install a custom ROM, or ressurect my device if it becomes hard-bricked.
Here's what I know about my S4
About Device:
Model Number
SGH-M919
Android Version
4.3
Baseband version
M919UVUEMK2
Kernel version
3.4.0-2015522
[email protected] #1
Sat Nov 16 14:22:56 KST 2013
Build number
JSS15J.M919UVUEMK2
SELinux status
Enforcing
SEPF_SGH-M919_4.3_0010
Secure boot status
Type: Samsung
Here's what I have observed about my phone so far:
* T-Mobile finally gave me a SIM card that works
* Full eMMC dump using RIFF (anything available upon request)
* KNOX is installed
* ODEX information was found on this phone when I looked through partitions in a hex editor
* Found code amongst the boot loader partition in WinHEX, "BootLoader.Rollback.BlowFuse" <<< NOT Warm and Fuzzy feeling
So, in short, do I have nothing to lose by accepting the OTA update (I believe it is still rootable), OR should I root my current firmware and do everything by hand? OTA would ensure greatest stability, but I still want it to be MY phone. Any suggestions?
If anyone wants my full eMMC dump, *.pit file, anything let me know (as long as it's not something personal like a certificate or IMEI)
P.S. - What are these "Security Policy Updates" it constantly is asking me to enable? My friend said they are harmless (don't do any permanent castration on rollback capability). What do they do? Can they update the security - against me? (like changing the lock on my front door and stealing my house)
I'm a newbie, so if some questions sound stupid just bear with me. I just want the latest firmware, mostly stock but rooted, and not burn my bridges to go back and do anything I may learn about later. I could just keep delaying the update, but 4.4.4 ran faster on my last phone and I like it, but want to be able to keep my options open.
Thanks

If this is a stupid question, I'm a newbie just point me in the right direction.
I know how to root, I know how to use odin, I just need to know if MK2 is already too far to not trip the KNOX thing. I'm not sure if KNOX is actually installed, but I have a good bet it is, as it's listed under "Device Administrators".
It may sound a tad crazy, but everytime they fry one of these on my (originally $700) phone, they may as well have literally violated me, raped me, as if they're willing to go THAT far to control how I use... um, what is it called when you purchase something? I mean when you buy something, who's property does that become? Oh yeah, it's MY property. In Django Unchained, although his character is evil (and I'm talking electronics no offense intended), Calvin Candie said exactly how I feel about eFuses, controlling what I can and can't do with items I purchase.
"This CPU here, is MY property... and I can choose to do... with MY PROPERTY... WHATEVER I so desire!"
I'm just asking what would be the best course of action as I'm torn between stability and "Keeping my Rights". For those who do not know what an eFuse is, it's literally a fuse that's 20nm wide embedded in the snapdragon CPU itself. It's the way they can make it impossible to downgrade or reset the KNOX bits. When a KNOX bit is set, a higher voltage is applied to this fuse and it is purposely overloaded, breaking the link and setting it to a "1". If we had the RSA private key to sign our bootloader, it would be no problem. Here's some info on eFuses
https://en.wikipedia.org/wiki/EFUSE
http://paris.utdallas.edu/ssiri08/Tonti_SSIRI_eFuse_V2.pdf

Delete .bin files from older firmware to downgrade to an older bootloader version?

Id like to downgrade my S7 from nougat to marshmallow. My current lowest factory reset option is nougat on bootloader version 3. Id like to downgrade to a downloaded stock firmware that uses version 1 of the bootloader.
my device is currently rooted and carrier unlocked
ive made a full backup of the nougat system, before ive done anything to it other than the rooting.
ive been reading around that some people were able to bypass the downgrade bootloader lock error in odin by first going into their desired downgraded firmware tar files and deleting any file that ends in .bin , and then successfully been able to flash the older firmware. what I want to know is if i decide to try this, and it still doesnt work in odin, or something still doesnt work properly - am i still able to fully restore from that backup ive just made? has anyone done this without issues? i hate the look and feel of nougat and oreo looks and feels the exact same...
i did make another thread about downgrading, but i didnt know nearly as much at the time. Been told downgrading is impossible and thats true, officially speaking. Id just like to know if anyone has been successful with this workaround.

What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.

Beanvee7 said:
What model, SM-G930F? Is OEM Unlocking turned on?
If it's a G930U/V/T/A/P then you won't be able to.
For the G930F so long as you don't have the latest Nougat version it shouldn't prevent downgrading. Otherwise upgrading up to Oreo then back down just by flashing in Odin should work, as Oreo doesn't have the downgrade lock that the newest Nougat has.
Click to expand...
Click to collapse
model is sm-g930w8 but yes OEM unlocking is on, and so is usb debugging just to be on the safe side. It is running the very first version of nougat right now, 7.0. But the security patch is from feb 2018. Ive read that the bootloader itself is unlocked on this version of the phone though, its just that downgrade protection in the software that could get in the way, if what i read was correct? in the same place was where i read that deleting those bin files from the firmware i want to install would be a good workaround, it would make the bootloader not check it at all if i read it correctly.
i havent tried anything yet, ive been doing my research first to stay on the safe side. it might work without issues, but I want to be prepared for if issues do arise, what the correct next step should be to keep the device itself not bricked

Yea not 100% sure for the G930W8, it's the same SoC as the G930F but the firmware restrictions could be different since it's the Canada specific version

so, i decided to brave it and try it, since to read around you find alot of conflicting information... i was suspecting that odin would fail shortly after starting at sboot.bin if it was the bootloader thats the issue. but it didnt. it failed the very next step after that at param.bin.
anyone happen to know what param.bin means?

What files are you trying to flash? I have had the same problem, even though the bootloader is unlocked the device has efuses that prevent downgrade to older binary. I was using U2 binary and only managed to downgrade to nougat u2 binary version. Even when I skipped bootloader files, marshmallow would still give an error that system.img is version 0 where as device is v1

Samsung Galaxy J710F (6) After 10 days of trying ,I get same results .How to fix this issue?

DM verity failed
Frp locked
Bricked
Unlocked bootloader.
Odin different errors! If everything goes fine it stucks at something for minutes /hours then give fail message!
Smart switch is useless
Adb sideload /fastboot , the only commands that responds is the one used to get connected devices. When I try to flash there it reboot to recovery instantly.
Recovery is damaged or blocked!!
I cannot instal TWRP because the phone is locked.
I can flash only a stock firmware for my region . Is region matter? (no need to unlock??)
Please browse the pictures . Everything is portrayed. Simply I cannot flash! My mother's device. Not only me. But also the technicians!

Reflash phone's Stock ROM to get rid off of all modifications you applied so far.

[RESOLVED]Thank you.
The issue :I used frija to give me the last firmware for my region and the firmware was downgraded , B:4 .it is the last for my region , security level 4 . While the frimware I need to replace , is B6 ,its SWREV is B6 ,K1 S2. So level 6. I tried low level B for 10 days it is why I got Fail messages all the time. But did not give up. I'm a newbie thou. Learned many things in this processe .I used all possible tricks trying to solve the issue.
I thought it is obligatory to flash a firmware from same region if the bootloader is locked , and FRP is locked. I read it from a blog but no! The value of B , stands for security level and bootloader matters. Also the phone version SM-J710F matters ,That 's it. If you flashed ROM with higher B , and failed then adjust the technical stuffs, USB , ports and so on . Or try a Combination frimware create one or get it from the net , use pit files too...goodluck . Dear reader