hi, i have a s21 fe thats in a weird bootloop that i cant figure out, hoping someone here has an solution. I can get into recovery/download mode. its a snapdragon SM-G990W on binary 3. ive tried reflashing stock W, no fix, tried U1, no fix, back on W. with flashing, it passes odin. in rocovery, an error shows up "[libfs_mgr] error updating slotselect". does it mean SD card slot, cause there isnt one. im not the original owner of the phone so I dont know what was exactly done to it prior the bootloop, just trying to fix. thanks for any information.
*P.S. I can post the recovery log if someone thinks it will help*
Recovery with smart switch does not work ?
Related
Hello there, all xda members.
I got Ace 2 to fix from my friend. He doesnt know exactly why did the phone becoming stuck on bootlogo. Maybe messing up with flashing GB or JB. or maybe wrong terminal command.
Ace 2 Condition :
- Its unable to pass boot logo samsung galaxy ace 2
- Its unable to enter recovery mode
- Its able to enter download mode, and its custom binary download : No, Current binary : Samsung official
Here all the thing that i have tried to fix the phone :
1. Flashing the phone with Russian Gingerbread with 3 files, Pit, CSC, and PDA. But it still stuck on bootlogo and unable to enter stock recovery. it shows succeed though on Odin, but it can't boot.
2. Flashing the phone with Latest Jelly bean, with Jelly bean pit file. Odin displaying succeed, but it doesnt boot either.
Can someone help me how to solve this problem?
Is there a condition where phone completely unable to recover from hardbrick such as stuck on bootlogo, but still able to enter download mode?
I'm going to download jelly bean mb2 or mb4 which include pit and csc from jelly bean and try to reflash it. Hope it gonna work.
Thanks for any help.
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
And if it really doesnt have a solution, maybe i'll just give it up. And doesnt continue researching to fix this phone. Thanks
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
It got the same case. Successfull flashing, but still doesnt boot, it just like flashing is fail. or it just like it reverted the way it was before flashing. Your help is very appreciated.
riyosakura said:
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
Click to expand...
Click to collapse
Very strange. And more strange is that several people have this "only boot to logo / only downloadmode issue"
Up to now I have no Idea - I asume that ADB is not working, because of missing recovery mode? With ADB there are plenty of possibilities.
An complete Factory reset could be helpfull - But how to do it out of downloadmode ?! Don't know.
Up to now I didn't had a Phone with this behaviour for repair at home. If it would be reproducible how this all happens, I would bring my phone to this state to find out how to repair it (riff box here - so dead ACE 2 is not a problem) - But even this is unclear - Every report regarding this said only "suddenly" "without any reason" "flashed this or that" - But no exact infomation what happend acctually.
I'm out of Ideas. Sorry!
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
riyosakura said:
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
Click to expand...
Click to collapse
Another try:
Flash with ODIN Ace2Nutzers Stock Kernel (search on FTP)
Do not let the Phone boot
After Flashing pull usb und press drictly the 3 keys to get into Rec. Mode
riyosakura said:
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
Click to expand...
Click to collapse
No, I haven't had the phone in such condition as described above. But I have heard that any odin-flashable file that's wrongly flashed via "Phone" entry can lead brick which is similar to this. I remember only one case - one user from 4pda has flashed some file via odin, wrongly putting file to the "phone", and wasn't able to restore it anyhow - but he also had some brick on GPIO side - vol.up worked like vol.down, and the real vol.down didn't work at all. I don't know however, what memory partitions / any devices capable of storing data would be messed after this operation, and whether it's reparable at all. I mentioned devices, that can also store data, I know only that touchscreen has small memory for its firmware(that what I had broke one day in the past after accidental firmware change in the kernel) - but maybe some other devices also has it?!
There are also some chances that it's dead flash memory - chances are pretty small, but should also be taken into account.
I have samsung note 2, Lately I was trying to flash a custom rom but I failed. So I tried to backup the previous rom but now I have a greater problem. It says md5 mismatch. And now I am stuck on boot screen and I have no idea how to fix it. I only have access to cwm recovery now. Please help me fix this. Also please give a solution that does not need any computer usage cause I dont have any with me right now. Been searching the internet for solution but nothing fix it. I'm totally panicked now.
Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
chrismin13 said:
Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
bubor said:
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
Click to expand...
Click to collapse
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
chrismin13 said:
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
Click to expand...
Click to collapse
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
bubor said:
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
Click to expand...
Click to collapse
Hello,
Sorry for the late response. I got around to trying most of that. First off the PIT File was something that I was looking forward to since it seemed the most likely solution. However it didn't work, giving out a similar message as everything else. The OneClick also failed with a similar message. As for heimdall I couldn't get the drivers to work but even if I had it wouldn't have helped anymore most likely.
I am out of ideas. I highly doubt this phone is recoverable at this point.
Thank you for all the help so far!
Anyone got any other ideas? I think it's safe to call it dead at this point, but I am willing to try anything to fix it!
Thanks.
Hi all,
so im coming here to ask you for a help.
Yesterday i have read about samsung pushing deactivating update for our notes 7, i have panicked and immediately started with installing TWRP, HydraRom and root to block incoming updates.
But, as i have already found out, my skills with android and flashing are already gone. So i have installed twrp, then rom and tried to reboot but phone was showing a lot of error messages and notification about low memory, which is weird. After couple of hours of seeking i have found out, that i should try to fix /data and /storage in TWRP by converting from EXT4 to ExFat... So i tried it, but phone suddenly died when it was repartitioning and now im stuck with note which is unable to boot or go to recovery. I can get into download mode yet when i try to flash anythin (whole rom, just bl, TWRP) odin shows immediately FAIL!
Does anyone know if there is way how to fix my note 7? I was thinking maybe a PIT file would help, but im unable to find one...
EDIT: Tried methods found here http://forum.xda-developers.com/note-7/how-to/fix-samsung-note-7-snapdragon-exynos-sm-t3443753 but no luck, same story with smartswitch as Odin, flash begins but immediately fails and note comes out of download mode.
So I have made decision, that I will add bounty - 50 bucks (will pay through PayPal) to anyone who will find way how to make my note work!
You should return your Note 7 to Samsung. Its safer and if want to do trial and error. I've found it possible to rescue any phone as long as you can put it in download mode ?
Sent from my SM-N930F using XDA-Developers mobile app
I know i should return it, but i really want to keep it atleast as a second phone, anyone has a solution please ?
Before trying to install twrp and custom Rom what firmware were you on? If I were you I'd download the stock firmware from Samsung site open Odin and put phone into download mode I'm sure that will work.
I was on the newest one, with green battery indicator. I have already tried flashing official rom downloaded from sammobile, but odin always only states fail! After a second, meanwhile phone leaves the download mode and gets stuck on bootloop.
When I try to entry recovery phone gets stuck on TWRP screen but doesn't actually start TWRP.
I will send 50 bucks through PayPal to first of you guys, who will lead me to the successful repair of my note!
Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.
I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.
Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.
Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.
Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?