Hello,
I have recently rooted my Razer Phone 2, and tried to undo the root so I could update my phone. I went about it the wrong way, and now my phone is stuck in a boot loop and displays the message Your phone is corrupt and can't be trusted. Something like that. I tried to reset my phone data via bootloader, and that's where I believe I went wrong. I used Magisk when I was rooted. It is a Cheryl2 also.
I'm really stuck and don't know what to do. Could really use some help. I've tried flashing to MR0 8.1, but it doesn't look like it helped at all.
Nevermind, issue was fixed. Not sure how to delete this tread though.
Relock the flash critical.
Related
I've tryed to root the tattoo with superoneclick but it failed to root, since and the end came across some supposely memory errors and when when I boot into system its all apparently the same. I guessed it hadn't done anything so I jumped to the method as described on http://forum.xda-developers.com/showpost.php?p=5835675&postcount=1
I even done the gold card. And tried it. it does some command lines with no errors and at the end it boots normally. The problem is when I try to go to recovery mode it doesn't go to it and when I try to go to normal stock boot loader it algo fails. It tries to enter, I even see the screen for some part of a second but it just doesn't enters.
It boots aparently with no errors into to the system, but somehow somethings seem not work properly like factory reset and screen callibration.
It seems I've got stuck between halfway to nothing.
I just wanted some 2.3.3 goodness to my haunt and I'm afraid I've just messed up her phone!
Any smart and easy solutions? Even back to full stock would be good!
Thanks in advanced!
you can allways (well, as long as its not completely bricked) flash a RUU to go back to stock rom.
for me first time rooting also failed (dont remember the errors exactly), then i installed the RUU, tried rooting again and it worked.
Tattoo RUUs: http://shipped-roms.com/shipped/Click/
potattoo said:
you can allways (well, as long as its not completely bricked) flash a RUU to go back to stock rom.
for me first time rooting also failed (dont remember the errors exactly), then i installed the RUU, tried rooting again and it worked.
Tattoo RUUs: http://shipped-roms.com/shipped/Click/
Click to expand...
Click to collapse
Thanks!
I thought that could be a solution! I promissed I've been trying to resolve this situation for about 4 days. And I did it!!!
Everytime I ran a root solution it said it failed but they also said it was rooted.
tried again using this app:
http://forum.xda-developers.com/showthread.php?t=761507
Used the CM7 recovery (http://forum.xda-developers.com/showthread.php?t=854152) with described method: http://forum.xda-developers.com/showpost.php?p=9192029&postcount=21
i thought the problem could be not the rooting part but the flashing of the recovery.
Did it step by step and worked!
Thank you very much for your reply!
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
Hello, i have been researching for this issue that i have for over a month now, and yet i haven't found any solution or even a clue on how to fix it, and im sure lots of people are having the same issue that im having, let me explain what exactly happened to my phone and what i exactly tried
i was running on 5.0.1 G920TUVU1AOCG, and at that time "Ping Pong Root" was not yet available, so the only way to root the phone was to flash the "g920t_of6_aou_kernel_v1.tar" witch i did and installed SU using "g925t_of6_aou_twrp_recovery_v13.tar" and the phone worked perfect after that, and after the 5.1.1 lollipop came out, i decided to upgrade to that, so i flashed stock 5.1.1 odin firmware and flash the custom kernel "g920t_of6_aou_kernel_v1.tar" to get it out the bootloop since it was flashed previously on it, it worked and booted up and all seemed to be fine, i also wanted to perform a factory reset, and here is where the PROBLEM started, i forgot to turn on OEM Unlocking in Dev options, so after the factory reset, the phone got stuck on the bootloop "Samsung galaxy s6; powered by android" and the only way to make it bypass this bootloop is by flashing the "g920t_of6_aou_kernel_v1.tar" again, but i cant flash that because i forgot to turn on the OEM Unlocking in the dev options, and every time i try for flash any custom recovery or custom kernel and will give me "Custom Binary (BOOT) blocked by FRP Lock", so now im stuck on the bootloop, i cant access the phone to turn on the OEM Unlocking, Phone is basically STUCK.
I have tried flashing all stock firmwares that are, i have tried flashing all available kernels, i have tried Factory resetting the phone and wiping the catch, i have tried every guide on XDA and nothing ever worked for me.
i apologize for the long explanation, but i just dont want people to think that i am repeating the same question over and over since a similar question was asked by other members on XDA previously.
Thank you very much for taking the time and reading my question.
Do you still have recovery mode?
EDIT: In this thread: http://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-t3152054 every person that had the problem fixed it by flashing the stock firmware. make sure you're flashing the stock firmware that's the exact same as the firmware when your phone worked. So if you were on OI1 for example, you have to flash OI1 firmware or it wouldn't work. Try a couple times too, I've heard ODIN can be wonky sometimes.
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
ameenz77 said:
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
Click to expand...
Click to collapse
Try to factory reset in recovery and flash the tar trough ODIN again. If that doesn't work, try to restore it with SmartSwitch. A lot of people have success restoring their phone that way. If that doesn't work then I don't know.
Hi, i'm kinda new to all of this, so literally any help is appreciated.
I recently rooted my S6, and managed to get it stuck in a boot loop on the Samsung screen, with the logo in the centre, slowly fading from light to dark repeatedly.
This happened when i accidentally logged out of my snapchat, causing it to detect my device was rooted and wouldn't let me log back in. I got around this by updating my superSU and disabling it as i logged into my snapchat. Once i was back into my snapchat i went to re enable superSU, but it failed the reinstall and prompted me to reboot, so i did, then ended up getting stuck at the boot screen for the past 3 hours.
I don't know if what i tried was right, or even helped or made the problem worse.
I have tried reinstalling the custom kernel, re flashing the superSU through recovery, using ODIN to flash the original OS but each time i tried it failed, i might be using the wrong firmware, not sure, but i have a SG920F and installed the firmware for that, but it failed when doing so. I also never had the chance to create a back up as my phone didn't have enough storage to do so... It's at the point where im happy to factory reset im just not sure what to do.
I'm genuinely sad that i messed this up, and managed to brick my phone already. If anyone can help please reply to this...
Thanks.
theBoyAnt said:
Hi, i'm kinda new to all of this, so literally any help is appreciated.
I recently rooted my S6, and managed to get it stuck in a boot loop on the Samsung screen, with the logo in the centre, slowly fading from light to dark repeatedly.
This happened when i accidentally logged out of my snapchat, causing it to detect my device was rooted and wouldn't let me log back in. I got around this by updating my superSU and disabling it as i logged into my snapchat. Once i was back into my snapchat i went to re enable superSU, but it failed the reinstall and prompted me to reboot, so i did, then ended up getting stuck at the boot screen for the past 3 hours.
I don't know if what i tried was right, or even helped or made the problem worse.
I have tried reinstalling the custom kernel, re flashing the superSU through recovery, using ODIN to flash the original OS but each time i tried it failed, i might be using the wrong firmware, not sure, but i have a SG920F and installed the firmware for that, but it failed when doing so. I also never had the chance to create a back up as my phone didn't have enough storage to do so... It's at the point where im happy to factory reset im just not sure what to do.
I'm genuinely sad that i messed this up, and managed to brick my phone already. If anyone can help please reply to this...
Thanks.
Click to expand...
Click to collapse
I think it should be fixable. Firmware should be available at sammobile.com
RealWelder said:
I think it should be fixable. Firmware should be available at sammobile.com
Click to expand...
Click to collapse
Ah! Didn't know this! Thanks, will download it now and use odin to get it back on my phone, will update here if it works or not!
I have update my rooted OP 3T by flashing the complete rom through TWRP.. But the problem is whenever I flash the Supersu version : SuperSU-v2.79-201612051815 or SR3-SuperSU-v2.79-SR3-20170114223742, I am getting bootloop.
Please anyone advise me.
I checked that without flashing SuperSU phone is able to Boot safely.
Thank you in advance.
It's normal if it bootloops once or twice
But if it's more than that then it's problematic
So which one is it
Another thing you can try is try magisk root instead of supersu and see if gets the same result
Phone was stucked in bootloop for an hour without any reboot.
I am not fond of magisk yet... So dont have any plan for it.
Just want to know if this happens to only me or there are many others with same issue.
Edit:
Finally installed Magisk for root... Issue closed.
help!?
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
plzz can anyone help me
amber sachdeva said:
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
Click to expand...
Click to collapse
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
redpoint73 said:
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
Click to expand...
Click to collapse
well i tried unlocking bootloader but it says failed (remote: oem unlock not allowed)
Iam i stuck here for ever ?
can u tell me the command that i can try on an phone with a locked bootloader
I forgot this is an edit the first time Gentlemen, I am absolutely at wit's end now I am no geek with a capital G however I have been modifying phones for some 3 years now and I can't even tell you how many times I flashed ROMs my beloved 3T 3T has had been acting glitchy lately like when I would reboot the circle that turns - instead of just turning evenly it would twitch, it was such a small thing I ignored it but I think now that that's must be have been indication something was not right few other things like that. I flashed the Freedom ROM cuz I'm so sick a Google and Google Assistant when I came out I was in a bootloop so I wiped everything except OTG everything and formatted data did the ROM Flash again the a boot Loop still abides and I've done it a dozen times now sometimes a couple of times it it just it kept recycling the bootloop another time and got hung up on the OnePlus it just sat there on the logo and if I miss something obvious I do apologize I'm tired and I'm at wits end because I'm not used to not being able to solve my own problems I guess so any help at all or just even a heading in the right direction would be so much appreciated that I don't even know how to call it quantify it thank you
By the way I seldom post or even post questions but when I do I always pretty much say the same thing you guys are the best this is the one place I can come for Andrew Android advice or or guidance and I just I absolutely trust what I read so thank you thank you thank you thanks for being there
Edit - I'm so tired I forgot the first time I went to reflash the ROM it told me that my 3T was in fact not a 3T that it was a three and I read someplace so I'm XDA that that's just Corruption of the install script so I downloaded it again I ran 7-Zip it said it was coherent so I flash it again if that's important but thanks again
Help required
kunal1540 said:
it's normal if it bootloops once or twice
but if it's more than that then it's problematic
so which one is it
another thing you can try is try magisk root instead of supersu and see if gets the same result
Click to expand...
Click to collapse
sir, i have oneplus 3t a3010. Last night my phone was crashed and after crashing it restarts and jumps to recovery mode. In recovery mode i wipe all data and restart my phone. But i still doing the restart thing. Please help, what to do now.
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
My oneplus 3 is stuck in recovery mode
My bootloader is locked
Everytime i switch on my phone there is a message
Which is on photo below