I recently ran into difficulty wherein my emulated/0 partition was borked after using TWRP recovery. In an effort to fix it I reformatted a partition (no idea which one I just followed some terminal commands from someone with a similar issue) and now the phone displays a brief message about being in factory mode (comes on for two-three seconds then disappears) and shuts off WiFi. Once I enable it the phone is fine.
I have looked at the various fixes for this but when I went into the efs / factory mode folder the two files mentioned in all the fixes are not there. I created them and gave them owner information, but this does not help.
Any thoughts? Would a flash back to stock solve this?
Hopefully you didn't just randomly delete the EFS partition without backing it up first
--
Try flashing stock ROM with the correct PIT file
*Detection* said:
Hopefully you didn't just randomly delete the EFS partition without backing it up first
--
Try flashing stock ROM with the correct PIT file
Click to expand...
Click to collapse
@*Detection* Will flashing the stock ROM replace the PIT file? Again, I don't know what partition was formatted. The factory mode overlay briefly displays then dissapears. The phone is fully functional and has not lost it's identity, just the annoyance of having to turn WiFi back on. Other than that, I do not know what other functions are limited (as it says on the factory mode overlay).
Mordred said:
@*Detection* Will flashing the stock ROM replace the PIT file? Again, I don't know what partition was formatted. The factory mode overlay briefly displays then dissapears. The phone is fully functional and has not lost it's identity, just the annoyance of having to turn WiFi back on. Other than that, I do not know what other functions are limited (as it says on the factory mode overlay).
Click to expand...
Click to collapse
The PIT file will repartition the phone, then the stock ROM will be flashed
Load them both into ODIN at the same time
Try flashing just the stock ROM first, could just be something messed up
If the phone works, and has an IMEI, then the EFS partition sounds like it's safe (Back it up ASAP)
http://forum.xda-developers.com/showthread.php?t=2705524
Any ideas on how to rid of the factory mode overlay? If not I will flash stock then rebuild again.
Not had any experience with factory mode before, so no unfortunately
There is a thread about Demo Mode kicking about
*Detection* said:
Not had any experience with factory mode before, so no unfortunately
There is a thread about Demo Mode kicking about
Click to expand...
Click to collapse
No worries and thank you for the replies. I will give it one more time.
Any thoughts on TWRP borking up the emulated/0 partition? Seems to happen everytime I do a backup (or soon thereafter).
Not had any problems with TWRP, flashed it on about 4 different ROM builds and it's worked fine each time
Sure you're flashing the latest?
I use TWRP Manager from G Play after rooting with CF Auto Root to flash it on mine
*Detection* said:
Not had any problems with TWRP, flashed it on about 4 different ROM builds and it's worked fine each time
Sure you're flashing the latest?
I use TWRP Manager from G Play after rooting with CF Auto Root to flash it on mine
Click to expand...
Click to collapse
I am, 2.8.0
I will give this app a try though.
Mordred said:
I am, 2.8.0
I will give this app a try though.
Click to expand...
Click to collapse
Looks like 2.8.6.0 is the latest
https://dl.twrp.me/klte/
But the TWRP Manager app will install the latest anyway
*Detection* said:
Looks like 2.8.6.0 is the latest
https://dl.twrp.me/klte/
But the TWRP Manager app will install the latest anyway
Click to expand...
Click to collapse
Correct, that is what I am running. I could not remember the last digit without going back into recovery.
@*Detection* What are the lines of text that display when you first boot into recovery on your phone? I am curious because mine says something about not running seanandroid, or something to that effect. They dissapear pretty fast but I think that is what is in red text.
Mordred said:
@*Detection* What are the lines of text that display when you first boot into recovery on your phone? I am curious because mine says something about not enforcing selinux, or something to that effect. They dissapear pretty fast but I think that is what is in red text.
Click to expand...
Click to collapse
Same, just means you're running custom
@*Detection* After I revert to stock, assuming everything goes back OK, can I then obtain root and re-flash my custom ROM and then do a restore from the backup I am making now? Would this (the restore) defeat the purpose of what I am doing?
"secure check fail : pit"
This is what I get when I try to repartition with an extracted pit for this phone. Any ideas how to make it work?
Related
I have an ATT i337 S4 (mdl baseband) running on T-mobile. Current setup was wicked 7.0 ROM with ATT kernel.
I was trying to change to cyanogenmod ROM and tried using my TWRP 2.5.0.2 to load the rom but it would flash it and gave me an md5 error. Supposedly this is a known issue with TWRP so most people recommend using clockworkmod recovery and I tried to load that using recovery tools. Recovery tools couldn't find the CWM image file but did find the 2.6.3.0 updated TWRP image file so I tried to update TWRP and when I did, I can't boot to recovery anymore and instead get the yellow triangle saying unauthorized software.
At the same time (ugh) I flashed wicked 8 ROM update and think I loki'd it (I am running wicked 8.0 now) but I forgot to run the att kernel afterward. The current kernel is 3.4.5 ... dirty ptmr3 ... N5110 #1. I think this is the standard t-mobile kernel which will obviously not work on my ATT phone.
The problem is, now I can't reboot into recovery mode. When I try, I get the yellow triangle "system software not authorized by ATT...". I don't know if the problem is with the bad kernel or with the updated 2.6.3 TWRP. The only way I can get around the bootloader problem is the hold down the down vol and home button, then the power button and that gets me into a "Warning a custom OS can cause critical problems ..." page. From there if I continue, I get the yellow triangle. If I hit the volume down button to cancel, it boots normally but not into the bootloader and I have partial functionality of my phone.
Where do I go from here? Odin to stock? Replace the bootloader somehow? Anything else?
I did do a nandroid of my system before all of this but for some reason I can't access my SD card. I can hit mount but nothing shows up on file manager. Will that backup replace the bootloader with the known good one? I could copy the backup to the phone memory and do it from there using titanium backup I think.
Thanks,
odin back to stock and then wipe/clear then retry should fix this problem
lilg754367 said:
odin back to stock and then wipe/clear then retry should fix this problem
Click to expand...
Click to collapse
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
colorchange said:
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
Click to expand...
Click to collapse
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
colorchange said:
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
Click to expand...
Click to collapse
I'm guessing I might be able to modify the open boot script and change to the old version but I don't know how to do this.
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
lilg754367 said:
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
Click to expand...
Click to collapse
Thanks lil, i know the kernel I want and have it downloaded. Right now I am downloading the tar file to get me back to stock. I was hoping to do something easier but crud...
yea no problem just hit the thanks button for me good luck
I can't get Odin to talk to my device. When it is not in download mode, Odin sees it but hangs and can't communicate. When I connect it in debug mode (very hard to get into download mode), Odin can't see it.
Help!
Hi guys,
I've got a problem. On Tuesday I was updating my apps on Google Play - I've updated some apps and started just to use them. One of them was popular messenger in Poland. Something's went wrong and my smarthphone freezed. I pulled out the battery after few minutes to prepare a 'soft reset', but it stucked on bootloop. I've tried to make a wipe /data, but it couldn't even mount /data, so I decided to change the ROM from networks' one to newest stock one (one file rom). Everything's went good, but it still stucks on bootloop on another boot animation. I've tried also repartitioning it using the stock rom with "totoro_0623.pit" - still the same. Wiping data after flashing didn't give any change.
When the phone was restarting after the last flash, they was written that /data can't be mounted (invalid arguments).
I don't know what should I do right now. Do you have any propositions for me?
Thanks in advance!
you can try with my firmeware
download
http://d-h.st/FhE
unzip the file
put phone into download mode
connect to pc
start odin
put the files in the following places in odin
pda in pda
modem in phone
csc in csc
begin flashing
do not remove the cable untill the phone has fully booted
it will enter stock recovery and flash csc and restart itself so leave cable connected
this firmware is a wipe pack so it should wipe all your partitions
if it fails you can try with the pit file but do not tick the repartition box in odin or you will be in trouble as you need to also include bootloader files for that
marcussmith2626 said:
if it fails you can try with the pit file but do not tick the repartition box in odin or you will be in trouble as you need to also include bootloader files for that
Click to expand...
Click to collapse
Thanks for reply.
Is it recognized as a stock rom? And the second question: what should I do when I have tick on 'repartition'? What changes will be done then? I thought it's just repartitioning and the bootloader is still the same, without any changes.
Ult1me said:
Thanks for reply.
Is it recognized as a stock rom? And the second question: what should I do when I have tick on 'repartition'? What changes will be done then? I thought it's just repartitioning and the bootloader is still the same, without any changes.
Click to expand...
Click to collapse
if you tick repartition it will wipe your boot partition and your phone wont be able to boot which is why you have to put bootloader files in
you dont need to repartition - in all the times iv flashed stock roms iv never had to do it
That link is for stock room firmware XXMI1 on baseband XXMC2 - its european firmware but will work on any gt-s5360 to get it working
You can always change to another baseband if you find you have no network by flashing a stock rom from your region
Sorry but I didn't have enough time to prepare it in this week. As I saw, I probably need also the bootloader files. Can somebody point me which one will be good? And another question: after changing bootloader the counter on downloading mode will be incremented?
Ult1me said:
Thanks for reply.
Is it recognized as a stock rom? And the second question: what should I do when I have tick on 'repartition'? What changes will be done then? I thought it's just repartitioning and the bootloader is still the same, without any changes.
Click to expand...
Click to collapse
This is a firmware and bootloader provided, I had same problem 4 days ago and this helped me alot
Sent from my GT-S5360 using xda premium
Somebody who tried to repair this phone ticked 're-partition' in my case, but this pack has helped me a lot. Thank you guys, you're amazing.
Hello all,
I have a S4 in my hands.
Now the history of the Phone is as follows:
Customer tried to take out the sim card by force. And broke the metal plate.
Yesterday I replaced the microsim/sim slot. Testing the full Phone and ready to go.
Today I go back to the end customer for the same device.
It keeps rebooting after the samsung galaxy S4 white screen. And keeps going.
This is what I tried:
Updating to newest rom - no luck
Plugigng in into pc by cable - keeps rebooting with only showing the battery icon.
Try to go in recovery mode - not possible
Going into download mode - works
The little smash trick of YouTube (smash to table gently with side of power button down) - don't work
Any suggestions?
So you are the employee that fixes phones and don't know what to do with a bootloop, but do know how to replace a simslot? I am somewhat confused..
A bootloop always has some cause.. check init.d script or so.
Code:
adb wait-for-device
adb shell chmod 000 /system/etc/init.d/*
at least get an adb connection and logcat,
Code:
adb wait-for-device
adb logcat -C
else you cannot say anything about the problem since you don't know the cause. (if debugging is disabled unpack boot.img and make changes in ram disk for enabling debugging/adb, then repack and reflash)
If download mode works just flash a custom recovery first, make a nandroid backup (make sure you secure the files whenever possible, since there is the nasty symlink "/data/media/" which is actually just /sdard. so if you wipe data manually it the nandroid backup will be gone), then try to do factory reset, if it doesn't work still, just reflash stock rom with odin + factory reset.
oh and for the record, the simslot being broken is not the cause of the bootloop, just that you know.
Hi,
When you say "updating to newest ROM" do you mean that you flashed stock ROM again via Odin? If not, then that's my suggestion for you, but first I'd try factory resetting it via stock recovery.
~Lord
Thank you for Your kind reply.
Yes indeed, I fix a lot, but I have and know my limits. . I've tried a lot to pass the boot loop.
But if it's not possible to fix it for me. Than its better to ask.
I will try a custom rom. And keep you informed. Thank you.
Installing a rom with odin din't help. I got na Green PASS but bootloop keeps running.
Installing CWM did not help allso, it give me a PASS, but I can't enter recovery.
So, how do I get acces to init.d ?
If recovery mode doesn't work and the device keeps rebooting, try to flash stock ROM with Odin and put the .PIT file after checking 'Re-Partition'
iJo09 said:
If recovery mode doesn't work and the device keeps rebooting, try to flash stock ROM with Odin and put the .PIT file after checking 'Re-Partition'
Click to expand...
Click to collapse
Thank you, I will try.
Can you give me a link to a stock rom with a pit file including?
The Chaser said:
Thank you, I will try.
Can you give me a link to a stock rom with a pit file including?
Click to expand...
Click to collapse
ROM and PIT file vary by model. What is the S4's one?
iJo09 said:
ROM and PIT file vary by model. What is the S4's one?
Click to expand...
Click to collapse
I have I9505
In this thread http://forum.xda-developers.com/showthread.php?t=2265477 you can find what you need. Flash the latest German XXUGNF1 firmware and use the .PIT file provided in the thread
iJo09 said:
In this thread http://forum.xda-developers.com/showthread.php?t=2265477 you can find what you need. Flash the latest German XXUGNF1 firmware and use the .PIT file provided in the thread
Click to expand...
Click to collapse
Just ready. got a green pass in odin. But still the same, and not able to go in recovery.
Maybe a hardware malfunction? Can I test that somewhere?
Retry with the same procedure a couple of times... if this doesn't solve problems, then it's an hardware fault
Solace50 said:
is there an odin file that can wipe the device clean as does twrp since for some odd reason i cant flash twrp, i think its due to samsungs bootloader puts on write protection if somethings out of place. though i did before and it worked fine. anywho i can boot into the os but have no functionality. i would assume i can still fix this through odin. i tired pushing a ota tar from my carrier but still did not work. i figure if i can wipe the os clean from the phone then push the OTA again perhaps it would then show offical status again since that would also change the recovery back to stock as well.
Click to expand...
Click to collapse
essentially i need the i337m/m919v pit file "i assume they would be identical" to perform a clean wipe from odin of which i cant seem to find it posted anywhere.
i did however find
http://softwarearab.com/Flash File/SAMSUNG/PIT files for Samsung/i337M/
edit: all is well, least the url is on xda for others who may encounter the same issue. apparently i corrupted the recovery partition or something. after wiping/repartitioning with odin i could get into the stock recovery so i assume twrp should work as well now.
edit: apparently i cant find the delete button and accidentally quoted myself.
Was running Temasek's CM13 on a rooted, unlocked note 3. Somehow during a flash, I ended up with a restart to the Note 3 screen and hangs there. I always do a backup prior to my flashing, so there's one there but now there's no twrp for me to get to? Do I restart the process over (flash OS via Odin, reroot, reunlock, etc)? Or is there something different I need to do bc my phone is unlocked as a developer? Please help and thank you
?hang budged?
^^^ that's indecipherable; try again.
It is unlikely that you will need to start from scratch, but let's start with this:
Will the phone boot into *any* mode, including Odin Download mode?
Try pulling the battery, reinserting, and booting with
Vol-Up+Home+Power (recovery)
Vol-Down+Home+Power (Odin)
If you can get into Odin mode and it still says "Developer" you should be able to reflash twrp using Odin.
stoph8n24 said:
Somehow during a flash, I ended up with a restart to the Note 3 screen and hangs there.
Click to expand...
Click to collapse
OK, that's better than "hang budged"
stoph8n24 said:
...but now there's no twrp for me to get to?
Click to expand...
Click to collapse
You state that as a question... what happens when you try booting to the recovery or to Odin (download mode) using the button combinations as suggested?
Restoring a custom recovery to an unlocked bootloader phone using Odin:
Code:
cp twrp-3.0.2-0-hltevzw-4.4.img recovery.img
tar -H ustar -c -f OdinInstallTWRP.tar recovery.img
md5sum OdinInstallTWRP.tar >> OdinInstallTWRP.tar
mv OdinInstallTWRP.tar OdinInstallTWRP.tar.md5
Flash OdinInstallTWRP.tar.md5 using Odin (v3.0.9 or so) in the AP slot and be happy.
This ONLY works if the phone still has MODE: DEVELOPER showing on the Odin (Download) screen.
cheers
.
Lost developer mode, had to reinstall all the steps then insert my primary sdcard with the backup, then restore my last backup. Wasn't a hassle, just didn't know if I need to flash a something totally different since my phone is recognized as a developer now. Thank you, I did download twrp to flash in case it happens again.
stoph8n24 said:
Lost developer mode
Click to expand...
Click to collapse
The only way that would have happened is if you overwrote the bootloader with stock firmware ("aboot" in particular) or - even less likely - that your CID got changed somehow.
Unless you are saying that you intentionally flashed a full stock firmware set in Odin in order to effect the repair... then it would make sense.
What were you flashing that caused the original trouble?
bftb0 said:
The only way that would have happened is if you overwrote the bootloader with stock firmware ("aboot" in particular) or - even less likely - that your CID got changed somehow.
Unless you are saying that you intentionally flashed a full stock firmware set in Odin in order to effect the repair... then it would make sense.
What were you flashing that caused the original trouble?
Click to expand...
Click to collapse
I actually think I may have flashed the partial firmware instead of the modem firmware that I wanted. But looking at my laptop, I have firmware for so many different notes it's ridiculous. I wouldn't doubt that I just flashed the wrong file.