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
Related
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.
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?
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.
My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Re-download the stock rom and flash it
Meboyzram said:
Re-download the stock rom and flash it
Click to expand...
Click to collapse
i did that lol thats when it says "model dismatch fail"
Do you have custom recovery?
Do you have a custom recovery?
Do you have the right and the newest Odin Version?
Did you try it with another transfercable or USB-Port?
Do you have the newest samsung drivers?
Did you have any Odin problems like this before?
My suggestion:
Just do a full wipe on your phone. Downlad the newest Odin Version. Get your device into download mode (maybe try different transfercables or USB Ports and the newest samsung drivers) and see if it works now.
If yes, flash the right Bootloader and Modem for your device and then flash the rom you wanted to flash.
If this didnt work, (and you have a custom recovery) try to reinstall the rom without any backups via the recovery at first and check afterwards, if the device is now recognized by Odin.
Good luck
JustAnotherAndroid said:
My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Click to expand...
Click to collapse
I guess you still have twrp installed.
1. Step: go to TWRP and wipe everything except your SD-Card
2. Step: enter download mode on your device and then plug your usb in (maybe try a different usb-port or even another computer, or another usb cable)
3. Step:Flash the newest bootloader & modem in one step.
4. Step: Enter TWRP again and flash the firmware.zip via the installation process
I dont have TWRP, but i got it fixed, somehow my roomate got it, thanks anyways guys
So all he got was my phone to turn on, im still having this model dismatch fail issue..
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
ProtoDeVNan0 said:
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
Click to expand...
Click to collapse
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
If system.img by itself will flash successfully and Your phone won't boot then add slowly more files to that tar file (boot.img, recovery.img etc)
You could also try looking for a pit file for Your phone and then flash it with it. Pit file usually fixes most problems even broken partitions.
And make sure that You put that tar file in AP/PDA.
If nothing above works then send me screenshots of ODIN and the file that You're trying to flash. Maybe I'll notice something. But I hope You'll fix it
JustAnotherAndroid said:
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
Click to expand...
Click to collapse
So I tried, and i get some invalid file error
These are the files that are in the AP one
https://gyazo.com/a72785631ad62d412a8c40eb464d3126
I found out my problem, i was still uing the modified version of odin that i used to root my phone
Hi,
My phone has TWRP installed and I have tried getting into recovery with vol up, home and power but I just get stuck on the regular boot screen (Samsung Galaxy S5 with Set Warranty Bit: Kernel). I have tried using Odin to flash TWRP in download mode (no Pit file error) which fails. I can't get my device to show up in adb or fastboot. I can't enable USB debugging because my device won't boot.
The only mode I can get into is download mode (vol down, home and power). Is there any hope of getting into recovery or accessing my files from there?
I have read through countless threads and posts without finding a solution. I really appreciate any suggestions.
Device: SM-G900T
zanmat0 said:
Hi, My phone has TWRP installed and I have tried getting into recovery with vol up, home and power but I just get stuck on the regular boot screen (Samsung Galaxy S5 with Set Warranty Bit: Kernel). I have tried using Odin to flash TWRP in download mode (no Pit file error) which fails. I can't get my device to show up in adb or fastboot. I can't enable USB debugging because my device won't boot...
Click to expand...
Click to collapse
I don't have this variant but, your best bet is to post this question within the following Official TWRP thread for your device.
https://forum.xda-developers.com/showthread.php?t=2727406
If all else fails, try posting your question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
zanmat0 said:
............
The only mode I can get into is download mode (vol down, home and power). Is there any hope of getting into recovery or accessing my files from there?
.........
Device: SM-G900T
Click to expand...
Click to collapse
Hi,
That's not a good symptom.
Just to be sure:
Did you try installing full stock firmware from odin via download mode?
Does download mode confirm that your phone model is SM-G900T? Is that model in line with a label under the battery?
Many40 said:
Hi,
That's not a good symptom.
Just to be sure:
Did you try installing full stock firmware from odin via download mode?
Does download mode confirm that your phone model is SM-G900T? Is that model in line with a label under the battery?
Click to expand...
Click to collapse
I tried installing TWRP with Odin, if I install stock firmware, will all my data be wiped? All I wanted was to get into TWRP to save the data.
Yes download mode confirms SM-G900T same as under battery.
zanmat0 said:
I tried installing TWRP with Odin, if I install stock firmware, will all my data be wiped? All I wanted was to get into TWRP to save the data.
Yes download mode confirms SM-G900T same as under battery.
Click to expand...
Click to collapse
The question is what happened before that your phone doesn't boot?
If a phone doesn't boot the basic way to fix it is to reflash it with stock firmware. It will not wipe your files in internal storage like pictures, downloads etc but it will most likely wipe your apps, settings, contacts, messages etc.
By the way what version of TWRP have you tried installing?
Many40 said:
The question is what happened before that your phone doesn't boot?
If a phone doesn't boot the basic way to fix it is to reflash it with stock firmware. It will not wipe your files in internal storage like pictures, downloads etc but it will most likely wipe your apps, settings, contacts, messages etc.
By the way what version of TWRP have you tried installing?
Click to expand...
Click to collapse
OK I tried reflashing with stock firmware, but same error "There is no pit binary. Flash read failure".
TWRP 3.2.1.
The thing is I'm not sure what happend because my screen broke, the phone was still working fine but I tried to reboot into recovery without a functional screen many times, perhaps some combination of buttons I pressed bricked it...
zanmat0 said:
OK I tried reflashing with stock firmware, but same error "There is no pit binary. Flash read failure".
TWRP 3.2.1.
The thing is I'm not sure what happend because my screen broke, the phone was still working fine but I tried to reboot into recovery without a functional screen many times, perhaps some combination of buttons I pressed bricked it...
Click to expand...
Click to collapse
Try to falsh this firmware only file with TWRP and pit (use AP slot in Odin): https://mega.nz/#!XksGAThB!oQnTcnp7YHJfEfekbQMaihm2SGItBNMihPPfzQehUq4
You cannot brick the phone with just a buttons' pressing.
To say the truth, your story sounds like a memory failure and there's almost no chance to get your data.
bbsc said:
Try to falsh this firmware only file with TWRP and pit (use AP slot in Odin): https://mega.nz/#!XksGAThB!oQnTcnp7YHJfEfekbQMaihm2SGItBNMihPPfzQehUq4
You cannot brick the phone with just a buttons' pressing.
To say the truth, your story sounds like a memory failure and there's almost no chance to get your data.
Click to expand...
Click to collapse
Same error looks like (There is no PIT binary).
I see, well in any case, thank you very much for your help. Its bizarre because the phone was working fine as the screen was slowly breaking up until it finally went dark forever.
A bit late to the party, but I found my GS5 wouldn't go into recovery if the USB/Charge cable was plugged in.
zanmat0 said:
Same error looks like (There is no PIT binary).
I see, well in any case, thank you very much for your help. Its bizarre because the phone was working fine as the screen was slowly breaking up until it finally went dark forever.
Click to expand...
Click to collapse
If Odin is requiring the PIT file for the SM-G900T device, you can obtain it on the following link.
Downloads for : Samsung Galaxy S5 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
The PIT file is the Partition Information Table that Odin uses for what goes into which partition from the Firmware.
I hope I had explained this okay via text.
There's a little helper guide on the following thread as well.
[FIRMWARE/PIT]T-Mobile Samsung Galaxy S5{SM-G900T/KLTETMO}[ODIN]
OFFICIAL FIRMWARE/PIT COLLECTION T-Mobile Samsung Galaxy S5 {SM-G900T/KLTETMO} {The above image is a refrence of all the Stock Firmware, Release Dates, etc...} CLICK HERE TO EXPANDED THE ABOVE IMAGE DISCLAIMER/FYI - This thread DOES...
forum.xda-developers.com
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. [Sent from the room next door.]
Many40 said:
Hi,
That's not a good symptom.
Just to be sure:
Did you try installing full stock firmware from odin via download mode?
Does download mode confirm that your phone model is SM-G900T? Is that model in line with a label under the battery?
Click to expand...
Click to collapse
Just an FYI...
The attached image is an example of where to locate the actual model number of your device (which is the second line down from the top of the screen).
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. [Sent from the room next door.]