Related
Hey all. Fist off, sorry about the new account and posting here in the Q&A and not development, but let me explain. I have been a member of XDA for a few years- my main account(and only account until being forced to create this one) is andr0id23. However, I am unable to login to that account. I keep getting an incorrect password error message and am constantly locked out of my account. I have emailed the people who can help with this issue, but still not having any luck. They did reset my password(even though I knew my password), but that still doesn't work. I try it once but it says i have used up all my attempts and locks me out for what is supposed to be 15 minutes, but seems to be forever instead. But I digress, just wanted to explain why I am posting from a brand new account and in this section(new accounts are not allowed to post in development). Now on to my issues I am hoping someone can help with. I typed it up in notepad last night while waiting for my account to be accessible and am just going to copy and paste it:
Hi all, I was hoping to get some help on my Galaxy Note 8.0. It is model number GT-N5110. It was given to me by a friend, who likes
to try rooting his devices, but has no experience and is actually quite computer illiterate. When I received it it wouldn't boot up,
but only go do a screen that says something like "Downloading. Please do not power off". I have no idea what is on there as far as firmware
or custom ROMs.
I am pretty comfortable with Android development as far as flashing custom ROMs, rooting, unlocking bootloaders, etc, but haven't been active for
some time now. I have owned a Droid, Droid 2, HTC Incredible, Droid X, HTC Thunderbolt, and Motorola Xoom and have rooted,
unlocked, and/or installed custom ROMs on all of them, ass well as doing so on several devices that aren't mine. I have used "one click" type methods
as well as more hands-on adb methods. I just mention so to show that while I am far from an expert, I do have some experience.
But I am stuck on this tablet. I can boot into Download Mode and was able to flash CWM Recovery via Odin. In CWM I tried
wiping data, cache and Dalvik cache, but when I go to reboot I get a message saying the device is not rooted and would I like to root. It doesn't seem to do any
good. I did try rooting thru odin, and it said it was successful. I have also flashed the stock firmware thru odin, but am still not able to boot. The
closest I get is a boot loop. Also, Kies does not recognize my device.
So, I can boot into download mode and CWM Recovery(though I don't know if I am actually rooted
and it will be of any use), and Odin does recognize the device. I have tried flashing stock firmware to no avail. If anyone
has any suggestions, I would be greatly appreciative and definitely willing to try. I can give you any additional info you
request. I was thinking of flashing a custom ROM, but not sure as I don't know what the tablet is currently running. If anyone
has anything to try as far as flashing a ROM or firmware, a d/l link would be greatly appreciated if at all possible.
I have been having the worst luck with samfirmware or sammobile(two sites that are named something like that). I have spent
literally hours waiting for the downloads, and the 2 times i did get lucky, the files were messed up. Again, I would be
extremely greatful for any and all help.
Nashtar said:
Hey all. Fist off, sorry about the new account and posting here in the Q&A and not development, but let me explain. I have been a member of XDA for a few years- my main account(and only account until being forced to create this one) is andr0id23. However, I am unable to login to that account. I keep getting an incorrect password error message and am constantly locked out of my account. I have emailed the people who can help with this issue, but still not having any luck. They did reset my password(even though I knew my password), but that still doesn't work. I try it once but it says i have used up all my attempts and locks me out for what is supposed to be 15 minutes, but seems to be forever instead. But I digress, just wanted to explain why I am posting from a brand new account and in this section(new accounts are not allowed to post in development). Now on to my issues I am hoping someone can help with. I typed it up in notepad last night while waiting for my account to be accessible and am just going to copy and paste it:
Hi all, I was hoping to get some help on my Galaxy Note 8.0. It is model number GT-N5110. It was given to me by a friend, who likes
to try rooting his devices, but has no experience and is actually quite computer illiterate. When I received it it wouldn't boot up,
but only go do a screen that says something like "Downloading. Please do not power off". I have no idea what is on there as far as firmware
or custom ROMs.
I am pretty comfortable with Android development as far as flashing custom ROMs, rooting, unlocking bootloaders, etc, but haven't been active for
some time now. I have owned a Droid, Droid 2, HTC Incredible, Droid X, HTC Thunderbolt, and Motorola Xoom and have rooted,
unlocked, and/or installed custom ROMs on all of them, ass well as doing so on several devices that aren't mine. I have used "one click" type methods
as well as more hands-on adb methods. I just mention so to show that while I am far from an expert, I do have some experience.
But I am stuck on this tablet. I can boot into Download Mode and was able to flash CWM Recovery via Odin. In CWM I tried
wiping data, cache and Dalvik cache, but when I go to reboot I get a message saying the device is not rooted and would I like to root. It doesn't seem to do any
good. I did try rooting thru odin, and it said it was successful. I have also flashed the stock firmware thru odin, but am still not able to boot. The
closest I get is a boot loop. Also, Kies does not recognize my device.
So, I can boot into download mode and CWM Recovery(though I don't know if I am actually rooted
and it will be of any use), and Odin does recognize the device. I have tried flashing stock firmware to no avail. If anyone
has any suggestions, I would be greatly appreciative and definitely willing to try. I can give you any additional info you
request. I was thinking of flashing a custom ROM, but not sure as I don't know what the tablet is currently running. If anyone
has anything to try as far as flashing a ROM or firmware, a d/l link would be greatly appreciated if at all possible.
I have been having the worst luck with samfirmware or sammobile(two sites that are named something like that). I have spent
literally hours waiting for the downloads, and the 2 times i did get lucky, the files were messed up. Again, I would be
extremely greatful for any and all help.
Click to expand...
Click to collapse
I would download stock ROM and flash with Odin 3.07. There are a number of threads that explain the process. Here is one... http://forum.xda-developers.com/showthread.php?t=2728370&page=3
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!
gooberdude said:
I would download stock ROM and flash with Odin 3.07. There are a number of threads that explain the process. Here is one... http://forum.xda-developers.com/showthread.php?t=2728370&page=3
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!
Click to expand...
Click to collapse
I was never able to grab any downloads from SamMobile or SamsungUpdates. It just loads forever until it times out. I did, however, grab a stock firmware download from another thread. I flashed it with Odin 3.07 but it did nothing for me. I am attempting to download the files from the 2 sites again now. Hopefully I'll have better luck. Thanks
Idiot
Ok so I am a complete tool. I was able to get it going. I knew what to do, and was doing it, but was doing it wrong. The thread you linked made it dawn on me. I was able to flash the stock firmware through odin 3.7. Sorry if I wasted your time and I thank you wholeheartedly. Now time to root and have some fun :good:
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:
Dear all,
I hope you can help me retrieve my lost SMS. Please excuse me if the question has been asked before, but all threads I found were dealing with very different devices and/or devices rooted prior to the event.
Also, I'm an absolute newbie to this matter, up until now my phones have worked just fine the way they were delivered.
I have an unrooted HTC One XL with Android 4.2.2 and HTC Sense 5.0 (~4 years old). Yesterday, my phone went out of power while I was watching a youtube-video. Back home, I started to charge it, and turned it back on after half an hour of charging. Everything seemed perfectly normal, but when I got an SMS and openend it, I realized it was the only SMS left in Messages! So far, I have never done a backup of my SMS (even though some of them are very precious to me - I'm such a naive fool ), because the nice ladies at the O2-shop always helped me transfer them from the old phone to the new one.
Please excuse the wall of text to follow, but I have downloaded a ton of software already to save my data, and I guess you need to know precisely to help me:
First, I turned on flight mode to keep new SMS from writing over fragments of the old SMS which might still be there. Then I've "tried turning it off and on again" , but to no avail. Then I've tried recovery software working without root, Myphoneexplorer and Titanium backup, but of course they only found the one SMS that I hat received after the crash. Then I downloaded Android Data Recovery by Aiseesoft, which unfortunately needs a rooted device, so I set out to root my first phone.
I tried different Apps, towelroot + SuperSU, King Root and Kingo root, which all didn't work. I then tried the "official" way via htcdev.com, but got stuck in the middle (My phone was in fastboot usb attached to my laptop, but the command fastboot oem get_identifier_token was not understood. Imagine my distress, I'm such a newbie that just the sight of a command window gives me sweaty palms.). Maybe something to do with the drivers (the HTC drivers coming with Hasoon2000's Toolkit, which I also tried for the "official HTC route", weren't compatible with my Windows 8 laptop, so I had to download some universal ADB drivers instead).
I've asked my more tech-savvy friends on fb, who mentioned some of the Apps I've tried, but also frightened me with the contribution that if I root my phone now, I'd HAVE to go through a factory reset in the process. So my SMS fragments, if there were any on my phone still, would be erased by the time I could give Android Data Recovery a shot.
So please help me with the following:
- Do you see any way how I can retrieve my lost SMS?
- Is there a way to root without factory reset?
Additional info: I don't mind if my phone gets destroyed in the process of saving my SMS. It's anyhow time for a new one. What I WOULD mind is destroying my laptop, so as a laywoman I would only very reluctantly try stuff like "force-feeding" my laptop new drivers and such. Still, I would be thankful for any kind of ideas, whether I'll be brave enough to try them or not.
Thank you very much in advance,
M&C
Marigold&Catnip;69616753 said:
Dear all,
I hope you can help me retrieve my lost SMS. Please excuse me if the question has been asked before, but all threads I found were dealing with very different devices and/or devices rooted prior to the event.
Also, I'm an absolute newbie to this matter, up until now my phones have worked just fine the way they were delivered.
I have an unrooted HTC One XL with Android 4.2.2 and HTC Sense 5.0 (~4 years old). Yesterday, my phone went out of power while I was watching a youtube-video. Back home, I started to charge it, and turned it back on after half an hour of charging. Everything seemed perfectly normal, but when I got an SMS and openend it, I realized it was the only SMS left in Messages! So far, I have never done a backup of my SMS (even though some of them are very precious to me - I'm such a naive fool ), because the nice ladies at the O2-shop always helped me transfer them from the old phone to the new one.
Please excuse the wall of text to follow, but I have downloaded a ton of software already to save my data, and I guess you need to know precisely to help me:
First, I turned on flight mode to keep new SMS from writing over fragments of the old SMS which might still be there. Then I've "tried turning it off and on again" , but to no avail. Then I've tried recovery software working without root, Myphoneexplorer and Titanium backup, but of course they only found the one SMS that I hat received after the crash. Then I downloaded Android Data Recovery by Aiseesoft, which unfortunately needs a rooted device, so I set out to root my first phone.
I tried different Apps, towelroot + SuperSU, King Root and Kingo root, which all didn't work. I then tried the "official" way via htcdev.com, but got stuck in the middle (My phone was in fastboot usb attached to my laptop, but the command fastboot oem get_identifier_token was not understood. Imagine my distress, I'm such a newbie that just the sight of a command window gives me sweaty palms.). Maybe something to do with the drivers (the HTC drivers coming with Hasoon2000's Toolkit, which I also tried for the "official HTC route", weren't compatible with my Windows 8 laptop, so I had to download some universal ADB drivers instead).
I've asked my more tech-savvy friends on fb, who mentioned some of the Apps I've tried, but also frightened me with the contribution that if I root my phone now, I'd HAVE to go through a factory reset in the process. So my SMS fragments, if there were any on my phone still, would be erased by the time I could give Android Data Recovery a shot.
So please help me with the following:
- Do you see any way how I can retrieve my lost SMS?
- Is there a way to root without factory reset?
Additional info: I don't mind if my phone gets destroyed in the process of saving my SMS. It's anyhow time for a new one. What I WOULD mind is destroying my laptop, so as a laywoman I would only very reluctantly try stuff like "force-feeding" my laptop new drivers and such. Still, I would be thankful for any kind of ideas, whether I'll be brave enough to try them or not.
Thank you very much in advance,
M&C
Click to expand...
Click to collapse
I currently see no means to save your SMS { I am really sorry to say that }
The first step to root is to unlock bootloader, unlocking it sure wipes the data
DevUt said:
I currently see no means to save your SMS { I am really sorry to say that }
The first step to root is to unlock bootloader, unlocking it sure wipes the data
Click to expand...
Click to collapse
Oh, that wasn't what I had hoped to hear. Anyhow, thanks for your contribution.
Will unlocking the bootloader completely erase the data, or will it "only" allow the phone to overwrite the space if new data comes up? If the latter were the case, maybe the Android Data Recovery might have a chance afterwards?
Please excuse my newbie questions, I bet this is common knowledge among all of you.
I've also posted this on Reddit and the OnePlus forums, but I'm hoping I can find an answer here, too.
Long story short: I really messed up my phone and I'm looking for help getting it to at least boot into the system. Lots of weird, confusing things have happened within the past few days, so bear with me; might be a long story, but I'll try to give you the abridged version.
I run locked and unrooted. I flashed OOS Beta 3 over 4.7.6 on my 5T, wiped my cache, and everything was wonderful for a week. Then one day, I got a system message saying "Bluetooth has stopped". I cleared that and thought nothing of it, but I got another message saying "Bluetooth keeps stopping". This message would actually pop up (with no exaggeration) every second. I could only stop the messages completely after going to the Bluetooth app and clearing the data, then disabling Bluetooth Scanning.
I figured the problem would fix itself, but the next day when I tried to connect to my car via Bluetooth, my phone would freak out again like the previous day. I had to listen to a CD like it was 1996. I thought I could fix the problem with a Factory Reset. As soon as I hit the Welcome screen, "Bluetooth has stopped". When I went to check the Storage section of the Bluetooth app in the Applications list, the app portion read 0 bytes. What? Even when I went into Settings --> Bluetooth and tried to turn it on, nothing would happen. I thought maybe I should revert back to 4.7.4 and start from the very beginning.
That served no purpose. The Bluetooth symbol did show temporarily in the Status bar as I was setting up my phone, but eventually disappeared, with the Bluetooth app once again taking up a whopping 0 bytes. I've done various combinations of installs, but I cannot get Bluetooth to function normally. And at some point, my phone developed a new problem: any time I hit the Bluetooth button in Quick Settings, the phone would eventually reboot on its own. Later, it wouldn't need any input from me at all. It would just be sitting in the Lock screen and reboot.
Icing on the cake: I got desperate, unlocked the bootloader, deleted the system and cache partition in fastboot, then wiped the data in Recovery with the hope that doing a completely fresh install would fix the problem, but at some point my internal storage got wiped and now I have no ROM on my phone to install. Even better: I'm having some real problems trying to install OOS (any version) on my phone via ADB sideload. I keep getting the message "cannot read <filename.zip>", even though it's in the correct folder.
I am currently back on my OnePlus 3 and the proud owner of a very sleek brick. I used to root and unlock Nexus devices and Moto X's, so I'm pretty embarrassed that I managed to ruin my phone while it was running (basically) all stock. It can still boot into Bootloader and stock Recovery. Is there anything at all that I can do to at least load OOS (or any ROM)? Do I have to send it back to OnePlus and beg for a replacement? Will they even take this phone in it's current state? Am I just SOL?
I've run out of ideas and patience. I'm really hoping someone out there can help me. At the very least, thanks for reading my long sob story. Hopefully this never happens to you.
try flash orero based twrp and flahs stock 5.0.3 zip in twrp, see if it works. then figure out the reset.
Why would you delete system from fastboot? Does people not formating partition from recovery more often？
The twrp I use
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673
Update: I managed to unbrick my phone using an unbrick tool. The process was pretty painless and it will revert your 5T back to OOS 4.7.4 no matter what you did to it. Props to Drasm19 from the OnePlus forums and the geniuses behind this tool! Funnily enough, I was ultimately led back here:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
You guys more than likely already knew about this tool, but definitely keep this in mind if you manage to brick your phone like I did.
Now I'm back to my original problem: Bluetooth is really messed up. This is what I'm talking about:
https://imgur.com/gallery/eEkbX
No matter what I do, no matter how many times I flash any version of OOS, this is always the result. As you can see, even with the toggle in the "on" position, Bluetooth refuses to do what it's supposed to do and the app takes up 0 bytes. Something is up...
I've searched a lot of threads that reference Bluetooth issues, but it looks like I'm the only one with this problem. I'm open to any and all suggestions that'll help me solve this and get back to using my 5T. I already miss those awesome navigation gestures.
Thanks again for your time and help.
im not really a developer type, but a while back it was easy to root and un root with kingo. and i could put things in the system with FX. please bare with me a sec.. p9's i like, but getting some glitches. when the gboard went byby, on reset, i had to set up my welcome screen by shouting at the phone.. 'at sign' does give you @ but to get capitals you have to trick it, eg. 'USA' to get an upper case 'u'
anyway, i got in, and got gboard from 'my apps' ..fine but of course, wont survive another reset.
so about the missing bluetooth.. iv got the directory info. and the missing files. thanks ..but i didnt want to wipe the phone, it seems rooting has become a can of worms.
wouldnt it be nice if there was a nice (no root) app , to run bluetooth from the apps ? so that 'joe blow' doesnt have to throw his phone away, cos it doesnt work in the car ect.. thanks
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.