Hi i read around and seen many different suggestions on this but was wondering if there was a clearly outlined step by step for this phone factory unlocked but carrier is Telus Canada SGH-I337M
I have factory reset the phone with oden after putting cyanogen-mod on it and now i have no sound, no wifi, and when i try to make calls it freezes the phone
I also have the "kernel not seandroid enforcing set warranty bit: kernel
I have tried various different methods listed on this site and others all to no avail and now i am frustrated and confused lol
Is there a step by step to make this all work again or have i coma-toasted my phone and should chuck it in the river?
thanks alot for any tips greatly appreciated
Related
Hi to all
I hope one or more of the very knowledgeable people out there can help me. Have a qualcomm SM-N9005 32gb European SIM model which was in a constant boot loop. Ocassionally, it would get to the the set-up screen but always go back into its loop boot once a few key presses had been made. It was on one of the 4.3 roms at the time - don't know which one.
So I put in it into download mode, flashed the stock 4.4.2 N9005XXUENB7_N9005OXAENB1_BTU rom via odin and this has solved (most of) the boot loop issues.
However, the phone is now showing as having:-
no IMEI
no baseband
no sim (despite there being a working sim in there).
If I go back into download mode, it seems an additional line has been added to the several that show at the top after flashing the stock Kitkat rom - this is "UDC START".
I don't have an EFS backup so can't restore that to get the IMEI/baseband back.
I am at a loss. I have tried a hard/factory reset - no joy. I know this kind of problem has been reported in the past and I have looked at many threads but no-one seems to have exactly the same problem and not many successful outcomes.
Can someone please give me a 'dummies walk through' of what to do - my phone expertise isn't the best, as you can see!
Many many thanks to anyone and everyone who can help.
Cheers :good:
largeruk said:
Hi to all
I hope one or more of the very knowledgeable people out there can help me. Have a qualcomm SM-N9005 32gb European SIM model which was in a constant boot loop. Ocassionally, it would get to the the set-up screen but always go back into its loop boot once a few key presses had been made. It was on one of the 4.3 roms at the time - don't know which one.
So I put in it into download mode, flashed the stock 4.4.2 N9005XXUENB7_N9005OXAENB1_BTU rom via odin and this has solved (most of) the boot loop issues.
However, the phone is now showing as having:-
no IMEI
no baseband
no sim (despite there being a working sim in there).
If I go back into download mode, it seems an additional line has been added to the several that show at the top after flashing the stock Kitkat rom - this is "UDC START".
I don't have an EFS backup so can't restore that to get the IMEI/baseband back.
I am at a loss. I have tried a hard/factory reset - no joy. I know this kind of problem has been reported in the past and I have looked at many threads but no-one seems to have exactly the same problem and not many successful outcomes.
Can someone please give me a 'dummies walk through' of what to do - my phone expertise isn't the best, as you can see!
Many many thanks to anyone and everyone who can help.
Cheers :good:
Click to expand...
Click to collapse
Have you try to look at this >>http://forum.xda-developers.com/showthread.php?t=2567133, http://forum.xda-developers.com/showthread.php?t=2627291, https://www.youtube.com/watch?v=Pai4BH3AWq8, http://forum.xda-developers.com/galaxy-s2/general/imei-baseband-guide-t1596842, http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
please make some research first before attempting to follow the guide. I know some of them are not for our phone and im not sure it will work for you, but if you can do more research and keep on trying, maybe there is a way
I followed the instructions located at http://androidcentral.us/2014/04/how-to-root-sprint-samsung-galaxy-s5-sm-g900p/ , my Galaxy S5 wouldn't boot. It was stuck on a screen which said "Recovery is not seandroid enforcing".
I found a post elsewhere on the xda-developers forums which suggested re-doing the CF Auto Root step and pulling the battery before the phone reboot, which I successfully pulled off but the phone still would not get past the "Recovery is not seandroid enforcing" screen.
I was able to restore my phone to a usable state using http://forum.xda-developers.com/showthread.php?t=2734322&page=7 and a utility for converting .img files to files suitable for Odin to upload to the phone. However, I'd still like to get the phone rooted.
Can anyone help? Would perhaps loading a standard KitKat kernel first be what's needed? I haven't done any modifications to the phone before this, but I realize that Sprint may have, and I'm wondering if that's what's throwing the process off.
Hello there. I don't know much about software and all, but I'm opening a cellphone repair shop and I tried to root a canadian (bell) S4 i337m to hopefully manage a carrier unlock without a code. It didn't work, the rooting. I pumped a lot of files into the phone and may have wrecked stuff.
At one point, I rebooted it, and the touch screen stopped working. I opened up the phone, checked all the connectors, everything is good. So I ended up downloading a stock bell i337 rom and installing that through odin. Now I get the "kernel is not seandroid enforcing / set warranty bit: kernel" top left on startup, and the touch screen still doesnt work.
I am currently downloading other rom files to test but there is also one thing, I'm using a nexus 5 data cable because I dont have the stock one and dont know where to find one.
So, what could I be doing wrong? I just changed the LCD/glass/digitizer assembly yesterday, I don't have a very long warranty period on parts so I need that kernel code thing to go asap.
Hello everyone! I got the device is SM-N900V, although the firmware is written everywhere that this is a SM-N9005, in the end, I decided to gain root and put custom recovery methods for SM-N9005, but in the end, the phone constantly trying to boot into recovery and says "Recovery is not seandroid enforcing" and then the whole screen "System software note authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help". Download mode works, but One sees the connection, but flash wants nothing((( Help please! Possible duplicate topic, but I'm not really good with English, sorry in advance!
takosan4ik said:
Hello everyone! I got the device is SM-N900V, although the firmware is written everywhere that this is a SM-N9005, in the end, I decided to gain root and put custom recovery methods for SM-N9005, but in the end, the phone constantly trying to boot into recovery and says "Recovery is not seandroid enforcing" and then the whole screen "System software note authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help". Download mode works, but One sees the connection, but flash wants nothing((( Help please! Possible duplicate topic, but I'm not really good with English, sorry in advance!
Click to expand...
Click to collapse
No help available. You cannot run other ROMs on the Verizon Note3. The SM-N9005 ROMs will not work.
Sent from my Note 3 via Tapatalk
please please help me
This is the same problem I'm having why n9005 rom not work? can work other roms on this phone?
samiabe said:
This is the same problem I'm having why n9005 rom not work? can work other roms on this phone?
Click to expand...
Click to collapse
As of now....NO
Sent from my Note 3 via Tapatalk
Hi Guys,
I have a sm-n910u (note 4) that my brother has attempted to flash. however its now stuck in the reboot loop with error "recovery is not seandroid enforced"
I personally am very new to the whole phone flashing, rooting and modding stuff but very experienced in IT.
I have played around with different roms and oden but cant seem to make it work
I was hoping that someone might be able to guide me in at least getting the factory system back on there.
details are sketchy about what has been done already but i do have the device here.
any help would be awesome.
Thanks in advance