Related
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
You might have root but from the sounds of it the tab does not like the insecure kernel hence the yellow triangle on the logo screen. On a tab, I am not sure how to get around this.
Why not run stock and use TiBu to get rid of the bloatware until you can find a solution? Keep a Nandroid of bone stock then another for your custom settings...
Mardenator said:
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
Click to expand...
Click to collapse
What roms did u flash...?
Sent from my GT-P7500 using XDA App
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
ZangetsuNX-01 said:
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
Click to expand...
Click to collapse
Tried this, got the same result I've been getting..
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Mardenator said:
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Click to expand...
Click to collapse
Next time please use the edit button.
I think I have an explanation as to why its crashing. The ISI-Galaxy Rom and P7500XWKK4 Galaxy Tab 10.1 / HC 3.2 ROM are for the P7100 model. Yours is the SCH-I905 model so the roms you tried to flash are incompatible.
Just realized that ZangetsuNX-01 is right, I've been flashing WiFi-only ROMs, not ROMs for the Tab 10.1 LTE. Downloading http://forum.xda-developers.com/showthread.php?p=17858660#post17858660 now, will flash and post results here asap.
UPDATE: got a leaked TW ROM to install via Odin and boot, posting this from the tablet. Added a screenshot for kicks.
BTW, for anyone with an LTE Tab, flash this via ODIN NAO!!!!
http://rootzwiki.com/topic/10463-ro...x-leak-build-for-vzw-galaxy-tab-101-lte-only/
It's unrooted, with stock recovery, but you can follow the directions on the page to get root, it's simple. Just Odin a recovery .tar file, go to recovery, flash SU zip, and voila. Running it at 1.4GHz max, 1GHz min, and it's awesome. TouchWiz is also a nice step up from stock HC.
@Mardenator
your screenshot a looke liek from my adwluncher from my tab...
Lol I'm using ADW Ex.
ok i dont untersant waht you with them post, sorry.
Conan179 said:
ok i dont untersant waht you with them post, sorry.
Click to expand...
Click to collapse
I'm not sure what the question here is, but I was suggesting that if you have an LTE Galaxy Tab 10.1, you should flash the ROM that I provided a link to. It's a good ROM, and I've been running it for 2 days now.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4
First time flashing CM, and I may have messed up.
I rooted, installed TWRP, everything went perfect. I made a backup, and then tried to do a factory wipe. The wipe ended with the messages "unable to mount /system", "... /cache" and another one. I still tried to flash, and it just immediately got stuck, nothing happened. I rebooted, and everything worked fine. It was the Samsung stock image and all my apps were still there. I'm assuming it just didn't wipe at all.
I then went full retard mode, and tried to do a restore. I wanted to be sure my phone wouldn't fail on me in the recent future because some random stuff may have been partially wiped or something. Feel free to tell me I have the IQ of a chimp.
This completely messed things up, as it just got stuck at "Restoring System...". Eventually I restarted it with the power button. Now it can't boot normally, it can't boot into recovery mode, which just leaves download mode.
Any way I can fix this and subsequently install CM properly? I'm using TWRP 2.6.3.0. I've been told it's recommended to use 2.5, as the other version may have some issues (including not being able to recognize partitions). Only download mode still seems to work, so maybe there's a way to flash my phone back into the living world?
Versions:
Team Win Recovery Project 2.6.3.0
CyanogenMod 10.1.3 (RC2 jfltexx)
Thanks!
No idea really but maybe try to flash default rom/recovery etc with odin?
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Sent from my GT-I9505 using XDA Premium 4 mobile app
HANDSY said:
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Click to expand...
Click to collapse
I got the Samsung stock ROM of july, flashed it using download mode, and everything was back! I then rooted it again, and installed CMW (see versions below). I went into recovery, and tried to do a backup. It told me it failed: "Error while making a backup image of /data!". I then wondered if it may have been due to a lack of storage (which could very well be, as that was the issue before and the old backup by Teamwin was probably still on it somewhere), so I rebooted my phone. That's when it just failed and kept showing the Samsung logo at boot. I tried flashing my ROM again, again the logo. Then I did a factory reset using the regular recovery (cache and data reset), which fixed it. Now all my apps and data are gone, but that's no problem.
I'm back at the unrooted Samsung stock image now. Any ideas what I did wrong? These were the versions I used:
CF-Auto-Root-jflte-jfltexx-gti9505
i9505-cwm-recovery-6.0.3.2(0611)
Odin3 v3.07
I did nothing more than root, install CMW, try a backup and then it all went to ****. I'm surprised a backup can even do that.
Mmm I'm not too familiar with the internal workings of backups. Perhaps something was corrupted during flashing? Glad to hear that you have got your phone working again. There is an updated version of CMW somewhere in the original development thread.
Sent from my GT-I9505 using XDA Premium 4 mobile app
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Chillzone said:
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Click to expand...
Click to collapse
I tried CMW 6.0.3.6 and the Google Play 4.3 ROM as you said, and it works perfectly! I didn't try a backup this time, as it didn't exactly have anything to back up anymore.
Finally my precious vanilla Android again, I missed it since I switched from my Galaxy Nexus to my S4. Thanks a lot guys!
Edit: I do seem to be having one issue. Quite frequently after it's booted, and I enter the SIM pin, the message "Unlocking SIM card..." stays there indefinitely. I can use the phone but the message covers everything up. This doesn't always happen, but quite often. I've read some ROMs can't handle SIM lock, like CM. This is a Google Play edition, however. Is it normal that this doesn't work?
I can seem to fix it by holding the power button, and choosing "Unlock SIM" from the menu. I guess it's not that bad as I don't often reboot my phone.
Kinda odd something I came across today in my S4, something I see others having mentioned before. Getting stuck on the att logo screen. I am stock rom, just rooted. Right now it seems to be back to normal on reboots and so, but a few mins ago, it would get stuck there on one boot, next boot might be fine. Now I did go into recovery to try that wipe cache, tho the android icon said error after it started and just rebooted, so not sure the deal there. Just was wondering, is this something that more people get commonly a random stuck on att logo? (Or is it just a odd thing where it could be a super long boot up and just wait?)
Now with reboot or shutdown, anyone know the deal why that seems to take so long to do?
Edit: Take that back, this reboot test, got stuck again on att logo... odd.
Anyone?
Something might have happened that caused a rebuild of the Delvic cache. When that happens, it can take as long as a few minutes to boot, but it should only happen the first boot after the cache wipe. If the problem persists, you could try to factory reset your phone in recovery or just use ODIN to re-flash MF3 to your phone. I suggest you make sure to read and learn about whatever option you try and understand, there is always risk associated with trying anything.
After I rooted, I was having similar issues. But the phone would reset or power up fine if I had the cable plugged in. Eventually figured out is was the battery that was bad. Rooting before the problems started was just a coincidence. Check to see if adding power to USB helps.
I had never tried to clear my cache or reset my phone through system recovery until after I had already rooted. Neither of them worked for me though, it would just say error and then try rebooting. I also got stuck on the AT&T boot logo, but it was every time I tried to boot. I was stuck with my phone like this for about two months. I finnaly fixed it but its still rooted. I haven't wanted to attempt to unroot it and brick it again, so I haven't been able to discover if it only fails with root or not. I will attempt to after I get my 4.3 update from AT&T, which should unroot my phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 07:20 PM ---------- Previous post was at 06:53 PM ----------
I think I recall the cache problem occurring on even unrooted phones though. The AT&T boot logo issue should be a direct problem from root though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
midge23 said:
I had never tried to clear my cache or reset my phone through system recovery until after I had already rooted. Neither of them worked for me though, it would just say error and then try rebooting. I also got stuck on the AT&T boot logo, but it was every time I tried to boot. I was stuck with my phone like this for about two months. I finnaly fixed it but its still rooted. I haven't wanted to attempt to unroot it and brick it again, so I haven't been able to discover if it only fails with root or not. I will attempt to after I get my 4.3 update from AT&T, which should unroot my phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You will attempt to what?
As of now, there is no Root method available for 4.3 on AT&T. Maybe there will be one, but who knows how long it will take. You would be better off to ODIN MF3 back to your phone (if you are currently on MF3), do a factory reset, re-root, and see if it solves the problem. If not, you can always ODIN back to MF3 again and take the OTA when it rolls out. Whatever you do, make sure you read and learn about it first because there is always risk. Good luck.
There is an odin mf3? I thought I was reading in some of the threads that there was no odin flash for mf3 and that if you rooted, you had to be super careful, cause there was no way to fix any damage done. Did I miss a thread? Cause if I did, I wanna get that flash file, so this way I could start titanium backup removing some of the att bloat.
Also even when 4.3 OTA rolls out, I dont think we can odin back to 4.2 could we, isnt there something that prevents it from going back?
As for battery, its a brand new phone, so dont think it could be that.
-Dupe post-
Hi everyone,
So i'm a complete noob at this whole .. custom rom thing, and I just googled instructions, and followed them. Except now I think I may have lost my recovery mode ... everything.
I bought the phone off craigslist, and it had a 4.4 kitkat installed. But I didnt like it and wanted the stock version, so i tried installing 4.3 on it. Except now I cannot get past the samsung logo (not to mention the boot animation is not right) and I cant even get into recovery mode.
When i press the buttons I just get a "recovery booting' on the top left corner, the samsung galaxy s4 logo for about 5 seconds and then everything turns off.
HELP! Ive not even had this phone for 24 hours yet!
I tried using Kies and Odin to get the roms to install, but I think theres something wrong with recovery or the boot.. both kies and odin say that the installation was successful, but I cannot get past boot or get into recovery at all. (i can get into download fine)
I read about the whole mf3 soft-bricking but I'm using a i337m phone, the Canadian one. is there a chance that that could happen to me too? I didnt check which version I was using before I tried odin because stupid me thought that all i337m devices work the same.
Best course of action would be to download the complete stock ROM and modems. As much stock as you can find. There's a thread for all the customs. Boot into download mode, then use Odin to flash the ROM.
If it then fails to boot ... try flashing CWM and reboot into recovery ... erase and restore all data and hope for the best.
ChrisDuffy20 said:
Best course of action would be to download the complete stock ROM and modems. As much stock as you can find. There's a thread for all the customs. Boot into download mode, then use Odin to flash the ROM.
If it then fails to boot ... try flashing CWM and reboot into recovery ... erase and restore all data and hope for the best.
Click to expand...
Click to collapse
Ok, so I tried using a 4.2.2 stock ROM, and now I got recovery to work... Except I can't get wifi to work and i now have..
"kernel not seandroid enforcing
set warranty bit: kernel"
I also tripped Knox... (cannot reset?)
Is the whole kernel thing a problem? and How should I go about trying to get back wifi? Would it be a bad idea to use Kies or Odin to install 4.3 over what I have now, now that I have recovery working again?
For WiFi flash mf3 module files on safe strap forum
mf3 rooted SHOstock
chiynadoll said:
Ok, so I tried using a 4.2.2 stock ROM, and now I got recovery to work... Except I can't get wifi to work and i now have..
"kernel not seandroid enforcing
set warranty bit: kernel"
I also tripped Knox... (cannot reset?)
Is the whole kernel thing a problem? and How should I go about trying to get back wifi? Would it be a bad idea to use Kies or Odin to install 4.3 over what I have now, now that I have recovery working again?
Click to expand...
Click to collapse
I would definitely go back as far stock as you can if you just want essential functionality. However, if you want something fun....there's no harm in putting it to a custom ROM / Kernel / Modem
I personally use MDOB (stock, rooted and runs my Galaxy Gear) with Toonzez (sp?) Kernel.
Check the MDOB thread. I was given a lot of help by members in there on the last few pages.
Do factory data reset, and without letting the phone boot into OS pull battery and Odin flash 4.3 official software
chiynadoll said:
Ok, so I tried using a 4.2.2 stock ROM, and now I got recovery to work... Except I can't get wifi to work and i now have..
"kernel not seandroid enforcing
set warranty bit: kernel"
I also tripped Knox... (cannot reset?)
Is the whole kernel thing a problem? and How should I go about trying to get back wifi? Would it be a bad idea to use Kies or Odin to install 4.3 over what I have now, now that I have recovery working again?
Click to expand...
Click to collapse
Knox cannot be untripped, nor will it ever. So forget that idea. Flash a stock firmware with odin, reroot, and go from there. Easiest way to get kernel back stock if you're new to odin and flashing in general. Tick auto - restart in odin, use pda button in odin to select the firmware, and flash. Lots of guides with steps and captures to assist with odin around here. Check out a return to stock thread for your make /model/region
Sent from my SGH-I337M
Just so you know. If you update OTA or via kies to the stock firmware you will no longer be able to flash custom ROMs anymore. I would download a custom 4.3 TW ROM. For your WiFi issue I would check your APN setting under more networks.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hey everyone,
So after a whole month, I still haven't gotten anywhere. I managed to get an OS onto the phone so that its no longer "soft bricked" but it cannot connect to wifi, and can't call. The call goes through, but then the phone freezes. It also will be lagging for a long time after the call attempt.
I'm wondering if I should just try flashing it a couple of times again with a custom rom since I can't use kies? Btw, I dont know if this is possible, but i feel like i might have lost stock recovery. I can't factory reset, or anything that has to do with recovery what so ever. It just does not exist on this phone.....
Bricked SG4
I have the Samsung GS4 i337 mk2 v4.3 (rooted) for a month and ending up with just the wait..... android downloading, don't know if that is a hard or soft brick, but took it to the AT&T distribution center in Portland, Or and they flashed it back to stock, FREE, no questions asked. Just though everyone would like to know.
I am having the same issue
ChrisDuffy20 said:
I would definitely go back as far stock as you can if you just want essential functionality. However, if you want something fun....there's no harm in putting it to a custom ROM / Kernel / Modem
I personally use MDOB (stock, rooted and runs my Galaxy Gear) with Toonzez (sp?) Kernel.
Check the MDOB thread. I was given a lot of help by members in there on the last few pages.
Click to expand...
Click to collapse
ChrisDuffy20 said:
Best course of action would be to download the complete stock ROM and modems. As much stock as you can find. There's a thread for all the customs. Boot into download mode, then use Odin to flash the ROM.
If it then fails to boot ... try flashing CWM and reboot into recovery ... erase and restore all data and hope for the best.
Click to expand...
Click to collapse
I still want to go with something like slim or carbon so can I use odin and just flash the rom I have on my comp??
SaHiLzZ said:
Do factory data reset, and without letting the phone boot into OS pull battery and Odin flash 4.3 official software
Click to expand...
Click to collapse
JLopez149 said:
Just so you know. If you update OTA or via kies to the stock firmware you will no longer be able to flash custom ROMs anymore. I would download a custom 4.3 TW ROM. For your WiFi issue I would check your APN setting under more networks.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can someone post a link to some stock firmware... I've looked for hours
Tank you