So Im a newb to the phone tinkering thing, but I'm obsessed with it and want to really learn a phones potential, but i cant figure this out and I've searched hard enough.. So I have the Galaxy s6 sprint, but its unlocked and that was paid for by idoneapps and also Ive been tinkering with my build prop and Ive changed my model number but have yet to conquer changing the build number. Im running a custom rom which is (lamlazy rom beta). now heres my issue that I cant seem to solve (I know it will be simple to just use a computer and use odin but I dont want the easier method) lol . I do have twrp recovery and a backup plus i was rooted but my phone still says seandroid is not enforcing at boot up... that mean rooted, right ? anyways somehow my husband flashed the wrong twrp and I cant flash SuperSU to my system. my build is g920p CPD3 ans model is g920f, I'm stuck. Help?!?
oh yeah NOTE: when I do manage to get into twrp my touch screen doesnt work.
nsharer.v said:
So Im a newb to the phone tinkering thing, but I'm obsessed with it and want to really learn a phones potential, but i cant figure this out and I've searched hard enough.. So I have the Galaxy s6 sprint, but its unlocked and that was paid for by idoneapps and also Ive been tinkering with my build prop and Ive changed my model number but have yet to conquer changing the build number. Im running a custom rom which is (lamlazy rom beta). now heres my issue that I cant seem to solve (I know it will be simple to just use a computer and use odin but I dont want the easier method) lol . I do have twrp recovery and a backup plus i was rooted but my phone still says seandroid is not enforcing at boot up... that mean rooted, right ? anyways somehow my husband flashed the wrong twrp and I cant flash SuperSU to my system. my build is g920p CPD3 ans model is g920f, I'm stuck. Help?!?
oh yeah NOTE: when I do manage to get into twrp my touch screen doesnt work.
Click to expand...
Click to collapse
Seandroid is not enforcing comes up on some custom kernels such as arters kernel, it's normal. Hmm see if you can use the volume up and down to navigate and power to select, you maybe able to flash that way. The only other way I can see is to start from fresh using odin which will require a pc/laptop. Not sure if there are any other easier ways.
Hes right normally flashing wrong files like that causes more probs id just start over fresh. also a sprint user. Go with renegde rom seems to be about the smoothest nd if u use ktoonservative gov. Killer battery life. With some form of data connect all the time. Im now getting upto 6 hours screen on time.
Related
i am extremely new to the rom/flashing/rooting scene. i recently used a "back door" rooting process, which worked great and i did all the recomended actions and apps: supersu titanium backup, root browser, etc. then i wanted to change my boot animation->samsung device-> flash a zip file to allow bootanimation.zip->samsung requires signature verification from stock recovery mode->cwm recovery(which flashes itself to the phone... curious why a custom recovery...or any recovery for that matter is even required if it isnt necessary...) -> recovery menu no longer accesible. i cant flash anything to my phone i tried changing the recovery to twrp but no dice. its giving me this dialog along with caution sign:"system software not authorized by verizon wireless has been found on your phone...etc" the phone is a samsung galaxy legend on verizon prepaid plan it is the jasper version of the samsung galaxy stellar. now for the question... What do i do so that i can flash files to my device?
i dont know much about unlocking the bootloader except that doing so with the wrong program will brick your phone and since im doing this recreationally on my primary phone i dont want to buy a new one. how can i regain access to my recovery menu/ unlock my bootloader?
its not a popular phone so i doubt anyone is going to be able to offer a one touch application to unlock the bootloader but any information would be helpful.if youre still reading this i thank you for any advice and i apologize if i : posted in the wrong section, offended anyone, or came off as a cheap experience-less n00b
EDIT: my phone is running 4.1.2 jellybean, baseband:i200ppvramh1, kernel: 3.0.31, build: jzo54k.i200ppvramh1, dont know if that will help any and before anyone criticizes me remember i am completely new to this forum posting thing but i guarentee i have scrounged this site the world over trying to get help but there just seems to be noone working on this problem the same as me...
So i have rooted my phone done the service menu flashed my phone and i have Odin up and phone in Odin mode. Now with the recovery there are many options to choose and i dont know which rom to pick in terms of philz recovery. I also dont know how to tell roms apart from another lol im stuck. Or maybe im looking at it wrong and there' only one option. I want to be able to use net 10 on a sprint galaxy s4. I do not show invalid sim anymore and from what Im following Im on the last step
Realy i just need to know which rom to use at this point. If someone can point me to
lclutchl said:
So i have rooted my phone done the service menu flashed my phone and i have Odin up and phone in Odin mode. Now with the recovery there are many options to choose and i dont know which rom to pick in terms of philz recovery. I also dont know how to tell roms apart from another lol im stuck. Or maybe im looking at it wrong and there' only one option. I want to be able to use net 10 on a sprint galaxy s4. I do not show invalid sim anymore and from what Im following Im on the last step
Click to expand...
Click to collapse
Realy i just need to know which rom to use at this point. If someone can point me to a rom i can use to make my galaxy s4 usuable on Net 10 on atts network then i will be done please. I have been at this for days and this is the last step
So my Samsung Galaxy Note 5 is stuck on SEAANRDORID KERNAL NOT ENFORCING, AFTER A FAILED ROOT.
I can still get to the download screen
How can I get it back to working order. I dont care about losing info on it I just dont want a 800 paperweight!!1
Its the Sprint Model, im pretty sure it was running 6.0.1
If someone could help me out that would be great. I have to get the phone sent back to me from the states because I am currently serving overseas in Korea with the Army. Would like to fix if possible so I dont have to pay out of pocket for a new phone! Thanks in Advance!
TikTok1990 said:
So my Samsung Galaxy Note 5 is stuck on SEAANRDORID KERNAL NOT ENFORCING, AFTER A FAILED ROOT.
I can still get to the download screen
How can I get it back to working order. I dont care about losing info on it I just dont want a 800 paperweight!!1
Its the Sprint Model, im pretty sure it was running 6.0.1
If someone could help me out that would be great. I have to get the phone sent back to me from the states because I am currently serving overseas in Korea with the Army. Would like to fix if possible so I dont have to pay out of pocket for a new phone! Thanks in Advance!
Click to expand...
Click to collapse
are you on stock recovery or twrp recovery? if you have twrp installed I would do a wipe of dalvic and cache and reboot. Or at this point you could flash a new rom like MOAR 4.2 witch is also 6.0.1 I believe.. TWRP can be flashed with ODIN and the rom can be flashed with TWRP Unless your planning on staying on stock rom and just gain root but I would still flash a good recovery like TWRP at the least so you can do a wipe and backup and restore from recovery. Be careful to read all instructions in the forum when flashing any rom or recovery or you can soft brick your phone. It sounds to my like you have a soft brick witch is easy to fix with odin and flashing a good recovery like TWRP.
good luck and be sure to read the OP steps and follow them when flashing
Hell! I meant to say HELLO ! But probably "hell" is context appropriate too!
I bought a BOOST specific Samsung SIII this week and rooted it. I used ODIN 3.04 and TWRP then Chainfire's SuperSU and PhilzTouch with SUCCESS.
(It's Jan 2017 by the way).
But afterwards, like when I was done installing all my usual post-root utilities, I was fooling around in TWRP and wiped the dalvik cache. I am now stuck in a bowl of BOOTLOOPS and all I can do is either boot to TWRP and flip to different utility screens in TWRP, or boot into DOWNLOAD MODE (fully functional: able to download from ODIN I mean), or power-up and BOOTLOOP with the Boost LOGO coming on before it reboots.
What have I done! Where can I get a stock image for this phone? So far I haven't found one anywhere on the net.
I have tried to use KIES 2, KIES 3 and Smartswitch to enter my model and IMEI (using the HEX # behind battery for IMEI).
I then bought ANOTHER SIII cheap. Rooted that one and used Smartswitch to back it up. I won't screw this one up but I don't believe I screwed the first one up either, just need stock. But the new phone is NOT OA3 (I had no way to know this when I ordered it from Amazon lol)
I would really appreciate --I mean tremendously appreciate--any one who had time for a couple back-and-forth messages to intervene and advise!
follow-up
I realise that wiping the dalvik cache may not have caused the issues I am having. When I was in TWRP mode I may have done something else--can't remember--I have neurological problems besides being a newbie. I just feel pretty sure that if I can ODIN an .iso tar of boost kitkat for this SPH-L710T all will be well but hell I know less than nothing and hate myself for not know what I did
vlaxonia said:
Hell! I meant to say HELLO ! But probably "hell" is context appropriate too!
I bought a BOOST specific Samsung SIII this week and rooted it. I used ODIN 3.04 and TWRP then Chainfire's SuperSU and PhilzTouch with SUCCESS.
(It's Jan 2017 by the way).
But afterwards, like when I was done installing all my usual post-root utilities, I was fooling around in TWRP and wiped the dalvik cache. I am now stuck in a bowl of BOOTLOOPS and all I can do is either boot to TWRP and flip to different utility screens in TWRP, or boot into DOWNLOAD MODE (fully functional: able to download from ODIN I mean), or power-up and BOOTLOOP with the Boost LOGO coming on before it reboots.
What have I done! Where can I get a stock image for this phone? So far I haven't found one anywhere on the net.
I have tried to use KIES 2, KIES 3 and Smartswitch to enter my model and IMEI (using the HEX # behind battery for IMEI).
I then bought ANOTHER SIII cheap. Rooted that one and used Smartswitch to back it up. I won't screw this one up but I don't believe I screwed the first one up either, just need stock. But the new phone is NOT OA3 (I had no way to know this when I ordered it from Amazon lol)
I would really appreciate --I mean tremendously appreciate--any one who had time for a couple back-and-forth messages to intervene and advise!
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried kies/smartswitch emergency firmware recovery ? This should return your phone to stock. You could also use twrp to flash another rom from here
https://forum.xda-developers.com/galaxy-s3-sprint/development
Good Luck
Sawdoctor
Hey thanks for your reply
When I put Smartswitch on my computer, it couldn't identify the broken SIII (unknown device error).
(Smartswitch DID identify the other functional Boost SIII )
It's crazy that it boots all the way to the Boost logo screen then reboots. What is happening?
Is there any chance you can walk me through some steps--I am having trouble finding functional mirrors to things and I'm not sure if I should just give up--I don't give up easily but, being inexperienced in this realm, feel foolish in the event the bootloop is a permanent, irremediable error. Then anyone else comes here will see the original thread title and feel heartened.
I seem to need a stock image for OA3 L710T. I see loads for L710 but then the radio won't turn on, according to what I have gathered.
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/