Develop Bugs

Bootloop on Rooted Pure Nexus ROM

*Irrelevant thread*

@Omnitrix4m3
Call Project Fi. Talk to them. They'll probably send a replacement (no waiting for repair). You can always talk to them and then after hearing what they say decide no.

Omnitrix4m3 said:
Wow. I spend so much time on Reddit ignoring these threads until today.
Allow me to set the scene, I'm a student who loves to tinker and modify, and the idea of unlocking my bootloader, rooting, and running custom ROMs on my device seemed fascinating at first. Becoming an avid user of this after fashing my device countless times and performing backups, I began to find a system thatworked for my device and was stable. Having not flashed anything for months on my phone, I had no reason to take a backup of my phone. Until today.
Realizing I had too many garbage apps on my phone, too much RAM being used, and my SOT being garbage, I decided on deleting some of the 222 apps I keep for fun on my phone. With that, I used my phone's built in free space client which cleared unused apps and saved photos. However, it also included my downloads folder where I consciously chose my downloaded ROM and vendor images to save space (Remember, my build was stable at the time and I wanted space to do an eventual nandroid backup). After deleting those flashable files I continued about my day as usual. However, until the end of the day I realized my phone was logged out of my school's wifi, so I logged back in. My phone then began to lag, and a combination of the phone and me using the powerbutton allowed it to reboot. Then it began to bootloop. Normally as a flasher bootloops are easy to get rid of, or may ensue for minutes after flashing a file, however this was consistent and I had no ROM to flash over it, muchless boot to TWRP to do it. I couldn't boot to anything but the system's own recovery mode. I gave the phone some time alone and tried to research how to fix the problem without opening the phone up and soldering. When I attempted again to boot the phone I realized I got boot into TWRP. However, that was shortlived as, when I tried to make a backup the phone froze and rebooted. Going home with my head in my hands, I later tried booting an hour and a half later making my whole boot animation until the very end when the name is shown and the lock screen should load, that's when it began to loop again. I spoke to my father who bought the phone through Project Fi, who recommended me to talk to support. However I just realized: A) If I send it, I lose my data or have it tampered with in a repair. B) If they attempt to boot it, they will see its void of warranty due to the bootloader unlock and rooting and might not honor my warranty (although people have done it after warranty, NOT BECAUSE IT WAS DEVOID BY UNLOCKING BOOTLOADER/ROOTING). C) I bought it on sale for like $250 for 32 GB so money I get back won't cover a Pixel or another phone I can tinker with again with AOSP roms (and I'm not trying to wait two years for Android O, the only other phone I would consider is a OnePlus 5 which launches in the summer and would be around $450).
What would you guys suggest I do?
1. DIY solder and fix
2. Continue tampering to find way to copy off data (I need suggestions)
3. Send it back completely wiped or in way it is to fix
4. Have it replaced with money (and then what phone would I buy?)
And finally do I go to Google Store, Project Fi, or LG to have this issue resolved while ommitting the fact it has been modified?
P.S.: While writing this, this actually booted up for 5 minutes and worked until it crashed and entered the loop again.
Click to expand...
Click to collapse
If you can get into recovery again, do a factory reset and see if it'll boot. If so, take the opportunity to back up your files then flash the factory images to go back to stock so you can get a replacement. Good luck

Phone soft bricked

So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.

Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
First of all, roms from other phones are not compatible with phones other than what it was designed for. If you tried others, that's why it won't boot up. Secondly, if you read all the posting about how do install twrp, it also said there wasn't any way back EXCEPT for your backups. Unfortunately there is no factory images for the Razer phone released as of yet. If you are unable to restore from your backup (or skipped the step and didn't create one) your only choice is to attempt to restore via the backups Xshooter726 made and posted, and if they don't work, you need to wait till the factory images are released and we don't know when they will be out other then a vague "soon" from a community manager on their forums.

Boltrag said:
So I recently had the great idea to root my razer phone after a friend talked me into it, I get the root on but I can't get wifi to turn on, I spend a few hours trying a bunch of different methods to get it working but none of them work. I read magisk can cause an issue, so I delete that and someone says wipe the cache as well in twrp so I do that, switch my slot from b to a and the thing boots straight back to twrp after sitting on the first boot logo for a good 10 minutes. Try the other slot same issue except it boots straight to twrp. So I try and use my backup I made, low and behold its corrupt, at this point I go straight to ****.exe. I try literally everything I can think of and I can't get this thing to take a custom rom, not even a nexbit rom, or a one plus 5t rom. Anyone have any ideas? I've contacted razer and I asked them if there was some way they can fix this without me buying a new phone.
Click to expand...
Click to collapse
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.

Roxas598 said:
If you're flashing roms for other Devices but now much experience do you have with flashing etc? Ignoring that fact unless backups from other devices work then youve no choice but to wait for razer to put up full factory images in January and flash those. Razer won't help you as you've voided your warranty.
Click to expand...
Click to collapse
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.

Boltrag said:
I had a decent bit, we only tried to flash another rom after we couldnt find the stock image, it was a last ditch effort.
Click to expand...
Click to collapse
Well you're lucky none worked it could have made your problem a lot worse. When factory images release you can flash those if the backup doesn't work but until then you're out of luck unfortunately.
Side note if razer ask for imie etc don't give them it. Might be able to list the device as have being unlocked etc.

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.

Bootlooping; flashing OTA update not helping, bootloader locked. Can ADB unlock it?

I converted my girlfriend (a long-term iPhone user) over to Android, and we got a shared plan with Google Fi. She installed the December OTA update, and today her Pixel XL began bootlooping.
She is running completely stock Android -- I haven't touched it in any way, and she doesn't know anything technical about the phone (so no funny business on her end). The phone was constantly bootlooping, sometimes with artifacts appearing on the screen (which looked like the "static" you'd see on a TV screen not set to any channel). These artifacts wouldn't happen every time, but about 25% of the time they'd appear.
I can boot into the bootloader with zero issues. Fastboot recognizes the device just fine. At first, I couldn't boot into recovery -- it would crash and start bootlooping before loading the recovery screen. Finally, though, I managed to get into recovery and did a standard factory data reset. No dice. I went into recovery again and flashed the OTA image via adb. This solved the "crashing before getting into recovery" issue, but not the general bootloop issue. I can't downgrade the OTA now, either.
My next option is to flash a factory image. However, as I mentioned, the phone is completely stock -- with a locked bootloader. I can't get into the device at all due to the constant bootloops. Is there ANY way to allow OEM unlocking through ADB/Fastboot? I'm running out of options here.
The good news is that Google Fi now supports iPhones, and she still has her old iPhone. I don't know if her Pixel XL is under warranty, though, so I don't know if they can RMA her a new one. Any help?

Update: She talked to Google Fi support (and by "she," I mean her calling me over to explain the technical stuff to the support rep), and they're going to RMA her a new one. Which sucks, but at least she has her iPhone until then. For anyone coming from the future, this thread matched my problem exactly, but ultimately I wasn't able to fix it. Even so, it might come in handy if this ever pops up on a Google search somehow.
Moral of the story: Leave your bootloader unlocked unless you absolutely need it locked. And even then, people were reporting that their phones got bricked.

march update

Just a quick heads up march up date has been released but the release notes only say that specific fixes are for the pixel 3 and pixel 3 XL. I don't know if there's anything for our OG XL.

ttocs99 said:
Just a quick heads up march up date has been released but the release notes only say that specific fixes are for the pixel 3 and pixel 3 XL. I don't know if there's anything for our OG XL.
Click to expand...
Click to collapse
I'm not certain, but people on reddit claim there won't be any new functional updates for our device :/
"OG Pixel will only receive security patches since Dec 2018. It's EOL for OS updates and functional updates."
Sent from my Pixel XL using XDA Labs

Velfess said:
I'm not certain, but people on reddit claim there won't be any new functional updates for our device :/
"OG Pixel will only receive security patches since Dec 2018. It's EOL for OS updates and functional updates."
Click to expand...
Click to collapse
I would of thought they would of looked in to the pie battery drain people are having but nevermind I'm still enjoying my experience with the OG XL and I'm still stock. I don't know whether to take the plunge and go custom ?

This is the support map for nexus and pixel phones (expand the sections) and yeah, Pixel probably won't get any new major update.
But, we still would receive security patches until october (theorically)

ttocs99 said:
I would of thought they would of looked in to the pie battery drain people are having but nevermind I'm still enjoying my experience with the OG XL and I'm still stock. I don't know whether to take the plunge and go custom ?
Click to expand...
Click to collapse
Well there's really no risk, it's not like something that takes a long time or that you can mess up. You could literally flash any custom ROM for this phone and completely screw everything up to the point where you couldn't use it. Then all you have to do is plug your phone into your computer and flash the latest factory image from Google and everything will be okay. Wiping your phone and flashing a custom rom takes less than 10 minutes and so does flashing the factory image back to the phone if you mess it up. So there's really no downside trying custom firmware on this phone. The only thing that you have to remember is never relock the bootloader. Once it's unlocked never ever ever lock it again. And even that is something that you have to manually do it's not like something you could do by accident.

Phalanx7621 said:
Well there's really no risk, it's not like something that takes a long time or that you can mess up. You could literally flash any custom ROM for this phone and completely screw everything up to the point where you couldn't use it. Then all you have to do is plug your phone into your computer and flash the latest factory image from Google and everything will be okay. Wiping your phone and flashing a custom rom takes less than 10 minutes and so does flashing the factory image back to the phone if you mess it up. So there's really no downside trying custom firmware on this phone. The only thing that you have to remember is never relock the bootloader. Once it's unlocked never ever ever lock it again. And even that is something that you have to manually do it's not like something you could do by accident.
Click to expand...
Click to collapse
I've flashed custom ROMs in the past to Samsung phones old Sony's HTC mtk devices and nexus range I just want a fully blacked out rom for the oled screen with out using substratum as that causes phones to slow down.

ttocs99 said:
I would of thought they would of looked in to the pie battery drain people are having but nevermind I'm still enjoying my experience with the OG XL and I'm still stock. I don't know whether to take the plunge and go custom
Click to expand...
Click to collapse
This! Accubattery reports 70 percent health and I can only barely squeeze 2.5 hours SOT on my phone. :/ This battery life is absolutely atrocious and nothing seems to point at battery drain aside from Android OS and Play Services.

snappycg1996 said:
This! Accubattery reports 70 percent health and I can only barely squeeze 2.5 hours SOT on my phone. :/ This battery life is absolutely atrocious and nothing seems to point at battery drain aside from Android OS and Play Services.
Click to expand...
Click to collapse
Ask the Google assistant for a battery health check it will tell you if it's in good health or not

Phalanx7621 said:
Well there's really no risk, it's not like something that takes a long time or that you can mess up. You could literally flash any custom ROM for this phone and completely screw everything up to the point where you couldn't use it. Then all you have to do is plug your phone into your computer and flash the latest factory image from Google and everything will be okay. Wiping your phone and flashing a custom rom takes less than 10 minutes and so does flashing the factory image back to the phone if you mess it up. So there's really no downside trying custom firmware on this phone. The only thing that you have to remember is never relock the bootloader. Once it's unlocked never ever ever lock it again. And even that is something that you have to manually do it's not like something you could do by accident.
Click to expand...
Click to collapse
Uh.. I'm new here, any side effect if the bootloader is relocked?

dic1911 said:
Uh.. I'm new here, any side effect if the bootloader is relocked?
Click to expand...
Click to collapse
Don't relock bootloader when unlocked unless you have flashed a 100% factory image but I'm going custom ROM soon just haven't got my laptop back from being repaired.and there should be no side effects if you know what you're doing.

dic1911 said:
Uh.. I'm new here, any side effect if the bootloader is relocked?
Click to expand...
Click to collapse
The majority of people who hard brick their devices here are ones that relock their bootloader's and then realize they hadn't wiped and flashed a stock factory image. So they can't use fastboot and end up not having a phone that will boot. There's no reason other than selling the phone you would ever need or want to lock your bootloader after unlocking it. It's just a bad idea all around.