Problems with Custom Recovery - AT&T Samsung Galaxy Note II

I have been using TWRP since I purchased my NOTE 2.
I am now having a problem - When I booted into Recovery today - I ended up in a Recovery BOOTLOOP - NO matter what I did to try to "REINSTALL" TWRP, the same thing happens - when I go to recovery I get as far as the Curtain and then it reboots. (TWRP 2.3.3.3) I also tried 2.3.3.1)
SO I flashed CWM - I was able to get that installed and I can boot into CWM fine - but there are other issues.
When I try to wipe data/factory reset - the phone reboots and then launches CWM - If I pull the battery and then reboot - it reboots fine and nothing is wiped.
When I try to create a backup - the final backup seems very small to me - only 16mb
I am not sure what to do at this point? I can't make backups - and I can't flash anything really - or at least I cant flash if I need to wipe data first -
any suggestions anyone?
(PS - this happened a while back to the original NOTE 2 I had purchased, and I eventually got frustrated and returned it to ATT and got a new phone - unfortunately, I can't do that again)

mocsab said:
I have been using TWRP since I purchased my NOTE 2.
I am now having a problem - When I booted into Recovery today - I ended up in a Recovery BOOTLOOP - NO matter what I did to try to "REINSTALL" TWRP, the same thing happens - when I go to recovery I get as far as the Curtain and then it reboots.
SO I flashed CWM - I was able to get that installed and I can boot into CWM fine - but there are other issues.
When I try to wipe data/factory reset - the phone reboots and then launches CWM - If I pull the battery and then reboot - it reboots fine and nothing is wiped.
When I try to create a backup - the final backup seems very small to me - only 16mb
I am not sure what to do at this point? I can't make backups - and I can't flash anything really - or at least I cant flash if I need to wipe data first -
any suggestions anyone?
(PS - this happened a while back to the original NOTE 2 I had purchased, and I eventually got frustrated and returned it to ATT and got a new phone - unfortunately, I can't do that again)
Click to expand...
Click to collapse
Odin back to stock, install chainfires exploit fix/root apk and use it only to root then install goo manager and use it to install twrp. Did this to my note 2 and had it rooted with twrp installed before I even got home from the att store.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

jyazzie110 said:
Odin back to stock, install chainfires exploit fix/root apk and use it only to root then install goo manager and use it to install twrp. Did this to my note 2 and had it rooted with twrp installed before I even got home from the att store.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Do you have a link for the Stock TAR? and do I need to flash anything else? Boot image?

mocsab said:
Do you have a link for the Stock TAR? and do I need to flash anything else? Boot image?
Click to expand...
Click to collapse
IIRC everyones been getting them from http://www.sammobile.com/firmware/?page=3&model=SGH-I317&pcode=ATT&os=1&type=1#firmware btw this is for the at&t model. And you dont need anything else
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

jyazzie110 said:
IIRC everyones been getting them from http://www.sammobile.com/firmware/?page=3&model=SGH-I317&pcode=ATT&os=1&type=1#firmware btw this is for the at&t model. And you dont need anything else
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Thanks - I found a similar download from somewhere else- I317 - tar - I used odin - but it seemed to stick on the Samsung logo - after the 'att' boot - and never booted up - how long should it take? I waited five minutes and it didn't happen.
I am hoping this file works better -
Does it take a long time to boot up the first time?

mocsab said:
Thanks - I found a similar download from somewhere else- I317 - tar - I used odin - but it seemed to stick on the Samsung logo - after the 'att' boot - and never booted up - how long should it take? I waited five minutes and it didn't happen.
I am hoping this file works better -
Does it take a long time to boot up the first time?
Click to expand...
Click to collapse
Usually it takes awhile. But I would boot into recovery and perform a factory data reset and see if that works
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

jyazzie110 said:
Usually it takes awhile. But I would boot into recovery and perform a factory data reset and see if that works
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I gave I ten minutes - no dice - I just went into Recovery and wiped data/facory reset - we'll see if that works.
If not - what options do I have?
Can I ROOT and then Flash CWM thru Odin - then flash a new rom?

mocsab said:
I gave I ten minutes - no dice - I just went into Recovery and wiped data/facory reset - we'll see if that works.
If not - what options do I have?
Can I ROOT and then Flash CWM thru Odin - then flash a new rom?
Click to expand...
Click to collapse
Yea you should be able to do that? Idk bout cwm I havent use it in ages.....lol why not just install a rom through twrp??
Btw did it boot? Sorry for the late reply?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

I went into stock recovery wiped data factory reset and was finally able to boot.
Thankd for the help
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

jyazzie110 said:
Yea you should be able to do that? Idk bout cwm I havent use it in ages.....lol why not just install a rom through twrp??
Btw did it boot? Sorry for the late reply?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
SO - I did everything you suggested and I was able to get things working again, I am now back on TWRP and running Jelly THunder RC2 - what I am curious about is why did this happen in the first place?
I have been flashing for several years now -and this is the second time this has happened to me with a GNOTE 2 - I NEVER had this kind of problem before and I really am not doing anything different from what I did before.
Could it be related to Undervolting? I am not doing any thing crazy - but I am undervolting by about -50 on all frequencies - Could that be the culprit? Oris the GNOTE II just sensitive?
I really don't want to go thru that again and short of not flashing anything again -I am not sure what to do to try to limit the chances it will happen again? Any ideas?

Related

What's wrong with my phone

Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.
hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Try TWRP 2.2.1.1
hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.
I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium
Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.
The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.
OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.

(Q) Been Gone For Some Time...???

I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?
XxLostSoulxX said:
I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?
Click to expand...
Click to collapse
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working
XxLostSoulxX said:
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working
Click to expand...
Click to collapse
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium
LuigiBull23 said:
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there
XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Click to expand...
Click to collapse
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file

			
				
XxLostSoulxX said:
Click to expand...
Click to collapse
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
XxLostSoulxX said:
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file
Click to expand...
Click to collapse
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.
XxLostSoulxX said:
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.
Click to expand...
Click to collapse
No AOSP ROMs at all? I would go back to complete stock, update to MA7 or MC2 then reroot and try flashing again.
Sent from my Nexus 4 using xda premium
XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there
Click to expand...
Click to collapse
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.
Skripka said:
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.
Click to expand...
Click to collapse
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation
XxLostSoulxX said:
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation
Click to expand...
Click to collapse
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.
Skripka said:
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.
Click to expand...
Click to collapse
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check
okay i used Toolkit 4.1.0 and chose to flash to stock and it didnt work because i still have root and still on ljc, and same setup as before, i cant update to ma7, however i chose to install stock recovery, but i know if i do update it will fail.
EDIT: **** it wont even reboot to install the update. says rebooting now and nothing. F THIS PHONE.
I CANT EVEN UNROOT
XxLostSoulxX said:
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check
Click to expand...
Click to collapse
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.
XxLostSoulxX said:
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.
Click to expand...
Click to collapse
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
correct yeah because i restored so i can atleast use my phone to try to fix it using toolkit
EDIT: Hooray i finally got it that did the trick this time. however basband is still LJC but is 4.2.2 because i went through setup this time and was able to boot up

HELP ME!!!!!

ok guys im very frustrated. this is my 3rd s4 and i just want to know what im doing wrong, im on a tmobile phone. so when i get my s4 i immediately root it via twrp method, then i go and find i good stock rom to flash, my favorite is wicked rom, i get the rom, putt it on the external sd card, flash the rom and flash ktoonsez kernel, it reboots and the rom works fine no problems, until i try and reboot, then it just hangs on the samsung galaxy s4 boot screen, and it then starts to bootloop without ever going back on, ive tried flashing multiple stock roms and even leaving the kernel stock and tried different kernels without any luck, i can odin back to stock and it works fine, also i can flash any aosp rom and i dont have any reboot issues, this has happened with every phone, im at a loss and i have no idea what im doing wrong, clearly something, i need help. please help guys
Did you do the wipes, including factory reset?
Yes I do all the wipes
Sent from my SGH-M919 using xda premium
Did you install the touchwiz kernel and NOT the aosp kernel?
Sent from my SGH-M919 using xda app-developers app
Yes lol, I'm not that daft
Sent from my SGH-M919 using xda premium
Just some quick questions. What model is your phone? Which TWRP did you flash? Did you check the md5 checksum of the rom and kernel zips?
Sent from my SGH-M919 using xda app-developers app
Model SGH-M919, I've tried twrp 2.5 and 2.6, mostly use 2.5 because I have issues with 2.6 and yes I've checked them multiple times, re-download them both multiple times as well
Use cwm, both versions of twrp are bugged or something is wrong with it. Cwm will do the trick for you
Sent from my SGH-M919 using xda app-developers app
Use Chainfire root, so easy.
Sent from my SGH-M919 using Tapatalk 2
I encountered the same problem, go to KTweaker if you are still using ktoonsez kernel. And change your settings to this.
Make sure you set it to on Boot as Immediately & save the settings. Same thing happened to me, I put in his settings and problem vanished.
After you do that, turn it off and go to recovery. Wipe Dalvik Cache & Cache than finally Fix Permissions in Advanced.
aznvi3tric3guy said:
Use cwm, both versions of twrp are bugged or something is wrong with it. Cwm will do the trick for you
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
didnt work
TehZam said:
I encountered the same problem, go to KTweaker if you are still using ktoonsez kernel. And change your settings to this.
Make sure you set it to on Boot as Immediately & save the settings. Same thing happened to me, I put in his settings and problem vanished.
After you do that, turn it off and go to recovery. Wipe Dalvik Cache & Cache than finally Fix Permissions in Advanced.
Click to expand...
Click to collapse
+1 you're having an issue with the kernel you're using.
Are you using exFAT 64gb sd card? If you are, take it out and your phone will boot fine.
Sent from My S4 in BEASTMODE
Ok. Because you formatted the internal storage with TWRP your partitions are probably messed up. Odin back to stock (like you need to return it) and start over again. You can use TWRP if you want, its a great recovery. Just dont format the internal storage with it. Obviously try the easier fixes first, ie SD card. These phones seem to be more sensitive to formatting than previous galaxy models.
aznvi3tric3guy said:
Use cwm, both versions of twrp are bugged or something is wrong with it. Cwm will do the trick for you
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
TWRP isn't bugged. I have been using it since my s2 and had no issues whatsoever
~~~~~~~~~~~~~~~~~~~~~
I am always on the mobile app and am always 'trying' to help others and moderators on the forum and learning something new everyday. I make stupid posts sometimes, but I never repeat a mistake more than once. I may not be a developer, but I know alot of stuff, so feel free to messsge me any questions and I'll be happy to answer them to the best of my ability.
~~~~~~~~~~~~~~~~~~~~~
I'm starting a video game company with my friend where we will be making Android games. message me for more info or go here: http://forum.xda-developers.com/showthread.php?t=2290843
CodenameRondo said:
didnt work
Click to expand...
Click to collapse
Ive been thru this issue also Trust me Restore stock once more and use oudhs cwm base recovery with swipe gestures. .. skip the twrp junk.
You need to root in a specific manor to bypass the Selinux permissive setting that samsung put on the s4.
I root with odin and flash these files in order after u google search them there also in the s4 root section ..I forget which page.
First @ foremost
FLASH RECOVERY I RECOMEND OUDHS 1.0.3.3 swipe gesture By shabby penguin.
Reboot device into recovery
Flash in order
1# root m919 UVUAMDL.zip
2nd #flash MDB SetUIDoff.zip that bypasses the kernel issue that samsung has blocked ..
3# flash superuser.zip of your choice
#4 wipe cash
5#reboot
You can now flash any Rom, restore etc.... no issues.
Sent from my SGH-M919 using xda app-developers app
I'm having issues no matter what kernel or rom I flash, I'm pretty sure it's a bit more complicated than that
Sent from my SGH-M919 using xda premium
No its not actually. ... if you would odin back stock and root the way I said with files i mentioned you would see.. if you dont want to then thats fine too.
You dont even need odin stock
Just format system in twrp
Then reflash the files.
Sent from my SGH-M919 using xda app-developers app
lojak29 said:
Ive been thru this issue also Trust me Restore stock once more and use oudhs cwm base recovery with swipe gestures. .. skip the twrp junk.
You need to root in a specific manor to bypass the Selinux permissive setting that samsung put on the s4.
I root with odin and flash these files in order after u google search them there also in the s4 root section ..I forget which page.
First @ foremost
FLASH RECOVERY I RECOMEND OUDHS 1.0.3.3 swipe gesture By shabby penguin.
Reboot device into recovery
Flash in order
1# root m919 UVUAMDL.zip
2nd #flash MDB SetUIDoff.zip that bypasses the kernel issue that samsung has blocked ..
3# flash superuser.zip of your choice
#4 wipe cash
5#reboot
You can now flash any Rom, restore etc.... no issues.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
phone doesnt boot now, and i did everything in order
CodenameRondo said:
phone doesnt boot now, and i did everything in order
Click to expand...
Click to collapse
Does Odin recognize it?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

[Q] My S3 is stuck on the logo after using CWM. Odin not working please help

Alright, im not completely new to rooting but I have encountered a new problem.
I rooted my phone through odin (galaxy s3 T999), had some hiccups with that so I ended up downloading the stock rom tar and reflashed using that, problem solved good to go still rooted. awesome.
So, I attempted to flash the cyanogen rom using clockwork mod. it wouldn't come past the load screen, went into clockwork mod to recover my backup but for some reason it wouldn't let me access the SD card to get it. next thought was to go back to odin and flash the same file I used previously to get back to where I was, for some reason this is not working, I can get to download, use odin to flash it, says success and all that, then upoon rebooting it stays at the Samsung loading screen.
So from there I went and downloaded the GS3 toolkit and tried all of their recovery files, all having the same issue. about 18 flashes later I tried reformatting from the phone itself, same issue with the samsung logo being stuck. And now, I am currently baffled, anyone wanna help me out? I have a feeling it has something to do with the .pit option on odin, but I am not that advanced and its just a hunch. so...thanks in advance guys!
So I understand not to touch pit, roger, reading other posts makes that clear, but still cant find a fix, the top right of my download says
ODIN MODE
Product Name SGH-T999
Custom Binary yes: 19 counts
Current Binary Samsung Offical
System Status Custom
Qualcomm secureboot Enable
Okay, what is the current state of the device?
Whst do you see when you boot into recovery ( take battery out of phone the put it back in and do the following: hold volume up, home button and power button, let go of all buttons when you feel the phone vibrate and blue text flashes in the upper left corner of the screen)?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I just tried to send a rom over that had CWM 6.0.2.3 and it installed that, but still stuck on logo. going into recovery I am in CWM 6.0.2.3
have the standard options wipe/factory, install from zip etc.
You flashed a rom that had cwm 6.0.2.3 or did you flash a rom while on 6.0.2.3?
Sent from my SGH-T999 using XDA Premium 4 mobile app
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Flashed a rom that had 6.0.2.3. I do not have any roms on my ZIP, been doing everything through ODIN. Very confused as to why it suddenly stopped working.
DocHoliday77 said:
I'd say about 98% of the time, when it hangs like that you just need to factory reset.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
I would do what Doc said.
If it still doesnt work, download a rom of your choice (in the t-999 section) and do a full wipe before flashing the rom you picked.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what do you mean by full wipe, factory reset? or something else?
connorjiy said:
what do you mean by full wipe, factory reset? or something else?
Click to expand...
Click to collapse
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
When flashing a new rom, you have to do a full wipe or youll run into problems like you are currently having.
If you dont know what a full wipe is, then stop what you are doing and put your phone down. Just about every rom thread here on xda explains what a full wipe is, it will be in the first post of the thread.
Like I said, find a rom you like in the t-999 section and flash it after doing a full wipe.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looked it up, that is what I do by default, didn't know thats what was considered a full wipe, just tried it with similar results, didn't know about the dalvik cache though. im on a work computer so I cannot currently DL a new rom from the site, I hope thats what the issue is, but I still cannot see why my other ones would suddenly not work.
connorjiy said:
tried to factory reset and it does the same logo stuck business. That was the last thing i tried after attempting to back up and reflash numerous times. tried flashing again recently, it will install CWM if it is attached to the rom but still gets stuck on the logo. tried re installing odin as well, it is working as usual, starts, restarts the phone, sits awhile, success. then i restart the phone and never get past logo.
Click to expand...
Click to collapse
I'm just not sure what you mean by it installing CWM attached to a Rom? Recoveries shouldn't be included with a Rom.
Odin flash the root66 firmware, then reboot to STOCK recovery and factory reset. This will wipe all user data, including your internal sd card. Then try rebooting again.
Sent from my SGH-T999L using XDA Premium 4 mobile app

No Recovery?

So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app
devynbf said:
So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
BACARDILIMON said:
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Click to expand...
Click to collapse
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app
devynbf said:
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I am not familiar with asop so I don't know what to say. But best bet is Odin back then flash twrp as you would like
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
just connect fastboot
fastboot flash recovery (recoveryname).img
Hi man,i also have a sm n900t and im having this problem to,tried with every kind of recovery but no1 made it possible to boot into recovery,did you find an answer?

Categories

Resources