Grumble grumble bootloop grumble - G4 Q&A, Help & Troubleshooting

Like so many others, my phone spontaneously developed the infamous bootloop problem. I've had the phone for less than a year, so Sprint will replace the phone for free, but I have a lot of things stored on internal memory of the device that I would very much like to retrieve before the exchange.
I've tried freezing it and heating it--both techniques succeeded in getting the phone to boot up, but not long enough to do anything other than confirm that all my data is still there.
I've been searching the web and this forum and found the guides about disabling big cores, but it seems that the files do not apply to my version of the phone, the LS991. Other guides describe booting the phone into recovery mode or fastboot/download mode, both of which I've done successfully, but I haven't been able to find out what to do from there. ADB only seems to recognize the phone is there when it's in "sideload mode."
Yes, I rooted my phone shortly after I got it, but I don't have any custom recovery installed because at the time, and apparently still, there aren't any available for this model!
So here I am with a phone that has my data on it but won't boot, and all the solutions beyond extreme temperature and hope are unavailable for this version.
Am I missing something? Is there a reason that a chunk of the population facing this growing problem have been left without the means of doing anything about it? Has someone produced the tools (either a custom recovery or a big cores disabling file) and I just can't find them anywhere?
Again, I'm not the first to ask, but I'm asking anyway. If anyone knows something that would help, please speak up!

Related

[Q] Bricked Phone...Peculiar Situation

Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!
As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.
Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again
This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app
I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that

Accidentally Botched SW3 Firmware by Flashing TWRP

When I got my SW3 last summer, I stupidly ignored all those warnings about flashing TWRP to recovery, mostly because I didn't see what harm could come of it. However, while investigating a battery drain that's persisted despite multiple flashes to stock and more than a few attempts to use crpalmer's LCA43 kernel, I discovered via my SW3's kernel log that it's got some serious weirdness going on with its firmware.
As it turns out, it's reloading the pedometer firmware every three seconds. This happens because every time it loads the firmware, it promptly encounters some manner of error while running it, which then prompts Android to try to reload the firmware. My first hint that this was a firmware issue came from the fact that I can't access any sensor data via the developer menu. Under 'Manufacturer: Menu-Launcher' at the bottom of Developer Options, the entries for Accelerometer, Gyro, Magnetometer, and Compass are all blank, while Ambient Light Sensor and Step Counter are perpetually stuck at 0.0.
After trying everything I could think of in my attempts to fix this issue, I then began investigating other variations from stock that I'd had over the months that I've had my SW3. Rooting didn't appear to change anything related to the firmware, and crpalmer's LCA43 kernel (and craigcharlie's simple MTP mod and, later on, alex6600's modified version of the kernel itself) didn't appear to cause any of the issues I'd been experiencing for anyone else. Finally, I found a comment somewhere about the fact that flashing TWRP to recovery instead of just booting it would really mess things up because it uses a device tree different from the SW3's stock device tree.
Since then, I've been trying everything I can imagine to fix this, but I haven't had any success thus far. Because of that and a few other reasons, I haven't been able to mess with this since the end of January, but I'm really getting tired of my SW3 only lasting for about 6-8 hours with pretty minimal use. I think the closest I got to any sort of progress was using dd to individually flash partitions that'd been uploaded, but I don't think I was ever able to find an upload of mmcblk0p19, dt-blob.
Does anyone have any ideas about what I might be able to do to fix this? Specifically, I'm curious to know whether or not dding partitions damaged when I flashed TWRP should work; if so, would someone be so kind as to either post or PM me dded copies of the relevant partitions? Thanks in advance for the help!
Repair with PCCompanion. Did that some weeks ago. Version is LCA43.
If pc companion does not work (and it probably wont), hold down the button on boot, and you can force it to usb mode. If that does not work, hit the button twice to go to fastboot and flash the original OS (look for the repair threads).
Good luck.
Sent from my SM-T810 using Tapatalk

Help me solve a complicated case - Backup bricked 100% stock M8

Hi All,
I seem to have run into a very dire case where my 100% stock M8 is completely unusable, due to what seems to be a failed OTA update.
Phone will boot up normally, but as soon as the home screen comes up a "com.android.systemui" error comes up, preventing any type of further interaction with the os, since the screen goes black and start flashing an empty default background on and off indefinitely.
Now, I'm fairly computer literate but I never rooted or modded any phone so I spent the last 3 days on these forums looking up information and learning what rooting, bootloaders, ADB and all that fun stuff I had never heard of before meant. However, after initially being optimistic about at least getting my data back before an inevitable factory reset I have reached a dead end.
Here's what I went through so far:
- To backup without normal access to the OS, I need the ADB pull command
- To use the ADB, I need "USB debug" enabled BUT Can't access settings, so can't enable USB debug
- Searched for ways to work around enabling USB debug via bootloader/recovery
- Found out you can use ADB with a custom recovery image
- Tried flashing a custom image BUT bootloader is locked, so no dice
- Found the only way to unlock the bootloader with S-ON is via HTC dev BUT will wipe all data upon unlocking
- Found no way to set S-OFF without wiping
I can't believe a fully stock phone can be hard bricked by a simple OTA update just because I never tampered with it (cos if I did, I would have a lot more options).
I'm aware I'm going to have to factory reset eventually anyway, but I want to pull out whatever data I can first.
Please help, I'm running out of ideas.
Thank you all.
lo11o said:
I can't believe a fully stock phone can be hard bricked by a simple OTA update just because I never tampered with it (cos if I did, I would have a lot more options).
Click to expand...
Click to collapse
I can believe it, since I've seen it happen enough times to folks on these forums. You do a major update to the OS, bootloader, and radio; and there is always a possibility of rendering the phone non-operational.
What kind of data are we talking about? Is it on internal storage, and if so, can you see internal storage on your computer when you connect the phone?
If no to any of that, you're probably stuck at a dead end. If the data is important, it should have been backed up off-phone to begin with.
Thanks for replying redpoint, and the answer to both questions unfortunately is no.
I'm mostly interested in backing up text messages and notes, everything else is either synced with google or redownloadable. Of course I'll take care to remove the SD before resetting so whatever's in there won't be affected.
I have no idea what could have caused this mess. What's more infuriating is that the system underneath the error dialog does seem to be functional, notifications pop up and it even rings if I try calling my number, but can't pick up. Even Wi-Fi is on, for the record. Everything just goes to hell as soon as that dialog goes away (yes, I've tried ignoring it and trying to get the notification bar down). It's just that the fact it's technically not in a "bootloop" situation made me hope.
I read somewhere on these forums that unless your phone doesn't charge, doesn't turn on and doesn't even get recognised by a computer, it can almost always be saved. Am I truly SOL?
lo11o said:
I read somewhere on these forums that unless your phone doesn't charge, doesn't turn on and doesn't even get recognised by a computer, it can almost always be saved. Am I truly SOL?
Click to expand...
Click to collapse
If you can't interact with the phone to turn on Debugging, I personally can't think of any way to pull the desired data off the phone.
Bummer. I'll proceed with the factory reset then, live and learn.
Thanks for the advice, I learned a lot of very useful stuff from this community, having the patience to read and process all the wealth of information - even n00b-friendly, too. :good:

I'm an idiot and I got some crazy malware. Help please.

OK so I smashed my s5, am a UDP verizon guy and hooked on the open bootloader, so i searched far and wide for another one with the 15 chipset...which I didn't find but I found a note 4 with it.
I bought it and unlocked it and loaded on a rom I loved. (5.0.1 og5). Well...no sense lying here...I was trying to do some less than kosher things regarding my ex's Facebook account with it. In the process I wasn't smart enough to cross check MD5s (a precaution I learned all too well) and opened an app that has me baffled.
It basically hijacked admin on my device completely. No Antivirus program can touch it, though many detect it. "Unknown sources" in my security folder is stuck permanently enabled, and I can't take over as admin on my own brand new note4.
I have tried flashing twrp and titanium backups to no avail, and also tried the safe stock og5 firmware through Odin but it never completes. I am stuck. I have logcat records and all the tools I would think might help, but I can't get rid of it...it seems to have used root and embedded itself into every facet of the device.
I am willing and ready to do anything including a full unroot and stock rom, I just don't want a locked update. Can anyone help me please?
As of now, no roms break it, only the stubborn malware CM app tries to get rid of it, but only identifies it as "suspicious file". My user admin and unknown sources are both locked, and a gaggle of bizarre log events happen constantly, forcing my device into crazy lag. As soon as it happened I received a couple random number-link blank text messages, but I never opened them. I don't have the numbers saved as I've flashed the phone like 30 times since trying to rid myself of this. Aside from the lag and locked unknown sources and admin, and an inability to clear trusted credentials, the phone seems to run normally, though I am scared to use it to log on to pretty much anything. The malware didn't come from a text, but from an app that I knowingly permitted thinking it was something else and I feel like a moron for it. It doesn't seem to have a name. It installed as an untitled app and I couldn't delete it with the root system app deleter, because it put a green bar over the check box in the app. I got rid of it with titanium, but to no avail. It still lurks.
Thanks in advance, and let me know of any screens hits or logs or tests I can provide to help.
At that point, I would recommend using Samsung's Smart Switch for PC program to do an emergency firmware upgrade & initialization. This will download a full copy of the stock firmware for the device (including a few bits that you won't find in stock firmwares available for download through sites like SamMobile) and will erase everything on the device and restore your phone to stock firmware.
If you are in the US and have a Best Buy nearby, you can see if one of their Samsung reps can perform a factory recovery using their SMART tool (which will do the same thing that Smart Switch's emergency firmware initialization will). Officially, rooted devices are not supported and they may rightfully refuse to do this, but it's worth asking if you don't have a computer to use for Smart Switch or don't want to wait.
You will need to redo the developer conversion, but that's the only thing I can think of that will definitely completely restore your phone to stock and eliminate all traces of whatever you installed.
thanks. that solved my problem and got it back to stock, rid of the malware completely. unfortunately, when i tried to return to the rom i had used, everything fell apart for me :/.

PSA: Bricking my phone with Fortnite(good educational story and cry for help)

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.

Categories

Resources