Develop Bugs

Is there a way to avoid N7 hard brick?

Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...

carpamagica said:
Just bought a N7 2013 and I'm afraid it bricks after update and wanted to know if I could avoid it by flashing Marshmallow factory image instead of updating via OTA, skipping lollipop, or if there is any precaution to not brick it...
Click to expand...
Click to collapse
why would it brick via OTA? almost all N7s are updated that way.
the best precaution for not bricking it is if you follow the instructions that are given for manually flashing factory image, although I don't think it is necessary to do it manually. I did it OTA and it works perfectly normal.

Hard Brick
FWIW,
I've used Ubuntu with the adb utility and if I "bricked" my N7 2013, I found when I got to the bootloader "START"
window, I could simply do the sudo ./Install-all.sh command that comes in the package for the "stock" Android
kernel without any prerequisite commands and the ROM would load.
Of course anything that was on there previously was wiped out but at least I had a new system to start from.
I discovered this when I had my "bricked" device at the START window and the "adb devices" command showed that the N7 2013 was recognized at the USB port. Just went ahead and did the Install-all.sh command and away it went.
I tried to get Android 6 installed, rooted and with MultiROM operating but no dice. When I got to the point of installing MultiROM on Marshmallow, the device would perpetually boot into TWRP, never booting Marshmallow. I ditched it and went back to KitKat 4.4.4 and got it settled and then loaded a Cyanogenmod
snapshot. I'm liking CM more and more.
I'm just a script kiddie that's dinked with Linux since '93 and am by no means an expert. The background has helped when slogging away with my N7 2103 Flo. Kurt

reso91 said:
why would it brick via OTA? almost all N7s are updated that way.
Click to expand...
Click to collapse
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)

carpamagica said:
Huh... back when Lollipop was released I heard a lot of N7s hard bricked because of the update(5.0.2), causing a motherboard problem, idk, but no one could flash anything, and I thought I could avoid this problem with lollipop skipping it (ex: N7 come with JB and I flash Marshmallow factory image instead of going through KK,LP till MM)
Click to expand...
Click to collapse
Sigh. The issue was widely reported as being caused or exacerbated by the OTA update to the initial release of lollipop. The best way to avoid the issue, if there ever truly was one, is to simply use custom ROMs, or stock rooted ROMs, which can be installed via custom recovery as opposed to through installing the factory image...

One of the nice things about Nexus devices is that Google posts factory images on their site. I generally prefer to use those, rather than OTA updates, as it guarantees a fresh install. I use a variety of other methods to backup/restore data and apps, but I've had pretty good luck doing it that way.

There's a really simple way to not hard brick your N7 with an OTA update:
If your present Android version is working okay, is stable, and does what you want it to do...wait for it...LEAVE IT ALONE!
Seriously. Other than for additional stability and MAYBE security enhancements, stick with what you have. Don't fall for all the hype out there.

The bricking caused by lollipop was due to a bug in the update causing a excessive amount of read/writes to the NAND and caused premature failure of the chip, this has long since been fixed and lollipop is safe for use again.
Sent from my Nexus 7 2013 using Tapatalk

Hardware/software Diagnosis.

Hello all,
I just bought a Note 4 as a replacement for my busted Note 3 and the one I purchased had a improperly flashed firmware, so I thought i'd take a gamble and try to restore it.
I was able to re-flash to OG5 then use the OTA update to 6.0. Then the phone would reboot randomly have severe battery drain, become very laggy, and lock the device to the point where I had to pull the battery and let it sit for a few moments to be able to boot it up again.
Then I decided I'd try a custom ROM and flashed the Resurrection Remix rom and per the instructions flashed to OG5 first, I also cleared the partitions and dalvik, prior to ROM install. Problems still persist.
I have read that the eMMC memory can fail leading to read errors, and a failing battery can fail leading to some of these symptoms but i'm not sure what to do now. I have ordered a ANKER replacement battery just to be on the safe side and I ran a app to test the eMMC and it passed but i'm not sure on the effectiveness of the app. Any advice would be appreciated. Thanks

Pixel XL - HUGE data usage NOT rooted

Hey all,
I've done heaps of searching here and the wider web but only found reference to rooted phones failing to take updates.
I can't get a screenshot on here right now as I'm at work so no wifibut:
- Android OS _______________3.04GB :silly:
- Chrome__________________434MB
- Google Services ___________24.13MB
- etc
When I read about the failed update I checked in there and sure enough I have a 2017-5 patches system update sitting there failed, when I retry it it will download successfully then do step 1/2 of the installation then fail.
So it seems this would be the problem but the phone is definitely NOT rooted, any ideas??
thanks

You speak in codes, man. Could you explain your issue simpler? Right now I see an Android OS usage of 3.04GB. That seems abnormally large times 10. No one should have that, really. So it seems like your Android OS process downloaded multiple copies of system updates in error. Is that your problem?
Your post is still largely incomprehensible, so I won't make a final conclusion.
These are just suggestions:
1) If your phone is downloading system updates over and over, just damn update so it stops, or factory reset your phone.
2) If this is some kind of a rogue app, you are literally funked. Good luck trouble shooting it.
In any case, GL!

Yes, android OS used 3.04GB in ~5 days, my best guess is it was due to repeated attempts at '2017-5 patches system update'
Sorry, when I did a search I got heap of references to rooted phones having this issue so I guess I just talked from that reference point? It seemed to be a known issue but for rooted phones.
I just wanted to be clear that my issue matched those symptoms but was not rooted.
1) I've tried a manual update (many times) fails at the same point, I assume this is what is causing the data usage, as mentioned above.
2) Pretty sure it's not a rogue app
I'll try a factory reset, it's only a couple of weeks old (warranty replacement) so I hadn't really thought to reset straight away.

The phone doesn't necessarily need to be rooted to fail the update. A previously rooted phone can also fail to update as described, but typically that would mean an unlocked bootloader. I would have figured that the phone would have been reimaged and the bootloader locked on a refurbished phone, but maybe that doesn't happen. Is the bootloader unlocked? If so you could image the phone yourself to see if that works to fix it. If the bootloader is locked and a reset doesn't work, then I figure you might need to contact support about getting a different phone.
https://developers.google.com/android/images

I think you've gotten good information from everyone so far but just to add some clarity.
I had this exact same issue and was not rooted but did have an unlocked bootloader.
A factory reset did not resolve it. At the time I had issues, there were questions about rooting the stock images so I flashed PureNexus and have never looked back or had the issue again. Also, Verizon did add data to my plan and credit my account for the additional charges to negate the cost. Hope this helps!

It sounds like an issue with your phone that Pixel support might be able to help you with but they will certainly suggest a factory reset so you should do that first. Since you have a refurbished phone you don't know how the previous owner was using it and its possible a modification he made is still on the phone and causing you problems. If the failed system update isn't actually causing the excess data usage it could also be a carrier issue. I know some Project Fi users had that problem and it was related to the service. Google gave people credit for the excess data. You could also have an app that is interfering with the update so a factory reset should definitely be your first step and I'm guessing it's fairly likely to fix your problem.

Slow Phone and Options?

Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!

Have you tried looking through the various posts within the forum to find your answer? I just scrolled through and found a few without searching. Exerting a bit of effort could yield amazing results, at least that's what I've had happen over my years on here

bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
My Verizon Note 4 is exactly at the same update level as yours and it is working great.
When you did the factory reset did you completely wipe all user data on both the phone and the SD card? If not I would give that a try.
I would also suggest that you not let Android restore any applications when you first start the phone after the factory reset. You could have an errant app causing problems. If it seems to work phone without any user installed apps I would then reinstall apps one by one and make sure the phone continues to work fine. It it starts to run incredibly slow again then the last app you installed is likely the culprit.
If these options don't work I would take the phone to a local Best Buy. Go to the Samsung Experience counter and talk to them. They can do a deep factory reset that will completely reinstall the firmware and thereby restore the phone to a pristine factory image.
If these options do not fix the problem you may be in the early stages of hardware failure. The Note 4 has developed a bad reputation for the motherboard slowly failing and causing progressively worse problems. That is what happened to me and the phone eventually became unusable. I finally had to contact Samsung technical support (1-800-SAMSUNG) and they had me send the phone in. They replaced the motherboard and other printed circuit boards. It did cost me $70 since the phone was out of warranty, but it works like new now.
Good luck. The Note 4 is still a great phone and worth the effort (and possibly cost) to get it fixed.

Can anyone confirm that Foxfi tethering works (not usb) on a non rooted Verizon Note 4 phone (marshmallows 6.0.1) with the following security update installed (mmb29m.n910vvrs2cqe1)

bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
Yeah im thinking the problem is this phone came just packed with bloatware nobody uses a third of the garbage that came preloaded (200+ apps you use 10 of). You can root but you have to downgrade with odin back 5.1.1. bpa1 . you could also try a less invasive approach and just disable the bejeezus out of pretty much anything allowable there is an easy disable option that lets you do it in batches from the apps drawer. I did this to root the phone given the unstable root method.

Flashed TWRP to both A and B

So i followed the instructions to flash TWRP. this is the first time i have used a phone with the A and B type boot and when it was supposed to reboot to TWRP after flashing TWRP to A (my default boot.img was B) it instead loaded the OS. Confused i tried the process again and was relived to boot into TWRP. However i then discovered that TWRP had been flashed to both A and B. I am on the Three UK Razer phone and i can only access TWRP. I did a backup but I think it either didn't work or was wiped while i was trying to fix the issue. I would appreciate any suggestions or help anyone can offer. Thanks in advance.

Same here
And used also the backup files that was uploaded by one of members in here but so far not work
I purchased mine from amazon us
Anyway to fix our phones
Please

hi there, i got the same problem i flashed twrp exactly like you , i can only boot in twrp not in os . with boot.img from another guys here i managed get the bootanimation with the green circle but i can't boot or past that screen. i leave it for 4 hours ,drains the battery and shut itself off. after i read somewhere on this forum that if the boot partition(kernel) is matched with your system and won't boot in another phone ,i got the backup tried to restore none work. my phone is dead on the drawer , meanwhile i bought oneplus 5t sandstone white 128GB and i got like 12 roms on the Data partition and i don't know witch one to flash , so the difference for support for this two device is major . i will never buy a non popular phone
i will wait for them to release the factory image, (at the end of this year) i will flash it and i will sell it with 300 pounds less because razer
Just for you to know , they just released the robin phone factory image after that phone is obsolete
i also got a ****y phone from china witch is AndroidOne (xiaomi mi a1) witch meens is nexus /pixel like witch i got android 8.1 and in two weeks i got 4 updates streight from google .i was just amaze what support got this cheap phone . the point is next time when you buy a phone check if is popular on XDA forum

The razer phone got good spics and potential
But I wonder why it's unlike op5t in terms of support.
Let's skip the factory part but my main point on the developers in here , why we can't find help in here and support.

The reason there is fewer developers on this phone is cause there aren't factory images yet. Developers don't want to get there phone in a state that can't be reset and right now, that's razer phone. Razer has said that they are coming but I suspect like others, they haven't released them yet cause they are trying to get everything tweaked right before they release them. There really is no point having images for a phone that reintroduces issues they have already fixed with updates. I don't expect it will be much longer though.
OP and the like already have an established following that's why there are so many options. Also remember the 5t is still based on the 5 which already had a development community. Razer on the other hand is a new company and this is there first go at it. Once we see images released alot more developers will be more willing to jump on board. You see this with almost all new phone manufacturers.. You don't think htc and the like had developers lined up out the gate do you?
This phone wasnt released as a developer phone like the nexus line was. Razer has been quite good so far in terms of software updates and being in touch with the community as a whole.

I totally agree with you , my main point is to find solve for our corrupted phones and not only me having that issue.