Related
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Yeah im pretty sure your emmc is fried. So you have two options: buy a new phone or a new motherboard. You van check by locking the bootloader if its still unlocked upon reboot your emmc is fried..
Sent from my Galaxy Nexus using XDA Free mobile app
I runned "fastboot oem lock' from my command line, and I got the status "OK".
Then I pressed "restart bootloader" on my phone, but it still says "lock state - unlocked".
So I suppose, I should let it rest in piece, or change the motherboard?
I think a motherboard is more expensive than a new phone. If it is just let it die. If it isnt you can buy a new motherboard and swap it. But I dont think that is a smart move now. The moto g for example is a awesome phone for (i think) almost the price of a new mobo.
Sent from my Galaxy Nexus using XDA Free mobile app
same problem here
It makes me wonder, I'm having the exact same issue just a couple of days later. Is this the planned obsolescence thing?
withend said:
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Click to expand...
Click to collapse
Google's secret weapon to make us buy the new Nexus 6.
I don't know why that happens though - dual core processor, with this amount of RAM. Tech-specs-wise, GNex has nothing to be jealous about than mid-range smartphones right now.. Unless, the CPU architecture from 2012 is so bad that it can't run properly today's apps.
Hey guys, I have these problems too. Just bought the Galaxy Nexus from a friend for €15 (cracked screen) and from the moment I turn it on, (sometimes at Nexus logo, sometimes on lockscreen.. ) it reebot itself. Again and again.
Unlocked the bootloader by toolkit or manually by fastboot but after the reboot it's locked again, as you said. I've tried Odin too with same results. The strange thing it's that it took time to do things but after the reboot, it's like I haven't done anything. I mean, even if I delete an app, or wipe data from recovery (not custom), when it turns on, it's always the same.
It's like a challenge to me. Anyone can help? I can't just give up >.<
Inviato dal mio Nexus 4
What the hell, just finished answering another thread with same issue (forum.xda-developers.com/galaxy-nexus/help/wipe-flash-restarting-help-t2908788). Happened to me last week, very same, never touched the phone, always stock.
What the hell is going on here???
Is there any way to get any log files to determine what the hell is going on?
Mine opens up for a few minutes, maybe 3-4 and it seems to be working well.. It gradually gets unresponsive and ultimately restarts.. So, if there is anything to do during these 3-4 minutes, I would be glad to know..
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
7175 said:
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
Click to expand...
Click to collapse
Already tried, uneffective. Everything, no matter how low level (e.g. Odin) has no effect, like the memory is write-protected. I've read elsewhere this means the eMMC is fried, but if you go backwards in this forum you see many ppl had the very same problem in the past few days/weeks. Very strange indeed.
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Atreb92 said:
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Click to expand...
Click to collapse
No. I've always been on stock.
fabrice79 said:
No. I've always been on stock.
Click to expand...
Click to collapse
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Atreb92 said:
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Click to expand...
Click to collapse
That's what I say, but just go backwards and have a look at older post. I subscribed to ~10 posts until 15 Oct then I got tired of browsing backwards...
I'm allready looking at older posts thats why i'm saying it's pretty strange that there is a massive hardware fail for this many devices. If it's a software fail there must be a solution somehow.
Same problem by 31th December...
Yeah, i have the same problem since august 2014. This thread confirmes for me, that my Gnex is really dead. It is sad, it served my very well and i wanted to use it as secondary phone and as mobile hotspot.
Same for me at the beginning of december
This problem I've faced one time and that meant that EMMC is fried, as fellow members said earlier.
If you overwrite the storage and reboot then everything's the same means that you can't write (somehow) thus emmc is dead. Write failure also means that EMMC is dead.
It's really sad, but that's it
A little background and info before I begin- The Nexus 7 in question was running absolutely stock unrooted Android 5.0.2. Recently the battery was going downhill FAST with spikes on the battery graph as well as falling from ~35% to 5% instantly so I figured I would look for a new battery. There weren't many batteries out there that I was too impressed with (at least the reviews of said batteries certainly led me away from them) so I figured I would at least try Asus and see if they have a battery replacement service. They do, and mentioned that I will lose all data on the device. In an attempt to make their lives easier I asked if they would like me to do a factory reset for them, customer service representative said yeah that would be great.
SO... the real issue: I do the factory reset, and it stays on the "erasing..." image for 3+hrs, I was a little concerned but figured my best bet was to give it a little longer and see what it does. I go back to it ~30mins later and it looks as though it somehow got into recovery mode (stock recovery mode) and stayed there. Because I was curious (and impatient) I interrupted it and performed the following from this point:
erased cache from stock recovery
rebooted into fastboot menu
tried to reflash using the .bat file included in the nexus factory images from google but this failed on writing 'boot'.
tried then erasing boot, bootloader, system, cache, userdata- all failed.
new error includes "write failed" error.
on ANOTHER attempt to erase, any attempt to do so states that the partition does not exist (for all images/partitions).
So... has anyone experienced any write failed issues before? I cant erase anything OR write now apparently...
I see that this problem is kind of in line with a number of other threads. Just an FYI if anyone stumbles onto this post and not the others or is curious to see how this panned out:
I have RMA'd the nexus 7 for the battery and also told them about how the factory reset went down.
I will report back their findings but its looking to be the flash memory is corrupted somehow.
Hi,
I plugged my note 4 into the OEM charger and all of a sudden it just goes into a bootloop continuously.
Occasionally it will reach the home screen and reboot again, but more often than not.. it reboot before the Sprint logo comes up.
Was fine before i plugged it in and was trouble free prior to that.
My phone is stock, not rooted.
The fact that it will reboot even at the Note 4 welcome sign is leading me to believe this could be a hardware issue...
Any ideas?
Anybody had the same situation and had luck troubleshooting or fixing this?
Any and all help i much appreciated...
Regards,
asmd.
Can you boot into recovery?
First thing I'd try is to pull battery, boot into stock recovery and wipe cache and try to boot.
If not booting, try wiping cache and dalvik.
You have the option to just take it in for evaluation but you should determine if you have reactivation lock enabled before doing anything else.
Still not booting? Factory reset. But if you have reactivation lock enabled that is not a good idea. It would be better if one of the two above booted the phone.
If reactivation lock is enabled, you need to install the same update the phone is on to prevent factory reset protection from activating. Don't factory reset yet; Odin or taking in for service may be your only option. If it boots, you should be able to open with same unlock method as before.
If you have reactivation lock disabled, you're free to try factory reset or update to latest through KIES. I've heard Samsung Switch may work too. You could also factory reset and update or emergency recover with one of those.
If still not booting, if it just updated, I'd mention that and not the charger you mentioned. It could be corrupt memory due to battery failing or bad update. The eMMC may be failing too.
Sent from my SM-N910P using Tapatalk
samep said:
Can you boot into recovery?
First thing I'd try is to pull battery, boot into stock recovery and wipe cache and try to boot.
If not booting, try wiping cache and dalvik.
You have the option to just take it in for evaluation but you should determine if you have reactivation lock enabled before doing anything else.
Still not booting? Factory reset. But if you have reactivation lock enabled that is not a good idea. It would be better if one of the two above booted the phone.
If reactivation lock is enabled, you need to install the same update the phone is on to prevent factory reset protection from activating. Don't factory reset yet; Odin or taking in for service may be your only option. If it boots, you should be able to open with same unlock method as before.
If you have reactivation lock disabled, you're free to try factory reset or update to latest through KIES. I've heard Samsung Switch may work too. You could also factory reset and update or emergency recover with one of those.
If still not booting, if it just updated, I'd mention that and not the charger you mentioned. It could be corrupt memory due to battery failing or bad update. The eMMC may be failing too.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply...
Ive been messing with it all morning... and if i leave it a lone and it cools, it will last a little longer than when it becomes warm, rebooting quicker and quicker.
i managed to get into recover and did a factory reset and cleared cache.
it has made no difference.
The longest time its gone before rebooting is the lock screen.... and the it reboots again.
as it warms, it eventually wont even get past the Note 4 welcome screen before rebooting.. and then finally freezing and will require a battery pull.
Makes no difference if its on charge or off.
i have a sinking feeling about this.....
Could be terminal but you haven't tried to flash firmware on partitions with Smart Switch, KIES or Odin yet. Right? You can check the phone status while in download mode to verify reactivation lock is disabled.
Try one of those on PC or take it to Sprint to have it flashed again.
If you purchased at Best Buy and they have a Samsung Experience kiosk, they can do that too. Dunno, maybe it doesn't matter if you purchased there or not but they've flashed my phone a couple of times.
I've tried to guide you down the path of least effort to restore your, if possible. There's still some hope of recovery.
Edit: Your battery could be suspect. Let it cool and plug in to make sure it's at least 60% or higher. If the battery is near a year old, I'd suggest fully charging but get a replacement if you frequently discharge it to 15% or lower. Especially if you use fast charging.
But you've most likely discharged it with all that reboot activity and heating up. Kudos to you if you're managing all that and keep a healthy battery. Otherwise, the battery may be contributing to or causing your issues.
Sent from my SM-N910P using Tapatalk
thank you for the help..
reactivation lock is off.
i can't get it to reliably not reboot anywhere in any screen.. only screen that will stay on for any period of time is recovery... but the phone stays cool.
Its not the battery, i have two, and both do the same thing.. the battery does not get warm, area that gets warm is neft to the battery below the sd card slot. (sd card removed).
Frequency of hang/reboot seems to be related to how warm that area gets.
The most i have managed to do is get into my phone past the lockscreen and it will shortly freeze and reboot as it warms up.. it will reboot at the note 4 welcome screen or sprint logo... and repeat... eventually to hang.
Both batteries are charged fully using the external charger. (samsung oem)
Shame, not a scratch on her....
Oh well, on to Ebay for parts/AS IS and time to move on...
Even if doubtful, I'd still take it back to Sprint or place of purchase.
The Note 4 has a bit of history with eMMC failure. It's even happened with updates and Samsung and Sprint is apparently aware of it. A while back I saw that listed as an ongoing carryover of known issues that needed resolution.
I don't have true stats on exchanges but several users here have repeatedly gotten deals on replacement phones, paying a small percentage when they failed- similar to yours.
OTA updates have also been suspect to cause eMMC failure. But honestly, l don't know what causes this: bad hardware or updates? Maybe it's just bad hardware not taking updates well? Nonetheless, I don't know if I've just been lucky or my hardware is stable. Still going strong here with no hint of failure.
Sent from my SM-N910P using Tapatalk
can i still take it back even though its out of warranty?
nearing 2 years now....
asmd6230 said:
can i still take it back even though its out of warranty?
nearing 2 years now....
Click to expand...
Click to collapse
No promises. Couldn't hurt. If you don't like the answer you get from first Sprint store, try another.
I would mention that bit of history with the updates.
Sent from my SM-N910P using Tapatalk
asmd6230 said:
Hi,
I plugged my note 4 into the OEM charger and all of a sudden it just goes into a bootloop continuously.
Occasionally it will reach the home screen and reboot again, but more often than not.. it reboot before the Sprint logo comes up.
Was fine before i plugged it in and was trouble free prior to that.
My phone is stock, not rooted.
The fact that it will reboot even at the Note 4 welcome sign is leading me to believe this could be a hardware issue...
Any ideas?
Anybody had the same situation and had luck troubleshooting or fixing this?
Any and all help i much appreciated...
Regards,
asmd.
Click to expand...
Click to collapse
I have the exact same issue going on with my wives phone. Just started yesterday out of no where rebooting over and over. Never really getting past the Samsung splash screen. She got an update like a week ago, but other than downloading a new app several hours earlier nothing sticks out to why its happening. I was able to once get into safemode, but the phone rebooted a minute into it and typically doesn't even get to the sprint splash screen when I've tried to do it since. It's totally stock and has not been unlocked or rooted. I thought it could be the battery since so many of these boot issues on the Note4 deal with that when googling, but my battery from my working Note4 in her phone does the same thing and her battery in my phone works just fine. I can get into the recovery options menu (volume up + home + power) and I can get into the download area (volume down + home + power) for loading bootloaders and such for long periods of time with no issues. I've cleared the cache with no luck. Haven't tried factory reset yet because I want to try to recover the photos and stuff first. Searching for the issue on google I came across this software (android-recovery.net/android-recovery-mode.html#two) where I was able to use the download area and connect the phone with this app which used its own bootup and it was able to show me all the files on the phone for recovery so we could retrieve them. It wanted $50 to complete the process though and, knowing the advances that everyone here has made on their phones I decided to decline that and search these forums for a way to just access the file directory of my the phone and retrieve my wives stuff prior to factory resetting it. I believe something is wrong with the bootloader of the phone and that is why it cannot get to the android OS to start up, but I could be wrong. Reading various articles made me to believe that if I just were to unlock the phone for rooting that possibly that could fix this issue with the bootloader or at least be able to recover her photos and stuff. I do have insurance on the phone and could get it fixed or replaced, but that would be a $200 deductible I believe and first thing they're going to try is factory resetting the phone which will lose her data we're trying to save.
It almost seems as if I were to get TWRP installed that I'd be able to access the files without the need of loading any ROMs. But I'm not sure if that will work in my case or erase data when I do it. The threads I'm reading aren't clear on that part. I would really be grateful if anyone could help me out with figuring out the easiest way to recover her stuff or get it working. Its been a long time since I've unlocked any phones and they were all iPhones back in the day when they were only on AT&T and I had T-mobile and wanted to it work.
@dsm_gsx97
I would suggest you try Odin and install the same update, if possible. That may be the most likely to retain your data if it's not corrupted.
Unfortunately, I don't think TWRP recovery works for Note 4 to copy data to PC. But if you go with that, know that it will trip Knox and void factory warranty. But if that's not an issue, you could copy data from internal memory to extSdCard to salvage it if it's not corrupt or private.
I know KIES has an emergency firmware recovery mode that may offer to reprogram it. But you may lose your data. Not sure but I think your phone has to booted into system to backup with KIES or Smart Switch?
This thread has the recent available stock tars, Odin and general instructions to get you started.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
samep said:
@dsm_gsx97
I would suggest you try Odin and install the same update, if possible. That may be the most likely to retain your data if it's not corrupted.
Unfortunately, I don't think TWRP recovery works for Note 4 to copy data to PC. But if you go with that, know that it will trip Knox and void factory warranty. But if that's not an issue, you could copy data from internal memory to extSdCard to salvage it if it's not corrupt or private.
I know KIES has an emergency firmware recovery mode that may offer to reprogram it. But you may lose your data. Not sure but I think your phone has to booted into system to backup with KIES or Smart Switch?
This thread has the recent available stock tars, Odin and general instructions to get you started.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you very much for the quick response. I would rather not void my factory warranty in case I have to use the insurance to replace it so it sounds like TWRP is out which is why I didn't use it yet because I was worried about that. I did try KIES and it said that firmware upgrade and initialization would erase all data. So I ruled out using that too. I did notice while in the recovery menu of her phone that it says she's on N910PVPU1ANIE ...so I put my phone in recovery menu and I'm on N910PVPU4DPH4. Googling her version it looks like hers is very old and mine is fairly new which makes sense because I did the update a few days ago also. I wonder if hers is so old because that's what the other software program put it on to be able to bootload it to recover the files.
Anyways looking at your link I think I'll try oden with one of the more recent TARs after getting her stuff off with that program. Yes I'll just pay the $50 for peace of mind. I really appreciate your advice. Its not easy gathering all the answers without really being involved on this forum so thank you for that thread. None of the TARs listed is the update I have, but that shouldn't matter should it? As long as its a newer one than what it says she has?
dsm_gsx97 said:
Thank you very much for the quick response. I would rather not void my factory warranty in case I have to use the insurance to replace it so it sounds like TWRP is out which is why I didn't use it yet because I was worried about that. I did try KIES and it said that firmware upgrade and initialization would erase all data. So I ruled out using that too. I did notice while in the recovery menu of her phone that it says she's on N910PVPU1ANIE ...so I put my phone in recovery menu and I'm on N910PVPU4DPH4. Googling her version it looks like hers is very old and mine is fairly new which makes sense because I did the update a few days ago also. I wonder if hers is so old because that's what the other software program put it on to be able to bootload it to recover the files.
Anyways looking at your link I think I'll try oden with one of the more recent TARs after getting her stuff off with that program. Yes I'll just pay the $50 for peace of mind. I really appreciate your advice. Its not easy gathering all the answers without really being involved on this forum so thank you for that thread. None of the TARs listed is the update I have, but that shouldn't matter should it? As long as its a newer one than what it says she has?
Click to expand...
Click to collapse
Was it only the OTA update that updated that phone?
NIE is the original-initial release of the Note 4. If OTA tried to update it, it must have failed?
Nonetheless, you should know the history of that phone. I wouldn't install one of those recent updates until you've backed up your data. You may lose your data jumping to a much newer update.
The phone doesn't boot at all? If it does boot, you could run Phone Info for Samsung from Google Play to see what the partitions are actually at. That would help to recover that data if possible to do so. But also KIES could backup data if it boots.
The NIE stock tar is in post #2 of this thread.
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If it boots after Odin, your data may be OK. If not, may be corrupted data or partition.
Sent from my SM-N910P using Tapatalk
samep said:
Was it only the OTA update that updated that phone?
NIE is the original-initial release of the Note 4. If OTA tried to update it, it must have failed?
Nonetheless, you should know the history of that phone. I wouldn't install one of those recent updates until you've backed up your data. You may lose your data jumping to a much newer update.
The phone doesn't boot at all? If it does boot, you could run Phone Info for Samsung from Google Play to see what the partitions are actually at. That would help to recover that data if possible to do so. But also KIES could backup data if it boots.
The NIE stock tar is in post #2 of this thread.
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If it boots after Odin, your data may be OK. If not, may be corrupted data or partition.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
She's done plenty of updates over the last few years since we got the phoens. In fact she did that last update a few days before I did. That's why I was confused when I noticed what it said at the top of the bootloader screen for her update version. The phone does not boot at all. Only to the the Samsung splash screen and never gets to the sprint splash screen. It initially would get further, but now doesn't at all. I went ahead and paid for that software and have now backed up all her stuff. Was hoping to fix it without factory resetting the phone. At this point at least I have a backup, but ideally it would save her from losing all her texts and other crap.
dsm_gsx97 said:
She's done plenty of updates over the last few years since we got the phoens. In fact she did that last update a few days before I did. That's why I was confused when I noticed what it said at the top of the bootloader screen for her update version. The phone does not boot at all. Only to the the Samsung splash screen and never gets to the sprint splash screen. It initially would get further, but now doesn't at all. I went ahead and paid for that software and have now backed up all her stuff. Was hoping to fix it without factory resetting the phone. At this point at least I have a backup, but ideally it would save her from losing all her texts and other crap.
Click to expand...
Click to collapse
In that case, try the most recent stock tar in the first thread you were about to try.
Something seems off but trying to flash the original stock tar would be problematic if it was updated beyond Android 5.0
If it doesn't boot, you'll most likely have to factory reset it.
Sent from my SM-N910P using Tapatalk
Note 4 bootloop
just heat main ic little bit with past and check there is no heatup board on boot.and set is ok.tested
*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
So yesterday, the beta for Fortnite on android came out and I obviously signed up immediately. I selected my device, signed up, and downloaded the installer which would not open. I did not do any research, but assumed that the problem had to do with xposed. I disabled xposed and sure enough, the installer opened, but now it said that my device was not compatible. After some research, i saw that the beta was only going to be for samsung devices for about 30 days so, naturally, i tried to figure out a way to circumvent this restriction. I thought back to my early android days and my spoofing of devices with build.prop and decided to replace some of the entries such as "ro.build.vendor", "ro.build.model", etc. with those from the Galaxy S9. After a quick reboot, it actually worked to my surprise. I was clearly excited at this point and spent about 45 minutes on mobile data downloading Fortnite and then downloading the game files. Finally, the game was downloaded, i was signed into my account, and I was waiting to join a Lobby. After entering a lobby and dropping out of the bus, I was descending towards tomato town to test out my favorite game on my favorite device when suddenly the loading screen came back up(this is where my luck took a turn for the worst). I was returned to the main menu and given a message along the lines of "Fortnite cannot be played on devices that do not pass safetynet, have an unlocked bootloader, or are rooted... Attempting to bypass this check may result in permanent account ban" At this point I began to get annoyed and figure that since I had come all this way I would just keep going. I went and turned on magisk hide from the magisk manager and set it to hide xposed. I then used the option to reinstall magisk under a different package name. I continued to enable exposed again and enable x privacy(I was planning on attempting to do exactly what i had been warned against by Fortnite). I then rebooted and... well, didn't reboot. I got stuck on the green RAZER circle for a bit then the screen just went black. After a few reboots i decided to restore my build.prop through TWRP. This didn't help at all so I decided to clear the cache and dalvik(this didnt work). At this point i decided to back up my photos and the Fortnite apk to my sd card and do a reset through TWRP. The reset did nothing so i figured I would try installing a custom ROM. I downloaded and installed resurrection remix. On the first boot i was greeted with the storage decryption prompt. I entered my password and it said that it was successfully decrypted but was corrupt and i had to factory reset. I pressed the button and the device went to the RAZER logo then turned off. I tried another boot tand the same thing happened so I went to TWRP manually and did yet another reset..... it failed. This is where i panicked. I went through twrp and did a bunch of **** like try to fix contexts and repair data until finally something succeeded and I was able to wipe data. From there I again booted into resurrection remix where it just hung on the boot gif. I plugged the phone into my pc and ran "adb logcat" and it said something about missing files in vendor. I then remembered that I had the RAZER factory images downloaded. I tried the flashall.bat and that just hung on the first command that was only supposed to push 44kb. I knew I had severely fluckled up at this point so seing as there was nothing else to lose I went back into twrp and tried to flash Resurrection again. After that succeeded and i pressed reboot on TWRP I was warned that no system image was installed. Remembering about the vendor thing from before, I pulled the stock vendor image and installed it through TWRP. I was going to flash all the images manually. I was unaware that flashing to vendor would remove TWRP so afte ra unwanted reboot, TWRP was gone for good. Since then, I have tried numerous things in download mode and am always met with messages such as "write failed {no error}", "a/b permissions not supported", "bootloader update required", and many moooore.
At this point I feel that all hope is lost but I feel that I have learned a valuable lesson and can be used as a perfect example of why you should think before you act. I would like to still ask for help from peers who are most likely infinitely more knowledgeable than I am. If you feel that you can help contribute to saving my baby(RAZER phone) in any way or you feel that this helped you in some way, don't hesitate to reply to this thread.
Thank you all for reading to this point and thank you in advance for any insight you have to offer.
Firstly, may I empathize with your pain, and I do need to say..."whooops". Maybe this can only be repaired from a RMA to Razer themselves. I'm not someone who roots his Android devices as I prefer them "as is" but I am a major Linux user and faff with those OSes till I break them. maybe contact Razer with the issue, maybe they can help. And again.....you have my sympathys.
Yeah, I'm going to wait a few days and see if either I can figure anything out or someone else can help me, but after that I will probably contact them. I just hope this doesn't end up being an expensive repair if it comes to sending an RMA. Thanks for your sympathy btw ???
I hate to say this, but today I finally got Fortnite installed and ready for use, totally officially, from epic games, and I'm now awaiting my email with my login access...yes, you may kick me, I will accept a virtual kick.
See, this hurts, it really does. I’m not going to virtually kick you though. I like to be kept in the loop on developments like this. ?
Just to make sure...did you try installing the stock image?
Why don't you just flash a fastboot image from MR1?
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-5038.zip
Yes I tried. That was the first thing I did when things started going south for the winter but it did not do anything. It kept giving the errors that i spoke of such as "unknown command" or "failed(no error)".
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
lostnsound said:
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
Click to expand...
Click to collapse
Did you do everything else the OP did, like changing build.prop? Or were you able to just install and attempt to play then it shut you out?
I received that same error message, but I'm not rooted, it seems the beta hasn't been properly coded to see changes in device status and architecture as ok. I also believe that epic games have bypassed the Google play store as they cannot guarantee the stability of the app and it would be seen by Google play store as defective. Maybe its something we need to wait for them to get fixed. Remember this is a "beta" version and is still in development.
lostnsound said:
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
Click to expand...
Click to collapse
As long as you did not edit anything within your system, you should be fine. The game itself did not brick my phone, I bricked my phone because I was careless. I do however agree 100% that there should have been some sort of prior notice that rooted phones would not be compatible because it would have given me some time to do proper research on returning to stock before hand.
ShaneRagans said:
So yesterday, the beta for Fortnite on android came out and I obviously signed up immediately. I selected my device, signed up, and downloaded the installer which would not open. I did not do any research, but assumed that the problem had to do with xposed. I disabled xposed and sure enough, the installer opened, but now it said that my device was not compatible. After some research, i saw that the beta was only going to be for samsung devices for about 30 days so, naturally, i tried to figure out a way to circumvent this restriction. I thought back to my early android days and my spoofing of devices with build.prop and decided to replace some of the entries such as "ro.build.vendor", "ro.build.model", etc. with those from the Galaxy S9. After a quick reboot, it actually worked to my surprise. I was clearly excited at this point and spent about 45 minutes on mobile data downloading Fortnite and then downloading the game files. Finally, the game was downloaded, i was signed into my account, and I was waiting to join a Lobby. After entering a lobby and dropping out of the bus, I was descending towards tomato town to test out my favorite game on my favorite device when suddenly the loading screen came back up(this is where my luck took a turn for the worst). I was returned to the main menu and given a message along the lines of "Fortnite cannot be played on devices that do not pass safetynet, have an unlocked bootloader, or are rooted... Attempting to bypass this check may result in permanent account ban" At this point I began to get annoyed and figure that since I had come all this way I would just keep going. I went and turned on magisk hide from the magisk manager and set it to hide xposed. I then used the option to reinstall magisk under a different package name. I continued to enable exposed again and enable x privacy(I was planning on attempting to do exactly what i had been warned against by Fortnite). I then rebooted and... well, didn't reboot. I got stuck on the green RAZER circle for a bit then the screen just went black. After a few reboots i decided to restore my build.prop through TWRP. This didn't help at all so I decided to clear the cache and dalvik(this didnt work). At this point i decided to back up my photos and the Fortnite apk to my sd card and do a reset through TWRP. The reset did nothing so i figured I would try installing a custom ROM. I downloaded and installed resurrection remix. On the first boot i was greeted with the storage decryption prompt. I entered my password and it said that it was successfully decrypted but was corrupt and i had to factory reset. I pressed the button and the device went to the RAZER logo then turned off. I tried another boot tand the same thing happened so I went to TWRP manually and did yet another reset..... it failed. This is where i panicked. I went through twrp and did a bunch of **** like try to fix contexts and repair data until finally something succeeded and I was able to wipe data. From there I again booted into resurrection remix where it just hung on the boot gif. I plugged the phone into my pc and ran "adb logcat" and it said something about missing files in vendor. I then remembered that I had the RAZER factory images downloaded. I tried the flashall.bat and that just hung on the first command that was only supposed to push 44kb. I knew I had severely fluckled up at this point so seing as there was nothing else to lose I went back into twrp and tried to flash Resurrection again. After that succeeded and i pressed reboot on TWRP I was warned that no system image was installed. Remembering about the vendor thing from before, I pulled the stock vendor image and installed it through TWRP. I was going to flash all the images manually. I was unaware that flashing to vendor would remove TWRP so afte ra unwanted reboot, TWRP was gone for good. Since then, I have tried numerous things in download mode and am always met with messages such as "write failed {no error}", "a/b permissions not supported", "bootloader update required", and many moooore.
At this point I feel that all hope is lost but I feel that I have learned a valuable lesson and can be used as a perfect example of why you should think before you act. I would like to still ask for help from peers who are most likely infinitely more knowledgeable than I am. If you feel that you can help contribute to saving my baby(RAZER phone) in any way or you feel that this helped you in some way, don't hesitate to reply to this thread.
Thank you all for reading to this point and thank you in advance for any insight you have to offer.
Click to expand...
Click to collapse
I feel your pain i locked me bootloader and bricked my phone crying atm
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
i tried many thing as well but if your bootloader is unlocked try use the 7.1.1 ver and add -i 0x1532 to the command
btw anyone wanna buy a paper for lol
Do any of you guys that bricked your phones happen to have 3 rescue?
It costs £100 but you'll get a new phone next day no questions asked.
I did this when I bricked my Samsung galaxy S6 edge+ last year.
It's expensive, but surely better than having a £500 paper weight.
Just wanted to let everyone know that Razer repaired it for $15.