Develop Bugs

6.0.1 Update after replacing motherboard

My beloved N7 2013 fell victim to the eMMC-nuking 5.0 (unsure about exact version) OTA update last year. I put off replacing the motherboard, as I had already bought a new tablet. Lately, though, my N7 itch returned. I was able to successfully replace the motherboard, but the replacement I purchased was also Kingston...much to my chagrin.
Anyways, I updated the new motherboard to 4.4.4 via OTA, and forewent the next OTA (5.0 OTA update). Things are smooth, and my tablet has been resurrected.
My question, then, is two-fold. First, is the 6.0.1 stock update worth the hassle of running a clean install? And second, will I run into the same problem that killed my N7 the first time (update nukes eMMC)?
I tried to find a thread where this has been discussed, but I must not fully understand searching for things on this site. Thanks for your help!

Amazing how you'd consider throwing good money after bad. If you insist on everything stock, you assume the risk, random though it might be with MM. There are plenty of custom roms that mirror stock almost totally, why the insistence? What's so sacred about it?

hekat0n said:
My beloved N7 2013 fell victim to the eMMC-nuking 5.x OTA. I was able to successfully replace the motherboard. I updated to 4.4.4 via OTA, and forewent the next OTA (5.0 OTA update). Is the 6.0.1 stock update worth running a clean install? Will I run into the same problem that killed my N7 before? I tried to find a thread where this has been discussed, but I must not fully understand searching for things on this site. Thanks for your help!
Click to expand...
Click to collapse
There was a known write loop error in one of the 5.x OTA updates that baked boards, but the Kingston boards are generally known to be unreliable among the three common boards for razor. Long story short, you have nothing to lose by updating to the latest OTA, 6.x adds nice features, runs well, and has the latest security updates and compatibility with the latest popular apps. Bricks on 6.x OTAs seem random, and are most likely related to instances of hardware failure on individual devices that developed over long periods of device use, than from a single software update causing or contributing to a hardware failure.
The users here have been contributing to a thread regarding this issue, it can be found here.
It's worth mentioning that instances of eMMc failure on devices running custom ROMs are far fewer in number than instances of bricks on stock devices.

Nokia XL 4G Backup and Root again

Hello!
I have a Nokia XL 4G with root, but it's 1.1.4 Stock Rom Version.
I'd like to update it at latest version, as I can check online, for this phone there is Nokia X Platform 1.2.5.. but actually I can't update my actual rom, so I thoght to proceed this way:
-Backup actual rom, so in case I find problems after the update, I can get back to root version.
-Flash newer OS version.
-Proceed with root of new version.
But actually I find problems with backup: neither cwm either twrp found on xda's tutorials seem to work on my phone.. I think it's probably because my phone is different.
So for first I want to know if there is some way to do the whole actual rom backup without a recovery mode..

DainoManthis said:
Hello!
I have a Nokia XL 4G with root, but it's 1.1.4 Stock Rom Version.
I'd like to update it at latest version, as I can check online, for this phone there is Nokia X Platform 1.2.5.. but actually I can't update my actual rom, so I thoght to proceed this way:
-Backup actual rom, so in case I find problems after the update, I can get back to root version.
-Flash newer OS version.
-Proceed with root of new version.
But actually I find problems with backup: neither cwm either twrp found on xda's tutorials seem to work on my phone.. I think it's probably because my phone is different.
So for first I want to know if there is some way to do the whole actual rom backup without a recovery mode..
Click to expand...
Click to collapse
If you want an update, try Nokia X Flasher and download the latest firmware for your device....:good::good:

http://m.romzj.com/list/nokia_xl4g.htm good luck

Veez21: Nokia X Flasher doesn't work.. I tryed Nokia X Manager too, it gives me some error like "length can't be less than zero"...
thinhx2: the site you send me is not comprensible, I don't need the rom, I need a way to backup my actual rom that is yet rooted, so if I find troubles after update I can get back to a rooted rom.

DainoManthis said:
Veez21: Nokia X Flasher doesn't work.. I tryed Nokia X Manager too, it gives me some error like "length can't be less than zero"...
thinhx2: the site you send me is not comprensible, I don't need the rom, I need a way to backup my actual rom that is yet rooted, so if I find troubles after update I can get back to a rooted rom.
Click to expand...
Click to collapse
Explain why custom recoveries can't help you
Sent by a Cool Guy using XDA-Developers mobile app

I didn't say Custom Recoveries can't help me, sorry.. I said that when I tried to install both ClockworkMod and TWRP but they can't be installed on my phone!
I followed the step to install those, it acts like they are installed but when I try to start the phone in recovery mode it locks on the Nokia logo screen and never get in recovery.
Is it possible that those don't work because my phone is Nokia XL 4G (it has 4cores cpu and 1gb ram) and so it's different by other normal Nokia X/XL?
What can I do to install recoveries? Or is there any other way to backup the whole phone without them?

Someone can help me?

Nokia xl 4g very different nokia xl

None of existing Nokia X/XL tools will work with XL 4G model, because it's totally different hardware (even used Qualcomm SoC is different); without recovery with available root shell it's rather impossible to make proper backup of system partitions.
Wish somebody outside China have access to XL 4G, maybe somebody would be able to port TWRP/CWM.

BluRaf said:
None of existing Nokia X/XL tools will work with XL 4G model, because it's totally different hardware (even used Qualcomm SoC is different); without recovery with available root shell it's rather impossible to make proper backup of system partitions.
Wish somebody outside China have access to XL 4G, maybe somebody would be able to port TWRP/CWM.
Click to expand...
Click to collapse
Can port rom but dont update version of android

Just got a new Nexus 5x

Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.

To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.

mikeprius said:
Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.
Click to expand...
Click to collapse
More signs point to hardware failure rather than the update. I think it was just coincidence that 7.0 came out when phones were getting close to 1 year old. I've been running my replacement from last month on 7.1 beta and it's just fine.
Sent from my Nexus 5X using Tapatalk

Ezekial said:
To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.
Click to expand...
Click to collapse
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat

mikeprius said:
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat
Click to expand...
Click to collapse
Gotcha. I have only had my 5x for just over a month so not the most knowledgeable. My take is largely the same as the other guy, failures are from hardware or just bloat from long term use.
I start with the latest 6 and considered staying on it for root, xPosed, etc. I have always ran this way for years. But it is super annoying not having Android pay and a few other things. I sucked it up and decided to try not rooting or even unlocking BL. There are things I miss but I am staying locked down for now. The primary issue I have is for tethering, which I cannot do. The rest I have surprisingly been able to do without.

Flash away
Hey mate, you will not have issues flashing what ever you like, issues are caused by hardware failures ( unavoidable ) or just not following instructions correctly. I flash factory images, beta etc, and custom ROMs. Never have issues. Flash like crazy. It's just a phone and almost all of them can be fixed, if something goes wrong.
P.s. You gotta try the 7.1.1 beta. Its has potential.

downgrade 8.0 to 6.0 a520

hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!

nubry said:
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
Click to expand...
Click to collapse
I don't think it will work because Samsung has anti rollback in its phones which prevents the bootloader from being downgraded. However, a system and boot flash might work. I don't know about the modem though.
Samsung is one of the few brands that implement it.
I don't really see the use though as it is quite possible to bootloop and if done incorrectly, could result in a hard brick.

nubry said:
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
Click to expand...
Click to collapse
Quick question...
Why would you want to?
I did this with my old Moto X Play and bricked it

iloveoreos said:
I don't think it will work because Samsung has anti rollback in its phones which prevents the bootloader from being downgraded. However, a system and boot flash might work. I don't know about the modem though.
Samsung is one of the few brands that implement it.
I don't really see the use though as it is quite possible to bootloop and if done incorrectly, could result in a hard brick.
Click to expand...
Click to collapse
that is what I thought... I think the only real solution would be to find a custom Rom of the Stock 6.0 but untouched. It would not need the bootloader to be downgraded would it?
I really like samsung phones but I hate the way the treat costumers, it feels like being fooled.
Thank you for your reply though !

moozer said:
Quick question...
Why would you want to?
I did this with my old Moto X Play and bricked it
Click to expand...
Click to collapse
When I bought my Moto g 2015 it was very fast and that was surprising. All the updates started to drain the battery and make the device work slower . I tried almost all the custom Rom possible and after flashing back the stock 5.1 out of the box version I have to admit they wanted the device to become slow with all the updates.
Now when I received my A5 it was already running nougat. I think the best you can get from your phone is with the outbox version because everything is planned to be running perfectly so people buy it. For me even though it brings new features and stuff, update wont get you device any better.
So ya that's the reason I'd like to downgrade.

nubry said:
that is what I thought... I think the only real solution would be to find a custom Rom of the Stock 6.0 but untouched. It would not need the bootloader to be downgraded would it?
I really like samsung phones but I hate the way the treat costumers, it feels like being fooled.
Thank you for your reply though !
Click to expand...
Click to collapse
You could extract the system and boot out of the stock firmware, but I don't know if it's worth the risk.

nubry said:
When I bought my Moto g 2015 it was very fast and that was surprising. All the updates started to drain the battery and make the device work slower . I tried almost all the custom Rom possible and after flashing back the stock 5.1 out of the box version I have to admit they wanted the device to become slow with all the updates.
Now when I received my A5 it was already running nougat. I think the best you can get from your phone is with the outbox version because everything is planned to be running perfectly so people buy it. For me even though it brings new features and stuff, update wont get you device any better.
So ya that's the reason I'd like to downgrade.
Click to expand...
Click to collapse
Motorola got in trouble for that. Others too. It's illegal now, so you should leave out that theory.
I've had only positive experiences with my last 5 smartphones. Upgrading does precisely that...makes it better. An OEM would not produce an upgrade without testing it. That's why we had a better experience with Nougat and even better with Oreo.
What do you do differently with Oreo than you did with Nougat?

H8324 Rooted Android 9, how to update to latest Android 10 rooted version ?

Hello,
I currently have a XZ2 compact H8324 rooted
Build number : 52.0.A.3.126
I rooted it some years ago and to be honest I don't remember well what I used to do it. I just remember DRM are safe.
The bootloader is unlocked if I remember well (warning message at boot)
Could someone please tell me how to update to latest Android version still rooted ?
I don't care about format it, but I would like it to work as usual (camera stuff) with root.
Is there some kind of precautions ? tools ?
Thank you.
Edit : downloading 52.1.A..3.49 with XperiFirm currently

Xperifirm might work. You can also try Emma (Sony's official flashing tool) which is easier to use but will wipe your device and uninstall any custom recovery you have installed. Your bootloader will remain ulocked, and your DRM keys intact, so you can always reinstall custom recovery after that.
You can also install LineageOS. They have an official 17.1 (Android 10) build for the XZ2 Compact, so it should be very stable and have minimal issues. I'd recommend installing LineageOS after flashing the latest firmware with Xperifirm/Emma because the stock ROM doesn't play nice if you have root or TWRP installed.

Thanks @dankcuddlybear for your answer.
I don't care about custom recovery and data as long as I'm able to flash back custom recovery and root after flash.

If your current Pie variant is fast, stable and is fulfilling its mission, be happy and leave it be.
Q is using cpu cycle wasting scope storage and is a downgrade in many ways from Pie.
Being rooted means you could (?) overcome many of these limitations but how much is your time worth?
Android 10,11(Apple) woke, go broke

blackhawk said:
If your current Pie variant is fast, stable and is fulfilling its mission, be happy and leave it be.
Q is using cpu cycle wasting scope storage and is a downgrade in many ways from Pie.
Being rooted means you could (?) overcome many of these limitations but how much is your time worth?
Android 10,11(Apple) woke, go broke
Click to expand...
Click to collapse
It is not... screen hangs for no reason and needs to switch it off and on
And last week i had to force hardware button reboot as it was stuck

Orphee said:
It is not... screen hangs for no reason and needs to switch it off and on
And last week i had to force hardware button reboot as it was stuck
Click to expand...
Click to collapse
Not good. Pie should be rock solid stable.
It sounds like it's fixing to crash and burn.
Look at the launcher and other 3rd party apps you're using. That load maybe corrupted or the original firmware was flawed.