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.
Related
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
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.
about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
qazplokm said:
about a month ago I tried to change to a new ROM on my sgh-i717R model note which was already rooted running TWRP and a custom ROM that I had installed quite awhile ago. I did not realize that TWRP had to be updated to a newer version to use the 4.4 ROMS and the update failed and bricked my phone. I managed to fix it and put back a stock Rogers 2.3.6 ROM and it put back the original samsung recovery. The problem now besides being on an old ROM there is a lot of input lag using on screen keyboard, so I want to try a new custom ROM to see if it fixes things, but when I try to flash a new recovery with Odin (TWRP 2.8.0.0), Odin tells me that everything is good and it passes, but when I then reboot my device and go into recovery mode afterwards, it is the same samsung recovery mode with only the custom binary download counter incremented, but TWRP is nowhere to be found... I have tried with several versions of TWRP and it is the same thing.
Click to expand...
Click to collapse
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
You may have lost root when you went back to GB
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
qazplokm said:
yeah it was unrooted, but you cannot root without putting the custom recovery first.. Anyways I solved the problem, for some reason TWRP does not work (even though I tried all the versions specified for quincyatt and sgh-i717) but I was able to put on CWM no problems and re-root with superuser from there.
Click to expand...
Click to collapse
I know this thread is a couple weeks old but I thought I'd add something that I have found that might help if someone else has this problem.
The only way I was able to install the new version of TWRP was to install the old one first while rooting the phone then download the new versions .zip and update it via TWRP. I was able to get the new version working that way and now I am able to flash any rom I want with no issues.
Hope this helps others.
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