warning: booting into recovery - T-Mobile Galaxy Note 4 General

I tried booting into recovery via quickboot and now I"m in a boot loop. Battery pull just starts the process again -- phone trying to go into recovery but does so unsuccessfully.
I guess i have to odin back to stock and start over. argh just restored everything perfectly, xposed and everything.

samklee said:
I tried booting into recovery via quickboot and now I"m in a boot loop. Battery pull just starts the process again -- phone trying to go into recovery but does so unsuccessfully.
I guess i have to odin back to stock and start over. argh just restored everything perfectly, xposed and everything.
Click to expand...
Click to collapse
Same happened to me, but flashing stock firmware using odin kept everything intact. Didn't have to start over again. But I did have to flash root again.

Yeah I just downloaded the new Firmware to Odin and tried to boot into recovery using the button method to wipe data before Odining - didn't work. Booted back did a factory reset via the menu options and the phone tried to reboot into recovery, the phone restarted and just flashed the android icon but wouldn't boot into recovery to wipe data.
Just now I flashed the new Firmware via Odin and it of course dirty flashed. Once the phone was completely booted up. I shut it down properly. Then booted into recovery using the button method and that worked. Wiped all and starting fresh.

What were you all doing when this happen? all rooted i presume? so are you saying if you are rooted you can't go into recovery without going through bootloops? someone please clarify

re: reboot recovery
glensta said:
Yeah I just downloaded the new Firmware to Odin and tried to boot into recovery using the button method to wipe data before Odining - didn't work. Booted back did a factory reset via the menu options and the phone tried to reboot into recovery, the phone restarted and just flashed the android icon but wouldn't boot into recovery to wipe data.
Just now I flashed the new Firmware via Odin and it of course dirty flashed. Once the phone was completely booted up. I shut it down properly. Then booted into recovery using the button method and that worked. Wiped all and starting fresh.
Click to expand...
Click to collapse
I don't know what to say, my phone was rooted so I had to I odin flash cf-autoroot
again to regain root after odin flashing the new firmware from Sammobile.com
but I had no issues or problems going into recovery, bootlooping or getting stuck
when trying to reboot or boot into recovery.
For me it was the same old same old, odin flash new firmware, odin flash cf-autoroot
to gain root access, check everything out including reboot to recovery & reboot into
download mode... No different than what I always did using the Note 3 phone.
Good luck!

This is what happens after I rooted (mind you I forgot to check prior to root if booting to recovery works. and tried to boot into stock recovery - watch video:
Pulled batter, reinstalled and phone starts up just fine though, no bootloop
https://www.dropbox.com/s/yy149do5f0b5ggc/Note 4 Recovery Issue.mp4?dl=0

mgbotoe said:
What were you all doing when this happen? all rooted i presume? so are you saying if you are rooted you can't go into recovery without going through bootloops? someone please clarify
Click to expand...
Click to collapse
They trying to find a magical recovery when none exist.
NOTE 4

BACARDILIMON said:
They trying to find a magical recovery when none exist.
NOTE 4
Click to expand...
Click to collapse
Well there is stock recovery

mgbotoe said:
Well there is stock recovery
Click to expand...
Click to collapse
Yeah but they looking for cwm or twrp features
NOTE 4

re: custom recovery
BACARDILIMON said:
Yeah but they looking for cwm or twrp features
NOTE 4
Click to expand...
Click to collapse
There has been a lot of chat going on today in the twrp irc channel
about custom recovery for the Note 4 N910T and they are getting
closer to finding a solution..
In fact it looks like bigbiff, koush and philz are having a race to see
who develops a N910T custom recovery first. LOL

Misterjunky said:
There has been a lot of chat going on today in the twrp irc channel
about custom recovery for the Note 4 N910T and they are getting
closer to finding a solution..
In fact it looks like bigbiff, koush and philz are having a race to see
who develops a N910T custom recovery first. LOL
Click to expand...
Click to collapse
Last I read philz gave up on doing cwm. I hope he had a change of heart. I dunno koush.
NOTE 4

Yep don't go onto recovery or u will bootloop
Sent from my SM-N910T using XDA Free mobile app

re: bootloop going into recovery
raw2000j said:
Yep don't go onto recovery or u will bootloop
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
What's all this about not going into recovery because of bootloops?
I never seen any such thing, the original firmware with or without
root the phone never bootlooped when I went into recovery.
The same holds true for the new updated firmware, it never goes
into bootloops either when I go into recovery rooted or not.
In fact I never yet seen my note 4 going into any bootloops for any reason.
Hmmm.. I must be doing something wrong! LOL

mgbotoe said:
What were you all doing when this happen? all rooted i presume? so are you saying if you are rooted you can't go into recovery without going through bootloops? someone please clarify
Click to expand...
Click to collapse
In my case, I was just being experimental and wanted to see what happens if I delete every file that had to do with Knox. It ended up boot looping. I guess cause it couldn't find Knox when booting

Are you guys that are getting bootloops when going into recovery using the 4 way mod in wanam. If so, then i recommend not trying to access it thru 4 way reboot. Do it the old fashion way till wanam fixes the files need to do that. I know that if you try thru 4 way you get bootloop so you will have to odin back and start over. This time dont use 4 way reboot. Iam sure someone will come out with a fix.

Misterjunky said:
What's all this about not going into recovery because of bootloops?
I never seen any such thing, the original firmware with or without
root the phone never bootlooped when I went into recovery.
The same holds true for the new updated firmware, it never goes
into bootloops either when I go into recovery rooted or not.
In fact I never yet seen my note 4 going into any bootloops for any reason.
Hmmm.. I must be doing something wrong! LOL
Click to expand...
Click to collapse
Must be cause I wanted to go to stock recovery and hit recovery on quick boot I didnt shut it down to press buttons guess trying to go to recovery that way messed it up

Power down phone. Volume up + Home + Power will get you into stock recovery on a rooted Note 4. Just did it no problem.

BACARDILIMON said:
They trying to find a magical recovery when none exist.
NOTE 4
Click to expand...
Click to collapse
Lmao...
Sent from my SM-N910T

Related

[Q] Problems with stock rooted rom when flashed from recovery.

Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.
Anyone? Please?
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.
What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.
My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium
Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium
Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.

[Q] Triangle of death, recovery and rom

Hello,
After successfully rooting my S4 and installing 4.3.3 I wound up screwing things up and now have the yellow triangle of death when I try to get back into recovery or boot the rom.
The only thing I seem to be able to do successfully now is get back to download mode.
Trying to flash a new recovery via odin results in a nand write failure. I've tried philz, clockwork and twrp, all do the same thing.
Since I can't boot the rom there's no way to use an adb based utility like casual, which is what I had used to originally root.
From what I can find it doesn't appear there are any odin flashable versions of the loki utility.
Any help with ideas on what to try next appreciated.
Thanks for any help
Update: I've been spending my time in the samsung galaxy s4 forum, just now realized there was an att specific sub forum which explains why I ended up using non loki'fied roms. Still stuck, still need help. Thanks in advance.
If you can get into download, then just flash the stock ROM via Odin and start over again.
CZ Eddie said:
If you can get into download, then just flash the stock ROM via Odin and start over again.
Click to expand...
Click to collapse
Flashed stock rom successfully via odin however now it doesn't boot
Stuck on the AT&T logo
Any other ideas?
tr2ride said:
Flashed stock rom successfully via odin however now it doesn't boot
Stuck on the AT&T logo
Any other ideas?
Click to expand...
Click to collapse
If you can't get into recovery at all, and you can't use Odin or Kies to restore with, I would say you are looking at needing Jtag.
I would try every known key combination and methods to get into recovery first though several times. It can be tricky.
tr2ride said:
Flashed stock rom successfully via odin however now it doesn't boot
Stuck on the AT&T logo
Any other ideas?
Click to expand...
Click to collapse
Need to boot into stock android recovery and wipe cache and it will boot up.
Sent from my SGH-I337 using Tapatalk 2
ripper4209 said:
Need to boot into stock android recovery and wipe cache and it will boot up.
Sent from my SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
ended up having to wipe data and cache in stock recovery ... but then it did boot up .... thanks!

Major Problem using TWRP

Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
doesntmatterx said:
Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
doesntmatterx said:
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
Click to expand...
Click to collapse
:good:
xBeerdroiDx said:
:good:
Click to expand...
Click to collapse
I take it back, stuck in a boot loop even after 2 fresh ODIN unroot tasks. Nothing I do gets me out of this, been a long day getting longer now
Can anyone help? Been at it for hours, I have tried everything, phone still reboots at the Samsung logo (the bluish one )
Unrooted 3 times
Launched stock recovery, wiped factory reset
wiped partition cache
removed battery
Cannot connect to Kies for Emergency restore.
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
seanpr123 said:
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
Click to expand...
Click to collapse
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
doesntmatterx said:
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
Click to expand...
Click to collapse
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Should I ODIN with the RE-Partition Option?
Just Odined again and no dice. I booted into stock recovery and noticed after wiping factory I get "Can't open /efs/log/boot_cause" which pointed me to this fix someone on the Galaxy note forum said they did and it worked but I dont understand the steps, need some elaboration.
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
jd1639 said:
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Click to expand...
Click to collapse
Yep did that mulitple times, also did wipe cache partition in the same stock recovery. I get to the Samsung logo where the blue halo spins around the name, then it freezes there and reboots.
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
seanpr123 said:
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
Click to expand...
Click to collapse
LOL thanks, yes I may have to do that. I had a backup and it was wiped.
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Try flashing using cwm. It'll probably work fine. Then you can go back to twrp. That's worked on other devices. Seems one you flash it once with cwm then twrp works from that point forward. Idk why
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
jds3118 said:
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I tried flashing with a PIT file I found online but it fails through ODIN everytime. I tried on multiple versions of ODIN as well. I also cant seem to find readily available PIT files to test as well, (perhaps the one I used does not work). Also I did try to flash a CWM through ODIN but failed, but again there isnt anything that I have read that says "hey you can do this that way and it will work".
From what I understand I need to be rooted to install CWM or TWRP, and since I unrooted to try and fix the problem I cannot root myself through conventional methods. Everything I found online requires the phone to completely start up. (to the menu screen etc)
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
jd1639 said:
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
Click to expand...
Click to collapse
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
doesntmatterx said:
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
Click to expand...
Click to collapse
Do you know what firmware you were on? Was it mdl or mf3?

[Q] Going from Safestrap to CWM?

So a while back I went through the process to root my phone and went with safestrap. Now it appears the new roms aren't compatible with safestrap (is it because of 4.3 gapps?).
How would I go about switching over to CWM? Is there anything fancy? Is there a guide? Any help appreciated.
Thank You.
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Leraeniesh said:
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Yes unlocked. I will look it up. Thanks.
I believe you can also use backups made in Safestrap in TWRP (/data/ only)
Sent from my XT907 using xda premium
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
So I am getting the "cannot load cwm.img" on the command prompt.
cwm.img is in the same folder as fastboot and adb.
not sure what is up. Currently searching for solution....
EDIT: Typed full path. Seems to have worked....
RikRong said:
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
Click to expand...
Click to collapse
Booted back into safestrap. I'm assuming this is why?
jagsfan82 said:
Booted back into safestrap. I'm assuming this is why?
Click to expand...
Click to collapse
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
RikRong said:
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
Click to expand...
Click to collapse
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
jagsfan82 said:
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
Click to expand...
Click to collapse
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Leraeniesh said:
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
RikRong said:
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
Click to expand...
Click to collapse
My first thought is I need to strip down the system.. maybe i didn't wipe something properly or what have you.
jagsfan82 said:
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
Click to expand...
Click to collapse
Yeah unfortunately there's no command to boot recovery from fastboot.
You can try running "fastboot reboot" while holding the volume buttons right after flashing cwm. That should do the trick. It should boot to the boot selection menu, then you can choose to boot to recovery.
Also, thought you killed yourself when I read your other post...
fastboot boot cwm.img is one argument away from a very, very bad day... If you put "flash" before boot, you'd be in trouble... Lol
Maybe I should write up a root app that will rename install-recovery.sh... That's not a bad idea...
Sent from my XT907 using Tapatalk
I always just power down the phone after flashing recovery and then manually reboot into recovery.
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
sloosecannon said:
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Haha, nice.
RikRong said:
Haha, nice.
Click to expand...
Click to collapse
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
sloosecannon said:
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Installed on phone. Says found but disabled. Tried flashing cwm.img and rebooting into recovery. Still goes straight to OS...
Enable install-recovery doesn't work
this all seems very straightforward of a process that should be working...
Do I need to try wiping everything down as bare as possible?
Is this the process that works for others? Take safestrapped, rooted, bootloader unlock device on an old pre-bootloader-unlocked rom. Uninstall safestrap. Flash cwm.img using fastboot comand. Boot into recovery. Then you should be in CWM?

[Q] HELP phone soft bricked

Hello Everyone,
This is my situation.... I want Unrooting my Sprint S4 using Mobile Odin .... and now my phone only boots up to the Samsung Logo. On that screen it also says Recovery Booting however it turns off after 10 Secs. I can get my phone into download/odin mode but that is about it. I can not boot into recovery.
I would imagine someone either has experience or expertise on this matter.
PLEASE HELP
Thank you in advance,
V.E.
If possible what bootloader, modem and ROM were/are you on, also do you care about tripping knox (or is it already).
You have to wipe data to get it to boot. This will wipe EVERYTHING on internal memory. Or you could reroot and install install recovery over Odin and boot into recovery and wipe data which will be like wiping to do a clean Install for custom ROM install. Which wknr wipe everything. Once it boots up apply the stock unrooted tar via Odin with a COMPUTER.
Sent from my SPH-L720 using Tapatalk
I HAD Twrp recover... Had CWM recovery... phones acting like it doesn't have custom recovery (pain in my ass.)..... thought i used rom manger to put cwm back on it.
IDK the modem
I was on a Slim ROM (which was giving me problem as well; Great Rom but it just recently kept crashing.)
I already tripped knox forsure ..... and dont care..... i wanted to get it on a stock kernel by unrooting (Wasnt as brillant as I thought)
Don't even know if thats it possible (If it is show me the promise land! :angel: I wanted root again so I could get triangle away working on root.
However that is how I got here. So getting my phone operational would be a win, start; challenge accepted! :good:
s4 problems unite
daniel4653 said:
You have to wipe data to get it to boot. This will wipe EVERYTHING on internal memory. Or you could reroot and install install recovery over Odin and boot into recovery and wipe data which will be like wiping to do a clean Install for custom ROM install. Which wknr wipe everything. Once it boots up apply the stock unrooted tar via Odin with a COMPUTER.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Oh and I dont mind if it deletes the internal memory..... I live on my external brah. :cyclops:
Then if your phone is still stuck right now, boot into stock recovery and perform a factory reset and it should boot up. drink up!
Sent from my SPH-L720 using Tapatalk
ruh roh.
daniel4653 said:
Then if your phone is still stuck right now, boot into stock recovery and perform a factory reset and it should boot up. drink up!
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
How would i go about that ? How do i get into stock recovery? (Magical Recovery Combo GIVE ME THE SECRET! )
I cant boot into customer recovery mode(Volume UP+ Power +Home.. Combo...phone shuts off when i do that)
I can only get download mode.
Its only volume down and power when the phone is shut off.
Sent from my SPH-L720 using Tapatalk

Categories

Resources