Hey guys I really need your help with something! I recently rooted my LG G3 using stump and downloaded an application that needed to restart my phone so I did and now when i try to turn my phone on all I see is the LG load screen but nothing will happen after that. The LED continues to flash at the load screen, but it wont go anywhere. Also, I have tried to wipe cache, factory reset, and apply updates in the recovery area but nothing seems to work. I have also tried doing a factory data reset but like everything else i can only make it to the load screen. This is the first device i have ever rooted so I am very new at this but I really need some help!
Sounds like the app did something malicious. What app?
I would like to make a suggestion for you and for other noobs planning to root and mod their devices.
Firstly every single person whom ever tweaked their device flashed custom ROMs, Kernels etc either has or will need some help at some point.
The most valuable point that I can stress is this, before you root, find out how to undo it and how to fix or troubleshoot different senarios.
If you see the LG animation then this means you have any number of ways to fix the issue(you're not doomed), check the tutorials, do some reading and search its all here, you managed to find out how to root etc so now do a little more to find out how to fix, good luck.
Can you enter download mode?
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!
hello newbie here
so i had until now a stock version of mm on my LG G3 D855 (i guess the phone is european because im from israel)
i tried to change the version to cyanogen mod 14.1 cuz lately my battery has been dying pretty quick (and i basically had no idea whatsoever on what i was doing)
so something happen along the way while i was following the tutorial and the phone just would get stuck on the LG screen with nothing happening. i tried a couple of methods (both TOT and KDZ or something like that) to just get back to some sort of functional phone (i really need it for work) with no luck.basically i see a MiniOS screen of some kind every time i boot for a couple of seconds then it goes to a blue screen saying Factory Reset Status 2. I have no idea what to do now and ill really apreciate to get some sort of help.
thank you very much.
Try and boot into recovery then you should be able to drag another rom onto your SD from your computer. Then you can flash a marshmallow build or fulmics easily. Probably I would recommend the most recent fulmics if you are still learning about flashing and what not. They have a good installer which is easy to use and it is near bugless. All Nougat ROMs have some fairly large bugs, so you probably don't want to be using that for work unless you know a bit about working around these problems.
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.
Good evening you absolute legends!
After quietly reading along since 2013 and flashing a few phones over the years thanks to you, I'm now at a point where I can't think of anything to do with my problem.
So I bought my dad a used G960F for his birthday and wanted to install Lineage OS just as I did with mine a couple months ago. To make things short, in the meantime all ROMs I used where deleted, so I did the same procedure but with other ROMs, and well ... bricked the phone. After a week or so I finally got it working (didnt know about Samsungs bootloader hierarchy and couldn't flash a ROM with a lower BL), just to find out now that in the process the IMEI got deleted completely.
After seeing too many shady websites this is what I tried so far:
Flashing with a Pit-File + NAND Erase and Re-Partiton
Flashing stock rom (tried both Android 9 and Android 10)
Erasing everything or only parts of the efs/ folder, even though I only found that applied to other Samsung phones than mine
One ROM I tried back when the phone was bricked was from _alexndr, and I found one post where a user also lost IMEI after using it but got it back when he installed the ROM again. This one I will try out now.
So I have one G960F working but with empty IMEI. Not a bunch of zeros, its simply empty. I know one correct IMEI, since its printed on the OEM box three times. (Don't know why they dont print both numbers on the box....). I've seen a bunch of semi-(il)legal Apps that let you change the IMEI, but I dont feel like getting into that and it wouldn't help me with the second IMEI.
(Additionally, I have my own G960F completely working, if it helpes in any way.)
Does any of you have any ideas left or has experience with such a problem?
Either way, thanks for taking your time with me and everybody else!
Cheers Anthony
Hi guys!
I solved my problem and maybe my way can help some of you.
As I understood from _alexndr's thread [1] is that you can not only not go down a BL-Version when flashing, but you can't also go down in the CSC version. But while doing the first thing resolves in an error while flashing, the second one simply works but therefore can't detect the IMEI etc sometimes.
My solution in the end was to flash _alendr's kerlel, force my CSC module (maybe this parts isn't necessary) while flashing and and then installing the BL he provided [2].
Even though this thread stayed empty, I still wanna thank all of you for keeping up so much work!
[1] https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-may-09.3764822/
[2] https://forum.xda-developers.com/t/...support-may-09.3764822/page-151#post-84984391