Hello everybody
I'm having this random issues with my Galaxy S5 G900F (Klte) with custom and stock roms.
Boot loops some times (System or Recovery)
Freezes at Logo or booting system or booting recovery.
Spontaneous reboots on recovery or system, at start or sometime later.
Some times it reach the PIN screen and sometimes not.
Some times it works for hours and some times it is rebooting all the time.
It happens from some days ago when I did a restore from custom rom backup.
It was taking a long time booting to system (more than 1 hour) so I removed the battery.
When I tried to start again the phone was not working well. (Just rebooting all the time)
I tried to solve it by flashing my previous used Stock Roms with Odin v3.09 with the result = <OSM> All threads completed. (succeed 1 / failed 0)
KitKat - G900FXXU1ANE2_G900FOXX1AND3_G900FXXU1ANE2_HOME
Lollipop - G900FXXU1BOJ1_G900FPHE1BOJ1_G900FXXU1BOJ1_HOME.tar
Marshmallow - G900FXXS1CPG9_G900FPHE1CPE3_G900FXXU1CPC9_HOME.tar
I also tried with custom Roms: RR pie, Bliss 12.7, Crdroid...
Sometimes I'm having errors while flashing custom Roms but sometimes everything be correct.
I also tried repairing, wiping and formatting every partition to ext2 and ext4
For some times I'm having problems wiping and formatting some partitions (randomly): unmount partition or no such file or directory...
I also tried with Original recovery and TWRP 2.x, 3.2 and 3.3 with the same results.
And also tried with and without SD and SIM
I don't know what more can i do. Some idea would be nice.
Aditional info:
My battery only have 7 months.
Is there any way to full clean all the phone partitions memory or any else?
Is Odin cleaning the phone during the installation of a new Rom or it is leaving some untouched?
How is posible that after install a Stock Rom with Odin with success end the mobile being unstable?
I'm doing a lot of tests because I don't understand the cause of my phone is unstable, but I'm learning a lot trough internet.
Some of the tests I'm doing are having this unespected results: (I could update this)
Boot loop entering to recovery mode
Cause: Unknow
Solution 1: Some times works better when I maintain pressed Vol+ and home until the TWRP screen si shown. (But not allways)
Solution 2: Some times I need to remove the battery, wait some minutes and try again after before entering in recovery. (Some times I need to repeat the proccess)
Boot loop entering to system
Cause: Partition system can't be repaired and shows "unable to mount partition" error on TWRP (May be the files or the partition is damaged or lost)
Solution: The only way I found is enter in recovery mode and clean system/dalvik/cache then install the Rom again. (Don't need to wipe data if it's the same Rom/Gapps)
Cause: Unknow
Solution: Sometimes the mobile enter to system after some tries
I also want to share some knowledge with the people that are looking for solution of similar problems and they found this post.
Some usefull guides I found: (I could update this)
A nice guide about Odin: https://pakfones.com/what-is-odin-and-how-to-use-full-guide/
What about nand erase on odin?: https://www.droid views.com/nand-erase-odin-samsung-firmware/
A nice program to get 4 part firmwares (SamFirm): https://samfirmtool.com/samfirm-v0-5-0 (The guide in the same site. )
Nothing new but , how to flash 4 parts firmware: https://rootsamsung.com/flash-samsung-stock-firmware-4-files
How to extract PIT from 4 Part firmwares (Easy way): https://www.droid views.com/extract-samsung-pit-file-from-firmware/#Extract_Samsung_PIT_File_from_Samsung_Firmware
Backup EFS/NV_data (Manual): https://forum.xda-developers.com/showthread.php?t=2737448
Something new, What is Combination Firmware?: https://combinationfile.us/what-is-samsung-combination-file-firmware/
Remove the space on URLS between droid and views.com
I don't see any diference between 1 part and 4 part firmware.
I think the Combination Firmware is only a little versión of Android (not much useful to fix nothing)
The same tools inside Combination are also on Development options in every Rom.
All credits of the guides/programs to their creators/maintainers. (I've only collected it here)
I will edit this post to not spaming the forum with the news.
Testing 4 parts Firmware obtained from SamFirm:
AP_G900FXXU1CRA2_CL12884729_QB16534923_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G900FXXU1CRA2_CL12884729_QB16534923_REV00_user_low_ship_MULTI_CERT.tar.md5
CP_G900FXXU1CQK3_CL12557498_QB15704233_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_PHE_G900FPHE1CRB1_CL12989714_QB16755881_REV00_user_low_ship_MULTI_CERT.tar.md5
But nothing really special, the phone continues restarting.
Testing 4 parts Firmware + PIT + re-partition + NAND Erase All
Nothing new, same reboot problems booting system.
At this point I have less reboots entering in recovery mode but:
Sometimes i have errors when I install custom Rom (E1001: Failed to update system image. and Error:7)
Stock roms boot loops everytime while booting system. (1 Part Firmware, 4 parts, with or without NAND Erase and PIT)
Custom roms like Bliss 12.7 works some times but without gapps.
I can't install Gapps now because errors / freezes at recovery.
Since the latest Stock Firmware installation I have more problems:
Black screen after Samsung logo.
More dificulties to enter on Recovery
Cannot solved by flashing any Stock Firmware.
Hardware buttons are good, and is not problem of overheats. (Works bad also in a cool state)
Going to SAT next monday.
Related
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!
Hi,
I initially had G935FXXS3ERHD_G935FXEO3ERG2_XEO installed and flashed Glamour ROM S9+ port some time ago, now i need to return it to stock but no luck...
Using latest odin i flashed:
G935FXXU3ERL3_G935FXEO3ERKF_XEO
and
G935FXXU3ERJE_G935FXEO3ERJF_XEO
(i need to remain on 3 bootloader)
after each flash i receive the NO COMMAND screen, and cannot boot into stock recovery... only way to boot the phone is to install TWRP... I have noticed when i plug the phone is it comes up as GALAXY S9+ so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
i have no idea what else to try
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try
hello ive samsung galaxy s3 alpha (SC-03E) and im having a big problem with it sicne it it stuck on boot and keeps rebooting every time
i tried flashing stock room as well as flashing a full firmware (4 files ) that was suppose to fix to the problem but nothing changed
any solutions
I NEED TO ROOT/UNLOCK THE PHONE
But i cannot check box (USB Debugging) because my S3 i9300 is Soft-Bricked, i have other S3 with similar problems...
Cannot install any rom because they are LOCKED in Soft Brick.
Tryed many tools like Octoplus, JurassicTools, Kies.... (Thinking to try on MiracleBox and ReiBoot too)
FACTS:
- I CAN ENTER ON RECOVERY MODE (e3) ADB SIDELOAD/ DOWNLOAD MODE etc...
- BOOTLOOP SCREEN
- NAND Write/PIT File Errors on ODIN(Test in all versions)
Someone Help , i ve seeing many people with this problem or similar ~
Thanks for your attention,
and cooperation o/
Try to write recovery after writing rom
I encountered such a fact when writing a custom rom on my phone.
At that time, I could solve the problem by writing a custom recovery after writing the custom rom.
The custom recovery wrote as follows.
1. Press the Volume Down, Home, and Power buttons to wake up the phone in download mode.
2. Start Odin, specify a custom recovery file in "AP", and press the Start button.
The custom recovery used "sc03e-KBC-CWM-v6.0.5.1_r4-recovery.tar".
have no idea about this
Please help me out guys
I installed twrp pro 3.2.1-1 (https://forum.xda-developers.com/galaxy-j5/development/recovery-recovery-pro-galaxy-j5-2015-t3728264) on my J500FN (stock rom v6.0.1). It supports AROMA file manager. With twrp pro i installed [ROM][J500xx][TW-7.1.1][v5.0] SEPerience-ROM A8 2018 Port (https://forum.xda-developers.com/galaxy-j5/development/rom-sep-8-5-galaxy-a8-2018-rom-t3796971).
The ROM also started and ran without problems. Since I didn't like it, I installed Odin again with stock rom 6.0.1 (four-part version). I paid close attention to BL AP, CP and CSC. Odin reports sucessfull 1, failed 0. But now my phone still gets bootloop at samsung logo. I also tried v5.1.1, but bootloop at samsung logo here too. But it is the right firmware (SM-J500FN_1_20190207155114_slzx5q4t70_fac.zip). Exactly the same with stock rom v5.1.1.
I am at the end of my knowledge . Please help.
knipsmoped said:
Please help me out guys
I installed twrp pro 3.2.1-1 (https://forum.xda-developers.com/ga...ecovery-recovery-pro-galaxy-j5-2015-t3728264) on my J500FN (stock rom v6.0.1). It supports AROMA file manager. With twrp pro i installed [ROM][J500xx][TW-7.1.1][v5.0] SEPerience-ROM A8 2018 Port (https://forum.xda-developers.com/galaxy-j5/development/rom-sep-8-5-galaxy-a8-2018-rom-t3796971).
The ROM also started and ran without problems. Since I didn't like it, I installed Odin again with stock rom 6.0.1 (four-part version). I paid close attention to BL AP, CP and CSC. Odin reports sucessfull 1, failed 0. But now my phone still gets bootloop at samsung logo. I also tried v5.1.1, but bootloop at samsung logo here too. But it is the right firmware (SM-J500FN_1_20190207155114_slzx5q4t70_fac.zip). Exactly the same with stock rom v5.1.1.
I am at the end of my knowledge . Please help.
Click to expand...
Click to collapse
Try rebooting to stock recovery and do a factory reset. Your data should have already been formatted by installing stock theough but just in case try this
When starting stock recovery, the message "installing system update ..." appears and shortly thereafter "no command.", before the recovery menu appears.
I did "wipe data / factory reset" and "wipe cache partition" and then "reboot system now". Unfortunately a bootloop at the samsung logo ::crying:
I don't understand what I did wrong. I have already flashed some Samsung smartphones with new firmware. So far I always thought that flashing the stock rom firmware can fix everything.
knipsmoped said:
When starting stock recovery, the message "installing system update ..." appears and shortly thereafter "no command.", before the recovery menu appears.
I did "wipe data / factory reset" and "wipe cache partition" and then "reboot system now". Unfortunately a bootloop at the samsung logo ::crying:
I don't understand what I did wrong. I have already flashed some Samsung smartphones with new firmware. So far I always thought that flashing the stock rom firmware can fix everything.
Click to expand...
Click to collapse
That should be the case. Try a different version of Odin perhaps? I know people have issues with certain versions on certain devices
garylawwd said:
That should be the case. Try a different version of Odin perhaps? I know people have issues with certain versions on certain devices
Click to expand...
Click to collapse
I tried the following odin versions:
Odin3 v3.09
Odin3 v3.10.7
Odin3 v3.11.1
Odin3 v3.12.5
Odin3 v3.14.4
Always the same
After flashing, Odin reports suceed 1, failed 0.
The automatic restart begins with the Android logo and the messages "installing system update ...", "erasing", "installing system update ...". Then the device restarts up to the Samsung logo and then goes into bootloop.
I also always did "wipe data / factory reset" and "wipe cache partition" and then "reboot system now" via stock recovery, just before I rebooted the device. Alwas the same. At samsung logo bootloop.
I have attached 2 screenshots of the flash process (without errors).
I am at a loss. What else could be the reason? I hope you can give me more tips.
Update, second attempt.
I've added a few photos as I may be missing an important clue.
I don’t know, what i do wrong.
With ODIN v3.14 I flashed the right stock rom (picture 1) back, which was previously installed (picture 2). I paid close attention to BL AP, CP and CSC. Odin reports succeed 1, failed 0 (picture 3). But now my phone still restarting on samsung logo (it isn’t bootloop, sorry for the wrong description).
If I try to enter stock recovery - first it appears "installing system update", then "no command" and then it enter the stock recovery. I did „Wipe data/factory Reset“, „Wipe cache partition“ (picture 4) and then „Reboot system now“ (Successfully verify for dmverity hash tree). But no success. After the samsung logo lights up a few times, the smartphone restarts.
I installed again TWRP pro 3.2.1-1 (https://forum.xda-developers.com/gal...2015-t3728264).
TWRP pro – WIPE data, cache and dalvik. Okay.
TWRP pro – INSTALL [ROM][J500xx][TW-7.1.1][v5.0] SEPerience-ROM A8 2018 Port (https://forum.xda-developers.com/gal...rom-t3796971)- without any changes. Okay.
TWRP pro – Wipe cache/dalvik. Okay.
With TWRP - "Reboot System" I restarted the smartphone
After „Reboot System“ – no restart on Samsung logo; the setup process started and after selection language and beginning selection WLAN, the system reported stopped something and then restart
After a short time the setup process started again – selection language, selection WLAN, selection terms and conditions – restart without any report
After a short time the setup process started again – selection language, selection WLAN (was already set up), selection terms and conditions, Searching for updates …. Finished. The desktop appears. But then without a reason – restart
After a short time the setup process started again – selection language, selection WLAN (was already set up), selection terms and conditions, Searching for updates …. Finished. The desktop appears. But then without a reason – restart
After a short time the setup process started again – The desktop appears immediately. And I can work with the smartphone perhaps 10 minutes – but then restart without any report
Can the error be further narrowed down? Is it a hardware or a software problem?
And the sim-card is not recognized.
I am at a loss.
And i don't know, why the pictures are not displayed
I bought a used motherboard. Problem solved.