Hey peoples,
Just wanted to say hey and thanks for all the hard work you obviously put into this phone, it is pretty amazing.
I have had the phone for about 2 weeks now.
It is my first Android based phone and my first smart phone.
I really want to be able to use tethering and so I have decided that it is worth it to me to root the phone and try my hand at making it work.
So, I have been reading for the last week, trying to digest all of the information and really trying to wrap my head around just how to do this the right way.
Here is what I have done, and how I have succeeded and failed.
I downloaded the following:
PC36IMG.zip
EVO-recovery.zip
and placed PC36IMG.zip in the root of my sd card.
Went through the motions and successfully flashed from within the bootloader of the Evo.
Rebooted as instructed.
Now, here is where I got lost, or really was unable to confirm if I was successful or not.
I extracted the EVO-recovery.zip file to a folder I called "evo".
I placed that folder in the root of my c drive.
I opened up a command prompt and typed "cd \evo" and confirmed I was in that directory.
From there I typed "adb reboot recovery" and hit enter.
Then, once that process started, I opened up the evo folder and double clicked "recovery-windows.bat".
The process seemed like it was doing what it should be doing, and once it was complete, I navigated to and created a NAND backup.
That is where I think I went horribly wrong, as once that was done, and I rebooted the phone, I was shocked to find that all of my contact data was gone, which was painful because I had spent the last 2 days getting that all sorted out and new numbers transferred from my old phone (manually).
Anyway, after the initial shock wore off, I started looking around and realized I now had a blank phone.
All of the sprint apps were still there and nothing seemed to have changed other than my phone was now void of everything that I had installed and added to it.
So, feeling like I had probably rooted the phone, but failed to back up at the right point in the exercise, I really had nothing to lose since I was going to have to add all that data again anyway.
That brings me to today.
After much reading, and poking around, I figured all I really had at this point was a rooted stock rom on my phone?
I could not find any super user app in my apps pane, nor any other indication that I had done anything in particular other than wiping my phone clean.
So, I then decided that I needed to install a custom rom.
That seemed like the logical next step.
So I downloaded "RvU_1.3.2.zip" from Android central.
I placed that file on my sd card, shut the phone down, and then powered it up while holding the volume down key.
I navigated to and flashed the file to the phone and was ultimately stuck in infinite (reboot) loop after the process was seemingly complete.
In a bit of a panic, I pulled the battery, and rebooted the phone with the volume key depressed, and from there I wiped the caches (delvic and cache) and reset to factory default within the same menu.
From there, I went in to restore mode and restored to the NAND back up I created.
Now I was back in the same spot prior to trying to flash the RvU_1.3.2.zip rom.
Feeling a bit deflated, I decided that I really needed to see if I could get the phone back to factory fresh stock condition and was successful using "RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe" which I downloaded from a link on this site.
So,
If you are still with me after this long winded post, and are even remotely interested in helping me figure out where I went wrong in the process, I would really appreciate any help you may offer.
At the end of the day, I would really like to root this baby, get a rom which has all of the Sprint crap ware deleted and ultimately be able to tether my laptop.
Is anyone interested in helping an old guy out?
Thanks in advance, this seems like a place with a hell of a lot of knowledge and skill.
I appreciate being here.
First off, your contacts should have been saved when you first created a google account when you got the EVO. After you completed part 1 of the root process, when you reboot your phone, you should gotten a prompt if you wanted to sign in to google. Since you are an existing customer, sign in, and within minutes, your contacts will show.
Second, it is highly recommended that you do part 2 of unlocking Nand protection so that you don't have to do extra steps to get into recovery mode and can get into it from within android.
Also, the blank phone that you saw was/is completely normal, since when you flashed the pc36img file, it ultimately erases all user data on the phone.
Ok, thanks Dave,
So, in your opinion, was I successful in rooting the phone?
And where did I fail in trying to get a custom rom installed?
Seems like you did it just fine. Try flashing the custom rom again if you'd like. Otherwise, go for the gold and do part 2 of unlocking nand protection.
-------------------------------------
Sent via the XDA Tapatalk App
Related
My rooted KF got bricked by the new OS update that was released last night. It boots as normal, gets to the locker screen, and whether you unlock it or not, reboots about 15 seconds later to a screen showing the Android guy and an exclamation point in a yellow triangle. Then, if you start touching the screen, 4 buttons will show up on the side, up/down, select, and back... but they do nothing. Reboot again and it takes me to TWRP.
I know how to wipe my KF and reinstall everything, but I was hoping that someone might know of a fix for this. Especially because I just got a new computer and am still in the process of getting my normal apps installed, let alone Android SDKs that I use once in a blue moon. Plus, I have a few games that I would rather not lose my progress on.
BTW, I rooted my dad's KF the exact same way as mine and his just lost root access with the update, everything else is fine. Kinda weird.
TIA
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S. You may also get lucky and be able to flash modaco if you`re on rooted stock or previously rooted stock 6.3.1 without wiping.
Thepooch said:
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S.
Click to expand...
Click to collapse
About 3am last night, I found my KF bricked after just using it about 30 minutes before (the wifi was on and it was hooked up to the charger). Today, I checked on my dad's KF and he has his wifi turned off. I turned it on and it instantly rebooted to just a "command line" screen saying that it was installing an update. Took about 10 minutes and then rebooted and worked fine, except that it was unrooted. I read somewhere in the Amazon Forums today that they did roll out an update and plan on spending 2 weeks doing it to keep from bogging down their network. Granted, their Software Update page doesn't say anything about it yet.
BTW, thanks for the other info, I'll have to check it out. Sounds like I'll have to wipe it (or at least restore from a 2-3 month old backup and see how the update goes again). But that's cool that I won't need to install the Android SDK.
Explains why some are instantly being unrooted or like in your case bricked strange thing is that it doesn`t change the system version it`s still 6.3.1 figures that Amazon would pull something like this.
Hey, I did manage to find a quick fix!
In the recovery mode, I decided to try using the Fix Permissions option. Still had the same problem.
I then just used the Clear Cache option and my KF was back up and running... and still rooted.
The only issue I have found so far is that I had to change the permission to allow changing the wallpaper, just uncheck the "write" permissions, (which was probably reset by the Fix Permissions option I ran). Other than that 2 second fix, everything is fine.
Granted, I'm waiting for Amazon to do an auto-check for some file that was in the cache that told it that it had installed the latest upgrade, and since I wiped that, it may install it again. If it does, I'll post it in this thread that my quick fix didn't work. But so far so good.
It turns out that my quick fix is only a temp fix.
Twice tonight I had to clear the cache again via the recovery menu. The first time it happened, I had just finished reading and hit the power button to put it in sleep mode, which caused it to instantly reboot and then do the same thing as I mentioned above. It boots up, and within 5 second of getting the locker screen, whether you unlock it or not, it starts shutting down and reboots ending up with the screen in the attached pic (those dots are just dust that appear super bright for some weird reason because you can't see them except in the pic).
So I cleared the cache again, everything was fine, and then about an hour later I found it sitting on that screen again. Clearing the cache fixed it again, but obvious this is a reoccurring problem.
Anyone have any ideas?
I'm reluctant to do a reinstall yet because I'm afraid I'll just end up with the same problem... along with none of my apps installed.
I have the same issue my temp solution is turn off wifi asap after lock-screen appear, wait abt 1-2 minutes then I can turn on wifi and use as normal.
Everything will fine for few hours. Any permanent solution plz? I remember that it occurred after i update something from Amazon app store, maybe : apps...
Sent from my Kindle Fire using xda premium
The permanent solution is to flash another rom preferably modaco if you want the stock experience. Full wipe, your apps can all be redownloaded that is the least of your worries at this point. probably a really good time to upgrade your bootloader and recovery if you haven`t flash both of these zips as zips in twrp if are behind the curve http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 and http://forum.xda-developers.com/showthread.php?t=1632375 only get them from where I`m directing you or use smirkit http://forum.xda-developers.com/showthread.php?t=1500935.
thanks for your help. This is done with the below solution
1) Copy the update bin file to the /sdcard as update.zip
Download stock ROM : https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.1_D01E_4107920.bin
copy update-kindle-6.3.1_D01E_4107920.bin into Kindle Fire and re-name to update.zip
2) From the main menu of CWM, "Wipe cache from partion" to remove the existing files in the data and cache partitions
3) From the main menu of CWM, press the "Install update.zip" button to flash the stock software onto your device.
no data/application lost accept FFF and CWM
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Thanks for the info guys.
Considering the post in the Amazon Forums said this update was being pushed out over a 2 week period, I'm just going to keep my WiFi off (unless needed) and wait until everyone should have received the update and then see how it plays out. Considering it doesn't change the software version number, I'm thinking that this update may be just targeting rooted Fires. And BTW, it appears that the post was removed, because I can't find it again. Maybe they remove any that mention rooting? I just stumbled upon it via a Google search... 99% of the question in their forum are just idiotic.
Directv used to pull this stunt all the time to bust people with hacked cards that allowed them to get all their channels for free (usually a few hours before some big PPV event). They finally completely stopped the ability to hack cards by rolling out parts of their code over a long period of time, a year or so. When the final piece was put in place, the previous parts of their code had already been integrated into the hacked card software, because it appeared safe, and along with upgrading the type of cards they used during that same period of time, pretty much eliminated the ability to cheat Directv. I'm not saying that Amazon is going to those lengths to stop people from rooting their KFs,.. but who knows? It may be costing them too much with people bricking their KFs by trying to root them. Plus, they may also be losing revenue by people getting their free apps (with ads) from the Playstore instead of Amazon. And considering they pretty much sell their Fires for cost, they definitely rely on revenue generated by buying and using things via a stock KF.
BTW, this whole issue had almost perfect timing... I was planning on wiping my KF because it definitely is slower than when I first got it (which was day 1 of its release). I've read that Gingerbread doesn't clean up after itself too well, especially not as good as ICS (kinda like a Windows registry just gets filled with junk over time, and no cleaner beats a fresh install). It also appears that the ICS roms are actually working reliably these days, compared to the last time I checked. So, in a couple weeks, I'll get to have some fun. I am a Windows/Cisco System Engineer, so this kinda stuff is fun for me.
F.Y.I.
It seems that Amazon did do a incremental update on the Original Kindle Fire version
6.3.1_user_4107720, April 30 build to 6.3.1_user_4107920, November 27 build.
I looked thru the update and the only things I found changed are to do with the
Wifi driver, launcher icons, boot animation, and boot.img; attached the changed file below.
I have not tried to update mine, will attempt this weekend.
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Thepooch said:
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Click to expand...
Click to collapse
It seems they increased the resolution of the images in the file, but for me I can not see the difference.
For me I wonder what they changed in the WiFi driver file, tiap_drv.ko.
Kindle Fire Reboot Problem Solved - Install MoDaCo Rom
Thepooch said:
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Click to expand...
Click to collapse
I took Thepooch's advice and installed MoDaCo rom on my KF. It was a snap. I had FireFireFire installed with TWRP. Just downloaded MoDaCo to PC copied to KF. Rebooted to FireFireFire Installed with Install Zip utility. Took a few minutes. Rebooted didn't loose any data , apps or functionality. Its still rooted. THANKS!
No problem you can find the entire uncomplicated method here http://forum.xda-developers.com/showthread.php?t=1923010 or at least a synopsis of the concept.
So I did something I knew better than to do, but after weeks of dealing with it, got annoyed and accepted it. There was a system update that came through a few weeks ago, pops up every ten minutes or so. Rooted and Freegee'd so I figured it was not in my best interest to accept this update. I tried to freeze it with Titanium, but that program for some reason constantly failed to load things, froze up, etc., even after reinstalls. Well, today, I decided to be dumb and said hell, let's see what happens. Hit "install now", phone rebooted into CWM, CWM asks if I wanted to accept this update, I said yes, gave me the broken android with the red triangle with a ! in the middle and said it failed. I selected reboot system now, it will only boot into recovery. I have two backups, neither of which CWM will load...ridiculous. Says MD5 mismatch, no idea what that means. Regardless, backups don't work. So, my question now is can I simply do a data wipe/factory reset or must I do an LGNPST? Also, will a data wipe/factory reset remove root and CWM? Because currently I have no reason for my phone to be rooted and unlocked, and CWM doesn't seem to function correctly anyways for me. I need a quick response please!
Look in general, there is a thread on how to recover from such things.
Cool. I'll see if I can figure it out. Thanks Chad.
Unbricked. It removed root and unlock, which from what I was reading, I didn't think it would do. Is it safe to update now? lol.
Hello,
My Ascend P1 seems to be soft-bricked, the phone turns on and I can access CWM Recovery... or so it seems. It all started when my phone's battery died and right after that, I put it to charge and left it alone for around 4 hours. When I came back, it hadn't charged at all, I tried to turn it on and it would get past the Huawei Logo and pass to the LiquidSmooth ROM launcher screen, however, it would just freeze and restart the phone. It fell in what I heard is called a bootloop.
I did some research here and there and found a lot of tutorials about how everything is done from the scratch. I did the basics, clear cache, dalvik-cache, factory-reset, etc, but when I tried to install the ROM from the SDCard, the installation finishes way too fast (15 seconds at most), almost as if it did nothing (which I believe it's true).
I also tried to install a new recovery through a tool called Shaume, it seemed to be working at first; I installed it (which took probably like 3 seconds to install), it launched the "new recovery" and everything about seemed to work just fine, however, when I first did this I had forgotten to put the ROM in my SD Card so I took it out, put the ROM in it and to make sure, I restarted the phone. After it restarted, it went back to the old CWM I had installed (this one has no touchscreen features) and it seemed as if everything I had done was for naught.
I just don't know what to do anymore. I tried to take a look at the logs after trying to format /data, /cache and such, and the most notable thing I saw there was "rm: can't remove '/data/dalvik-cache/' read-only file system", this same "read-only" happened referring to some of the applications I had installed before.
I am no expert in this matter, as I myself have never even rooted/flashed ROMs (the phone was already rooted/flashed when I got it). At least, through all of the research I've done it seems that as long as the phone is able to get to the Recovery, it's not something that cannot be fixed.
I really hope you can help me fix this.
Thanks in advance!
I'd try to Flash Stock firmware before trying again.
I am requesting to have this thread move to the right forum so that the right experts may be of help.
Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.
I like some solution?
SairoJ said:
Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.
Click to expand...
Click to collapse
I tried with all tutorials and I have not accomplished anything
(Not sure this is the best thread for this - I'm new here)
I'm afraid I may have really hosed my HTC ONE M9.... I seem to have half-a-phone right now. I took my own "crash course" the past couple of weeks reading everything I could find on custom ROMs and how to install. I thought I jumped through all the hoops. I signed up on HTCDEV.COM and unlocked the bootloader. After several false starts, I tried to install "HD Revolution" first, but that left me with nothing but a bootloader when I turned the phone on.I finally got CANDYSIX to install. All but one version of GAPPS errored out and wouldn't install. I did finally get one to install (or at least it said it did) from TWRP but I have NO Google apps whatsoever. I'm really confused now. If I had money to burn I think I'd buy a new HTC and start over. Is there any hope? I almost wish I could go back to "factory new" but I'm not understanding a lot of that. Another strange thing is that I no longer can access the phone from my PC - it shows the name of the phone in My PC but when I select it, there is no files - nothing.. It doesn't even show the SD card. And all of that worked fine yesterday before my problems with "Revolution"
Any idea? Is there any hope at all? Anything would be much appreciated.! I really can't afford another phone but it may come to that
xfoneguy said:
(Not sure this is the best thread for this - I'm new here)
I'm afraid I may have really hosed my HTC ONE M9.... I seem to have half-a-phone right now. I took my own "crash course" the past couple of weeks reading everything I could find on custom ROMs and how to install. I thought I jumped through all the hoops. I signed up on HTCDEV.COM and unlocked the bootloader. After several false starts, I tried to install "HD Revolution" first, but that left me with nothing but a bootloader when I turned the phone on.I finally got CANDYSIX to install. All but one version of GAPPS errored out and wouldn't install. I did finally get one to install (or at least it said it did) from TWRP but I have NO Google apps whatsoever. I'm really confused now. If I had money to burn I think I'd buy a new HTC and start over. Is there any hope? I almost wish I could go back to "factory new" but I'm not understanding a lot of that. Another strange thing is that I no longer can access the phone from my PC - it shows the name of the phone in My PC but when I select it, there is no files - nothing.. It doesn't even show the SD card. And all of that worked fine yesterday before my problems with "Revolution"
Any idea? Is there any hope at all? Anything would be much appreciated.! I really can't afford another phone but it may come to that
Click to expand...
Click to collapse
With all the reading you did, I'm sure you made a backup before you flashed anything. Just restore your back up
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.