Data does not stick on reboots (Full story inside) - Moto Maxx Q&A, Help & Troubleshooting

Hi! Long time lurker, and I am using my first post to request for help. I haven't had to before, as I am usually able to use existing resources on XDA to fix my previous phones. Right now, I am stuck.
I have a Moto Maxx XT1250. I am using it on T-Mobile. I do not know what information will be useful in resolving this issue, so I am listing anything that might have attributed to the problem.
What I did with the phone:
Received used with stock KK installed. I did not test my SIM.
Unlocked bootloader.
Install TWRP-mod and fully backed-up everything, including modem partition.
(This is where I'm fairly positive I derped hard) Installed Brazil 6.0.1 stock SOAK via TWRP.
Lose IMEI info. I still have not tested my SIM.
Wipe everything in TWRP and restore original full KK backup. IMEI returns.
Installed ResurrectionRemix MM with OpenGAPPS slim first to test. It was OK.
Full wiped RR MM (system, data, cache, dalvik) and installed Mokee MM release w/ OpenGAPPS slim. Liked it!
Customized everything the way I wanted (Xposed, app restore via TitaniumBackup, etc.).
Inserted SIM.
Turned on phone, signal cuts out every few seconds. Always starts at 3 bars, then no service, back to 3 bars, and so on. I can make calls, sometimes receive. Sending and receiving texts is intermittent at best, almost nothing at worst. No data. Checked to make sure APN was correct (it was).
So I'm fairly positive flashing the 6.0.1 Brazil SOAK was my big no-no (against the advice of experienced members like ChazzMatt). Almost definitely messed up something regarding the modem and radio. Everything else works without issue though.
In my attempt to resolve the issue:
Checked forums regarding radio issues. Flashed clear_modem_status.zip first. No go.
Flashed QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE.zip and it works!
Rebooted phone. Problem comes back.
From here, whenever I flash either the original latest radio zip or the clear_modem_status.zip, I have full service. Once I reboot, I encounter the signal issue again.
Attempted to restore modem via TWRP from clean stock KK backup. No signal.
Tried fastboot oem config fsg-id lra_gsm command. No go.
I am a bit stumped right now. But at this point, I am fairly positive I will have to flash back to stock 5.0.2 via RSDLite, then redo TWRP/flash ROM/Xposed/user customization again. However, I am curious if there is anything else I can try before doing this. I appreciate any response in advance, and can (attempt) to provide any further information I may have neglected to mention.

Update!
Update! So I decided to wipe everything and flash XT1250_QUARK_LRA_5.0.2_LXG22.33-12.27_cid9_subsidy-DEFAULT_CFC.xml via mfastboot. After starting up the phone again:
Going through the setup process, I encountered an issue where the SIM could not be detected. IMEI was also missing, once again.
Dumbfounded, I restored the modem portion of my stock KK backup. Now the SIM is read, the IMEI is present, and I get full service. This persisted through two reboots!
So I flashed the QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE bootloader, radio, and gpt again... and the SIM/IMEI problem happened again.
I have found that, after restoring the stock KK modem backup:
If I flash the radio, that's when the problem occurs.
If I flash the gpt and/or bootloader, all is well.
I will now try to restore my Mokee MM backup w/ the stock KK modem. Hope it works!

Update 2!
OK. I am now stuck. I have flashed two different firmware files via RSDLite and the LP OTA from KK. These flashes included radio.img, and once these are flashed, my IMEI dissapears. The only way I have my IMEI is with my stock KK backup modem. I can use KK and LP stock without issue after restoring the backup modem, but I still have trouble with Mokee MM.
Any advice would be greatly appreciated, thanks!

Forgive me if I miss a couple of points. I'm not sure I have a total solution, but maybe a couple of suggestions.
alarsama said:
What I did with the phone:
Received used with stock KK installed. I did not test my SIM.
Unlocked bootloader.
Install TWRP-mod and fully backed-up everything, including modem partition.
(This is where I'm fairly positive I derped hard) Installed Brazil 6.0.1 stock SOAK via TWRP.
Lose IMEI info. I still have not tested my SIM.
Wipe everything in TWRP and restore original full KK backup. IMEI returns.
Installed ResurrectionRemix MM with OpenGAPPS slim first to test. It was OK.
Full wiped RR MM (system, data, cache, dalvik) and installed Mokee MM release w/ OpenGAPPS slim. Liked it!
Customized everything the way I wanted (Xposed, app restore via TitaniumBackup, etc.).
Inserted SIM.
Turned on phone, signal cuts out every few seconds. Always starts at 3 bars, then no service, back to 3 bars, and so on. I can make calls, sometimes receive. Sending and receiving texts is intermittent at best, almost nothing at worst. No data. Checked to make sure APN was correct (it was).
So I'm fairly positive flashing the 6.0.1 Brazil SOAK was my big no-no (against the advice of experienced members like ChazzMatt). Almost definitely messed up something regarding the modem and radio. Everything else works without issue though.
In my attempt to resolve the issue:
Checked forums regarding radio issues. Flashed clear_modem_status.zip first. No go.
Flashed QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE.zip and it works!
Rebooted phone. Problem comes back.
From here, whenever I flash either the original latest radio zip or the clear_modem_status.zip, I have full service. Once I reboot, I encounter the signal issue again.
Attempted to restore modem via TWRP from clean stock KK backup. No signal.
[*]Tried fastboot oem config fsg-id lra_gsm command. No go.
I am a bit stumped right now. But at this point, I am fairly positive I will have to flash back to stock 5.0.2 via RSDLite, then redo TWRP/flash ROM/Xposed/user customization again. However, I am curious if there is anything else I can try before doing this. I appreciate any response in advance, and can (attempt) to provide any further information I may have neglected to mention.
Click to expand...
Click to collapse
Yes, installing soak test for a different Android OS for a phone with a different FCC ID, different internal storage (32GB vs 64GB) is the root of your issues.
I'm surprised you were able to re-flash the Lollipop bootloader and it worked. With the Marshmallow soak test it would seem you were on a Marshmallow bootloader and normally you can't downgrade that. Normally you have to flash everything except for gpt.bin if going back from factory image to a lower Android OS factory image.
The current Mokee, even though Marshmallow actually uses Lollipop bootloader.
[*]Tried fastboot oem config fsg-id lra_gsm command. No go.
Click to expand...
Click to collapse
That would have been one of my suggestions.
alarsama said:
Update! So I decided to wipe everything and flash XT1250_QUARK_LRA_5.0.2_LXG22.33-12.27_cid9_subsidy-DEFAULT_CFC.xml via mfastboot. After starting up the phone again:
Going through the setup process, I encountered an issue where the SIM could not be detected. IMEI was also missing, once again.
Dumbfounded, I restored the modem portion of my stock KK backup. Now the SIM is read, the IMEI is present, and I get full service. This persisted through two reboots!
So I flashed the QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE bootloader, radio, and gpt again... and the SIM/IMEI problem happened again.
I have found that, after restoring the stock KK modem backup:
If I flash the radio, that's when the problem occurs.
If I flash the gpt and/or bootloader, all is well.
I will now try to restore my Mokee MM backup w/ the stock KK modem. Hope it works!
Click to expand...
Click to collapse
alarsama said:
OK. I am now stuck. I have flashed two different firmware files via RSDLite and the LP OTA from KK. These flashes included radio.img, and once these are flashed, my IMEI dissapears. The only way I have my IMEI is with my stock KK backup modem. I can use KK and LP stock without issue after restoring the backup modem, but I still have trouble with Mokee MM.
Any advice would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Forgive me if I am suggesting something you have already tried.
First, save off all your data you think you need.
Then, in TWRP exhaustively reformat your entire partition. I forget the command, you can look it up, but it's not the "quick" format -- it's the one that takes like 30 minutes. It makes my phone get very hot so I stick it in the refrigerator.
Next, how about flashing the stock 5.0.2 but excluding the gpt.bin? Flash with your SIM card in.
Then after flashing that, re-flash the radio again -- with the SIM card in:
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
If that doesn't work, try that again this time flashing with gpt.bin. But I'm just hesitant to recommend you flash a lower bootloader partition (Kitkat or Lollipop) since you originally had flashed the soak test (for a different Quark) of Marshmallow. Even though you've already done it several times now. :silly:
If I was adventurous (and I'm not), I might even re-flash the soak test gpt.bin (since downgrading from that is probably what's confusing your system), then flash Mokee + radio, but not the bootloader -- just ROM and radio with the
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
Somebody like @Skrilax_CZ or @baybutcher27, who has very extensive experience in these matters would be a better advisor. Besides several Nexus devices and a few LG smartphones, my experience flashing my Quarks is mostly desiring to not mess them up. I did flash Moto Maxx XT1225 to Moto Turbo XT1225 to get Lollipop, and flashing CM ROMs, and later re-flashing updated Puerto Rico 5.0.2 radio. But I'm not an msfastboot expert.

Hi ChazzMatt!
It does make sense that the Brazil 6.0.1 SOAK is the root of my issues. Do not apologize, any suggestion is more than welcome!
I have backed up all my important data.
I have looked for TWRP terminal commands with little success. Might general Linux terminal commands work in place?
I actually have flashed the gpt.bin for stock KK and stock LP MULTIPLE times... I'm not sure how much that affects anything >.<
I will otherwise try everything you have suggested and get back with an update. Thanks for your advice and information, it has helped me understand my situation more.

So while I was working on the phone, I realized a few things...
ChazzMatt said:
I'm surprised you were able to re-flash the Lollipop bootloader and it worked. With the Marshmallow soak test it would seem you were on a Marshmallow bootloader and normally you can't downgrade that. Normally you have to flash everything except for gpt.bin if going back from factory image to a lower Android OS factory image.
The current Mokee, even though Marshmallow actually uses Lollipop bootloader.
Click to expand...
Click to collapse
I had installed the 6.0.1 MM Brazil Soak 3 via TWRP with this guide: http://forum.xda-developers.com/moto-maxx/help/tutorial-moto-maxx-6-0-1-brazil-soak-t3340820. In that case, it would not have installed the MM bootloader or partition table (gpt.bin), correct? It would explain why I am still able to flash stock LP (and for some strange reason, stock KK). I think this point is corroborated by the fact that, when I flash gpt.bin for stock LP via fastboot, it is successful. But when I flash gpt.bin for stock KK, it fails. So right now, I am fairly positive I am using the LP bootloader, and this may be why Mokee boots without issue (except the whole signal thing that plagues me).
ChazzMatt said:
Then, in TWRP exhaustively reformat your entire partition. I forget the command, you can look it up, but it's not the "quick" format -- it's the one that takes like 30 minutes. It makes my phone get very hot so I stick it in the refrigerator.
Click to expand...
Click to collapse
So far, I have not been able to find these commands. Could you point me in the right direction?
ChazzMatt said:
Next, how about flashing the stock 5.0.2 but excluding the gpt.bin? Flash with your SIM card in.
Then after flashing that, re-flash the radio again -- with the SIM card in:
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
If that doesn't work, try that again this time flashing with gpt.bin. But I'm just hesitant to recommend you flash a lower bootloader partition (Kitkat or Lollipop) since you originally had flashed the soak test (for a different Quark) of Marshmallow. Even though you've already done it several times now. :silly:
Click to expand...
Click to collapse
I have done as you have instructed. No go.
ChazzMatt said:
If I was adventurous (and I'm not), I might even re-flash the soak test gpt.bin (since downgrading from that is probably what's confusing your system), then flash Mokee + radio, but not the bootloader -- just ROM and radio with the
mfastboot flash radio radio.img
fastboot oem config fsg-id lra_gsm
Click to expand...
Click to collapse
So I tried a (sort of) variation of these instructions. As I do not have the MM gpt.bin, I full wiped (system/cache/dalvik/data/internal storage), flashed Mokee, then flashed the radio via mfastboot and set the fsg-id to lra_gsm. Upon first boot, the SIM is read, I see my IMEI, baseband is present, etc. However, after a reboot, same issue occurs (no data, weak signal meaning missed calls and texts not sent/received).
I have found that, when I either flash the clean_modem_status.zip or the LP radio, the problem disappears. It's only on the next reboot(s) that the problem comes back. Therefore, this is primarily a modem/radio issue.
ChazzMatt said:
Somebody like @Skrilax_CZ or @baybutcher27, who has very extensive experience in these matters would be a better advisor. Besides several Nexus devices and a few LG smartphones, my experience flashing my Quarks is mostly desiring to not mess them up. I did flash Moto Maxx XT1225 to Moto Turbo XT1225 to get Lollipop, and flashing CM ROMs, and later re-flashing updated Puerto Rico 5.0.2 radio. But I'm not an msfastboot expert.
Click to expand...
Click to collapse
It would be fantastic if they could lend me their aid, and hopefully they view this thread and advise me as well, but I still appreciate the advice you have given.

alarsama said:
So far, I have not been able to find these commands. Could you point me in the right direction?
Click to expand...
Click to collapse
I believe it's the secure erase function of TWRP. It overwrites all bits of your internal memory.
All I can find is an older version of TWRP that does it, uploaded by @baybutcher27
https://androidfilehost.com/?fid=24052804347796742
[QUOTE ] @baybutcher27About secure erase:
Secure erase is:
When a Secure Erase command is sent, data in the
specified memory addresses must be purged from the
physical memory array
“Logical” memory erase is not acceptable.
I determined that in the TWRP secure erase, the only ting be done is to, erase every file after a process start to "purged" fill it block of memory with zero (or one) making impossible to some one to restore any of the previously data.[/QUOTE]

Related

No service!!! On kk modems.

i need help this problem has been there with me since i bought my opo 2 months back. i received it with cm11s build which was not official. so i had to manually upgrade my opo to cm12s after that i have flashed many lp roms even cm12.1s but never a kk rom. then i felt like going back to kk i flashed @Bobbi lim cm11s mod rom 3.5 and i got no service tried many things still no service i then flashed cm11s 44s factory image but still got no service. then i gave up and continued to stay on lp roms. then till recently i found that it was not the roms but the modem if i flashed lp modem on kk roms i got service but with black screen bug but when i flashed back kk modem again no service.
please help me is there something wrong with my opo hardware. @Heisenberg @Vivek_Neel and anyone else who has solution to this problem.
sorry for making it so long.
vicelord97 said:
i need help this problem has been there with me since i bought my opo 2 months back. i received it with cm11s build which was not official. so i had to manually upgrade my opo to cm12s after that i have flashed many lp roms even cm12.1s but never a kk rom. then i felt like going back to kk i flashed Bobbi lim cm11s mod rom 3.5 and i got no service tried many things still no service i then flashed cm11s 44s factory image but still got no service. then i gave up and continued to stay on lp roms. then till recently i found that it was not the roms but the modem if i flashed lp modem on kk roms i got service but with black screen bug but when i flashed back kk modem again no service.
please help me is there something wrong with my opo hardware. HeisenbergVivek_Neel and anyone else who has solution to this problem.
sorry for making it so long.
Click to expand...
Click to collapse
Did you flash *fastboot images* of CM11S?
If yes and still if you are facing radio problems, please refer http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 and try out KK modems
Otherwise please flash OxygenOS and give it a try.
@Mr hOaX i have flashed fastboot images of cm11s with toolkit and manually too still no service and as i have said i get service on all lp roms including oxygen os. I have tried flashing modems using twrp 2.8.6.0 still got no service whatsoever with kk modems but with lp modems i get service even on lp roms if i flash kk modem i instantly get no service after booting back up.
vicelord97 said:
@Mr hOaX i have flashed fastboot images of cm11s with toolkit and manually too still no service and as i have said i get service on all lp roms including oxygen os. I have tried flashing modems using twrp 2.8.6.0 still got no service whatsoever with kk modems but with lp modems i get service even on lp roms if i flash kk modem i instantly get no service after booting back up.
Click to expand...
Click to collapse
Firstly, make sure your TWRP is 2.8.6.0
Secondly, flash KitKat firmware before flashing any kitkat ROM.
Thirdly, don't use toolkits.
To your problem, here's my suggestion. Do a full wipe in TWRP. Flash KitKat firmware A FEW TIMES - PREFERABLY 5 TIMES. Each time with a cache and dalvik cache in between. After that do a full wipe again and flash the KitKat rom. Not sure if its placebo but that's what I did to get KitKat working after I switch back from 5.x to 4.4 and have the same problem as you.
If it doesn't work, do a full wipe in TWRP. After that flash factory images except recovery and userdata. You should be good to go to flash my ROM.
By full wipe u mean clean flash or including internal storage?
And thanks will try and report back
Didn't help still got no service tried flashing fast boot image too manually still no service.
vicelord97 said:
By full wipe u mean clean flash or including internal storage?
And thanks will try and report back
Click to expand...
Click to collapse
vicelord97 said:
Didn't help still got no service tried flashing fast boot image too manually still no service.
Click to expand...
Click to collapse
Are you flashing fastboot images correctly? Full wipe = wiping system, cache, dalvik cache and data in TWRP

Unable to boot up

I have the XT1550 variant on stock 6.0.1 ROM and Fire Kernel, rooted and xposed is installed and I have changed the boot animation. It's been months since I have rooted, xposed was installed 2 weeks ago and Fire Kernel a week ago (able to reboot before flashing kernel). Today there was an update to an xposed module I had installed so I rebooted to enable it, but now the phone won't boot up. The Moto logo shows but then the screen turns off and the phone doesn't boot up. I tried restoring the stock kernel(didn't work), then tried factory resetting through TWRP (didn't work). What should I do? Should I reflash the stock firmware? When I tried to, the command "fastboot flash partition gpt.bin" returned the error - "cannot load gpt.bin". So, I didnt flash the firmware and directly skipped to the step - "fastboot oem fb_mode_clear" and now am trying to restore to an older backup from TWRP. Is this the right way? Please help!
Thanks in advance!
Tron_Legacy1680 said:
I have the XT1550 variant on stock 6.0.1 ROM and Fire Kernel, rooted and xposed is installed and I have changed the boot animation. It's been months since I have rooted, xposed was installed 2 weeks ago and Fire Kernel a week ago (able to reboot before flashing kernel). Today there was an update to an xposed module I had installed so I rebooted to enable it, but now the phone won't boot up. The Moto logo shows but then the screen turns off and the phone doesn't boot up. I tried restoring the stock kernel(didn't work), then tried factory resetting through TWRP (didn't work). What should I do? Should I reflash the stock firmware? When I tried to, the command "fastboot flash partition gpt.bin" returned the error - "cannot load gpt.bin". So, I didnt flash the firmware and directly skipped to the step - "fastboot oem fb_mode_clear" and now am trying to restore to an older backup from TWRP. Is this the right way? Please help!
Thanks in advance!
Click to expand...
Click to collapse
Your flashing error is in regard to fastboot.exe not being able to find gpt.bin, it has nothing to do with the phone...
Restoring a working TWRP backup is the correct solution. If you want to go back to stock, that is a different thing entirely and should only be a last resort.
[RANT]This is why I am absolutely opposed to Xposed, and even rooting, on modern stock devices... either leave it pure stock or flash a custom ROM, quit trying to f*ck with stock because it often ends badly. Xposed is nothing but problems, always has been and always will be, even if they figure out how to make it work in Nougat and later (which is questionable at best) it is one of the most dangerous things you can to do your device especially if you don't how to handles things like what happened to you, because they will happen. Rooting breaks OTAs and several features... If you want root, or to change your battery indicator, or whatever you use to customize your installation, use a custom ROM without Xposed (it NEVER belongs on a custom ROM). If you absolutely insist on rooting stock and using Xposed, backup, backup, and backup again, at every step in the process, and keep a backup off the device to and know how to get it back to working condition, because it will break, maybe not today or tomorrow, but someday.[/RANT]
And BTW, this is NOT pointed directly at the OP, it is more general than that, so I mean no offense. I also have the utmost respect for the developers and the work they do on these projects, it is a huge undertaking and they have made great strides for the Android community.
OK, I tried to restore an earlier backup from twrp but when it tried to restore the data partition there was an error, probably because when I tried to flash stock firmware, you have to factory reset from stock recovery, which probably deleted the data partition. So, I still tried to boot it and it booted up and I had to set up the device again. But not there are other problems, one of them being, apps can't write to SD card. For example ES File Explorer has a dialogue where you have to select the root of the SD card to allow writing to it. When I select it, the task that is running is stuck. And a lot of play services problems. Should I try and reboot to see if those are fixed?
BTW thank you a lot for replying and helping me!
Probably you've messed it up. Maybe another factory reset from settings would help.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Probably you've messed it up. Maybe another factory reset from settings would help.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I can try that. I was thinking that instead of flashing stock firmware again, could I just flash CM 7.1 as I was going to do it anyway. Will that cause any problems?
Thanks!
Tron_Legacy1680 said:
I can try that. I was thinking that instead of flashing stock firmware again, could I just flash CM 7.1 as I was going to do it anyway. Will that cause any problems?
Thanks!
Click to expand...
Click to collapse
It shouldn't be any problem. You can go ahead and install any custom rom [emoji106]
Broadcasted from Zeta Reticuli
Gravemind2015 said:
It shouldn't be any problem. You can go ahead and install any custom rom [emoji106]
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I'm going to do that then! Thanks a lot for helping!

XT1033 no signal after flashing back to Marshmallow from Nougat, how can i fix?

Hello,
Since i bought the phone when it was first out i have been flashing roms, factory images, etc. So i know how to search, what to search, usually but right now i am stuck!
5 days ago, i was using a cm 14 rom, both sim slots were working, but phone was slow so i tried to install idcrisis 14a which worked, then yesterday a new one appeared, i clean flashed it, now i have no signal on either of the sim slots. Second slot recognizes that there is a sim, but gets no signal. when i do *#06# i can see both imei.
I have tried following:
flash kernel(s)
flash radio
flash modems
flash factory image
turn the device to gpe
flash cm14 zip
i still can't get service, do you have any idea what can be the cause and how to solve this?
please TRY this:
reboot to recovery
wipe data, dalvick, cache, system
install this zip drive.google.com/file/d/0B_TBSNgzL5M2clhTWG1SLV9yR1U/view
now try if you can get signal
now, if you want, you can upgrade to cm12.1/13/14.1
thank you, i will try this when i am back home.
thanks for your help but it didn't work either.
still haven't found an answer, any help would be great.

TWRP says no OS is installed, but I just flashed it. Can anybody help?

Hi,
Its been a while since I been attentive to my Pixel. I was a lucky one who managed to get a Verizon 7.1.2 with an unlocked bootloader. I unlocked the bootloader, flashed a ROM, and rooted and haven't had a single major problem since.
I was running Resurrection Remix from about March and I yesterday I wanted to try to use Android Pay, so I followed a tutorial I found in another thread here to install Magisk, and when it was all said and done I ended up in a boot loop where the phone would reset as soon as it reaches the Google logo, ramdump, and eventually boot back into TWRP.
In the attempts to delete out all kinds of caches and dalviks and factory resets and whatever else, nothing worked.
So in the end I decided to just flash a new ROM. Flashed the latest Pure Nexus, reflashed TWRP, flashed the vendor image... went to go reboot and it gives me the WARNING! NO OS INSTALLED! error. I thought that was odd and decided to just update to the latest Resurrection Remix - same problem.
At this point I am unsure what to do next. I don't care about any user data on the phone, I just want to get it back up and running with a new ROM.
I have a few questions and thank you in advance for all help you may be able to offer:
1) Why am I getting the NO OS INSTALLED issue directly after flashing a ROM? Logs indicate no errors whatsoever. /system/ is mounted. Every time I boot into TWRP it asks me if I want to Keep System partition read only. I always tell it to allow modifications and never ask me this question again - it asks every time. Is it possible that /system/ can actually remain empty even after a fresh ROM install that gives no errors in the log?
2) I believe that I am supposed to reflash to stock image that this phone shipped with to start all over. If I reflash back to stock, will my bootloader have any chance of locking again? I don't even know what version the stock image was, and I'm further confused/concerned about the fact that it was a 7.1.2 image I shipped with - from my understanding there were security updates which make unlocking/rooting impossible. I don't understand why you have to start that far back - is it even needed? The latest Resurrection Remix ROM install instructions assumes that I am on latest "Firmware" NOF26W. This is another issue I don't understand - what is a firmware? The full factory image? In any case, NOF26W is specifically for Rogers Google Pixel devices. Since I need to be on this "firmware" before I install latest, can I just flash the NOF26W Stock image despite the fact that I am using a rooted Verizon Pixel? The NOF26W image is 1.8GB: What exactly in this ZIP am I supposed to flash?
3) There were various weird things about this phone/flashing ROMs that I seem to recall such as having to boot an older TWRP before flashing ROM and then flashing the newer TWRP - is any of this stuff still relevant?
4) I also remember that many people were fastbooting TWRP rather than flashing TWRP for some reason - are there specific builds/non-standard stuff required for any of this to work on the Pixel?
I really appreciate all and any help that anybody can provide. If there's files that you're referring to, PLEASE send links. I need to get this phone back up and running ASAP.
Thanks again!!
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
rohitece06 said:
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
Click to expand...
Click to collapse
This. I just reboot anyway after seeing that message and I've never had any issues.

Samsung Galaxy J320FN - update fail/loop

Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?​
bregaryevich said:
Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?​
Click to expand...
Click to collapse
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Click to expand...
Click to collapse
Hey, thanks for the quick response.
I tried what you recommended but the problem still persists. After flashing the current version, the phone did the exact same thing and started looping.
Also tried TWRP but there's an FRP lock, preventing me from flashing it.
Now that the stock rom flash thing failed, guess there's only TWRP left. I did FRP unlocks before, but not on phones that are soft bricked. Is there anyway around it except wiping all data?
I may have forgot to mention, that the phone indeed has a passcode. And god knows what did the owner install/do with the device, that made ot to seize up.

Categories

Resources