I was trying to remove FRP on an old company phone and have successfully done it, but I can't seem to flash a stock rom or anything. I have tried installing safestrap but to no avail and every time I reboot, no matter what I've flashed in odin, it goes back to the same screens like in image 8 of this guide https://www.samsungsfour.com/tutori...y-smartphone-using-combination-firmware.html#
I have tried using this guide https://forum.xda-developers.com/galaxy-s8/development/rom-t4063873
to flash another rom and tried to install safestrap using this guide https://forum.xda-developers.com/galaxy-s8/development/root-t4060701 and this guide https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206 but every time it reboots or is supposed to go into safestrap, it just reboots into the factory binaries. Help?
It's a 950U
Wdswds said:
I was trying to remove FRP on an old company phone and have successfully done it, but I can't seem to flash a stock rom or anything. I have tried installing safestrap but to no avail and every time I reboot, no matter what I've flashed in odin, it goes back to the same screens like in image 8 of this guide https://www.samsungsfour.com/tutori...y-smartphone-using-combination-firmware.html#
I have tried using this guide https://forum.xda-developers.com/galaxy-s8/development/rom-t4063873
to flash another rom and tried to install safestrap using this guide https://forum.xda-developers.com/galaxy-s8/development/root-t4060701 and this guide https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206 but every time it reboots or is supposed to go into safestrap, it just reboots into the factory binaries. Help?
It's a 950U
Click to expand...
Click to collapse
Which rom did you try to flash from factory binary? Which factory binary rom you flash originally? I had same issue on a different phone and I had to keep flashing various stock roms til they stuck.
And why are you trying to install safe strap? The g950u cannot be rooted in certain bootloader revisions...but yes it is possible on a certain bootloader version...which stock roms? Need more info dude
Related
While I did find a similar posts, they were for different devices. I also tryed to search o different sites for similar problems to no avial.
What Happened: After backing up system data and app data then removing Foxhound ROM with factory reset, and installing UltimaROM i came to find that the modem did not install correctly result in no connection to my cell network. I booted into TWRP recovery to try and do a re-install of the ROM only to find that TWRP was restarting itself every 3 seconds or so. I attempted to restart the device which i found to result in a TWRP bootloop that i cannot get out of, it constantly is booting into recovery mode and i cannot get it restart the OS.
What I've tried: Since i can get into download mode i decided to attempt to re-install TWRP using Samsung Galaxy S3 Toolkit but since i do not have USB debugging on i cannot do that. I'm mainly looking for a fix before i go and claim it on the warranty saying update went bad or something. If people need more information I will try to provide it as best i can.
Summery if i confused people is that TWRP is in a bootloop, i am unable to get to the OS, but i still have download mode available.
I fixed it but not how I would have liked to. I ended up losing all data due to flashing stock ROM using ODIN. I would still much appreciate a alternative method that does not involve loss of data though just for future reference, that is if anyone knows a alternative method.
Sent from my GT-I9300 using xda app-developers app
could've tried reflashing TWRP or any other recovery through odin
I have an LG Optimus Q (LGL55c) with twrp loop. I was trying to go back to stock rom, instead I deleted all the system files in twrp when it was working...Then I rebooted back into recovery and get the loop. Does this mean I completely bricked my phone? I tried using adb, adb shell doesn't work. It does find the device. Even tried the LG update with no sucess Any ideas or suggestions?
I just read the forum title, I thought this was for the Optimus Q not the Samsung S3. Sorry mods
Temasek unofficial cm12 5.02
I was running this rom when my power button shorted and I got it replaced but then I tried to do a complete wipe and clean flash but since then it has been twrp bootlooping, tried to flash the latest recovery through Odin but still doesn't work also tried stock firmware flash but says binary not available.
This is my secondary device and I've not been in touch with Odin for a while. Any help will be appreciated.
Thanks
Download latest firnware from sammobile.com and flash it with Odin, as described on sammobile: does Odin finish with '1 succeeded'?
I'm in a very similar situation, but with my Samsung Galaxy Note 2 (N7105). It's rooted, and I am, or was using TWRP 2.7.0.2. ROM is CyanogenMod 12, 5.0.2 Lollipop.
I did a factory reset from INSIDE Android, and chose to wipe internal memory. Phone did the reset and wipe, rebooted into TWRP instead of Android, and now I have TWRP boot loop.
I posted more about it here: http://forum.xda-developers.com/showpost.php?p=60247503&postcount=3671
I have the Problem toooo!
What must i do Now!
with my S3 is the same!!!
For posterity:
With an old (2014?) version of TWRP and a custom ROM, I tried reverting to factory settings. That caused the phone to reboot TWRP, and the screen would flash every couple of seconds. I flashed a stock recovery image I found on Google, and when it restarted again, the wipe was completed successfully. My intention was to wipe all user data anyways so I can't say if this method might save it.
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
First, you should have done more research. You can't install a custom recovery on 4.3 (or MJ7). The only thing available is a "questionable" root method. No custom ROMs and no Safestrap.
Second, once an update has been applied, there is no way of going back.
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
If that doesn't work, try this one. http://forum.xda-developers.com/showthread.php?t=2507253.
Make sure you read ALL instructions first.
Good luck.
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
k1mu said:
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
Click to expand...
Click to collapse
Thanks! Knowing this, I think I will just stick with root but no recovery...hopefully, something will change and allow me to unstick myself from this situation in the future.
riker147 said:
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
Click to expand...
Click to collapse
This worked well when I had the same issue. I did lose root even with Survival Mode enabled on SuperSU, but otherwise no issues. Thank you.
So the way I rooted was I flashed CWM via Odin, and then flashed SuperSU zip in CWM. I used the correct versions and i verified I had root with Titanium Backup and even Root Checker. I have tried twice to flash roms and I end up in samsung logo boot loop, don't even get any further than that. I downloaded 2 different roms that are meant for the Sprint Note 3 and work on my build number. Perhaps my root method screwed it up some how? Any ideas what is happening? From reading other posts, I realize I may have to flash another kernel, but on the rom (MiniN3) it said nothing of the sort. So, what gives?
hobokenshmo said:
So the way I rooted was I flashed CWM via Odin, and then flashed SuperSU zip in CWM. I used the correct versions and i verified I had root with Titanium Backup and even Root Checker. I have tried twice to flash roms and I end up in samsung logo boot loop, don't even get any further than that. I downloaded 2 different roms that are meant for the Sprint Note 3 and work on my build number. Perhaps my root method screwed it up some how? Any ideas what is happening? From reading other posts, I realize I may have to flash another kernel, but on the rom (MiniN3) it said nothing of the sort. So, what gives?
Click to expand...
Click to collapse
what rom firmware where you be fore flashing the new rom? did you tried to wipe cache/date after flashing?
Well I restored back to factory 4.3 stock, then use another 4.3 custom rom.
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Cwm from rom manager hasn't worked in awhile. Use philz touch if you really want cwm. Or use flashify to get twrp
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
Like Josh said just use Flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify
It's still updated and works great. To many have had issues with ROM manager or Goo.
Sent from my SCH-I545 using Tapatalk
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
sdsurferbob said:
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
Click to expand...
Click to collapse
Thanks guys. I tried all of this with the flashify. Even started off freshly reinstalling stock Mdk and then rerooting with the same method I mentioned earlier. Installing cwm through flashify. And though I can make and restore a backup of my stock rooted Rom. I get the same errors I've been getting trying to flash a custom Rom. I'll try to post a screenshot of the error I get in can when flashing.
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.