I've flashed a custom splashscreen logo and now my phone can't boot up (i don't see the splashscreen) but works the download mode. I've tried to reflash with odin the official firmware but doesn't work. Have you some ideas?
------------
EDIT
------------
SOLVED: After a lot of attemps I've readed the source code of the boot changer and I've created a new flashable file from a s6 device for odin and it works!!!
SOLVED: After a lot of attemps I've readed the source code of the boot changer and I've created a new flashable file from a s6 device for odin and it works!!!
Related
I start Install customs roms on s5360
Before i was on stock rom, kernel & recovery
First i zip update ( root ) all work well
after ZIP cmw 6.0.1.2 the phone reboots
Only recovery mode and it stills there
Same things with installed twrp 2.8.7.0
Phone dont quit recovery mode
I try to Install stock roms several times by Odin (---.tar) or recovery mode(-----.ZIP)
But It fails there are some screenshots of pc
Thanks for helping or suggesting
+++++++++++++++++++++++++++++++++++++++++++++++
SOLVED:
After many trials i unbrick my phone by Odin3 version 1.85 on windows 7
My s5360 relive : Odin green pass by
flashing set S5360XXLK1 on this link http://www.mediafire.com/download/bkz8eln4xpiov1n/Galaxy+Y+2.3.6+Update+%28Indian%29.rar
it has 4 folders :
1- Bootloader
2-Pda
3- Modem
4- Csc
If this dont works
you can flash twice :
First flash with check repartition case pit folder " totoro_0623.pit "
In second time 4 folders far above
Kindly all
Today i was trying to install the Android Marshmallow 6.0.1 on my Galaxy S5 Snapdragon via Odin, i downloaded the firmware from Sammobile, i verified that the phone model was exactly the same as named on the firmware, i place the .md5 file in the AP slot and everything was ready to go! (The phone was already plugged and in Bootloader mode, and drivers were up to date) then when finishing the flash Odin FAILS to complete the flash and the phone is left with nothing than the Download mode, i panic and try to access recovery mode but realize that there´s no recovery....I proceed to install the recovery.tar into my phone and it works, i start the phone and Samsung logo comes up, finally it loads and does al the process after you flash a Samsung phone.
Everything works just fine!...except for one thing, THERE´S NO RECOVERY!!!. The phone works perfectly but when i try to enter recovery mode, it sends me to Odin mode as it displays a message saying that failed to boot into recovery.
Please help me i don´t know what to do.
Thanks!
Just flash a custom recovery like twrp or cwm
Already did...same problem, recovery won't boot
adavicco said:
Already did...same problem, recovery won't boot
Click to expand...
Click to collapse
You need to flash a pit file to complete the install correctly.
I tried everything for hours. Till I gave up
All I want is to be able to root this phone. I would get stuck at samsung logo after rooting and OS won't boot
Country/Region Brazil
Product Code ZTO
OS VersionMarshmallow (Android 6.0.1)
Release Date 15.12.2016
PDA J500MUBU1BPL1
CSC J500MZTO1BPL2
Phone J500MUBU1BPK1
I get errors about dm-verity verification failed in recovery mode, and I also can see
QUALCOMM Secure boot : enable
Secure Download : Enable
At download mode...
Please help guys I tried everything I found in the internet. I flashed TWRP with download mode, then would remove the battery and boot to recovery, install the supersu zip and reboot, that was the tutorial I was following but didn't work.
Hello bro
First : goto developer options and enable oem unlock
Then flash the twrp recovery with odin . Then install flashable supersu
That's what was I did to root my J5 too and done successfuly
Best regards..
Sent from my Samsung Galaxy J5 using XDA Labs
Hello,
I wanted to change the bootlogo, I've modify an logoboot file (zip).
I have with TWRP install this zip file but now my tel does not boot anymore, and I no longer have access to TWRP because there is a problem with the logo ...
I still have access to download mode and odin. I tried to install the official ROM but nothing changes. Do you have any ideas how to reset the boot by odin?
I cant factory reset because the recovery is not shown, i see just an black screen.
Slon4564556 said:
Hello,
I wanted to change the bootlogo, I've modify an logoboot file (zip).
I have with TWRP install this zip file but now my tel does not boot anymore, and I no longer have access to TWRP because there is a problem with the logo ...
I still have access to download mode and odin. I tried to install the official ROM but nothing changes. Do you have any ideas how to reset the boot by odin?
I cant factory reset because the recovery is not shown, i see just an black screen.
Click to expand...
Click to collapse
You need to restore param partition.
View attachment SM-A510F-PARAM.tar.zip
Unzip and flash the SM-A510F-PARAM.tar.md5
If you have any other model of A5 you'll have to find it yourself. It's in the BL package of the full firmware.
tys0n said:
You need to restore param partition.
View attachment 4706671
Unzip and flash the SM-A510F-PARAM.tar.md5
If you have any other model of A5 you'll have to find it yourself. It's in the BL package of the full firmware.
Click to expand...
Click to collapse
Thank you very much ! You are my savior ^^
Hello to everybody.
like the title of the thread suggests i have a Samsung S7 Edge (g935f) that isn't able to boot anymore. For what I remember I rooted this phone in 2017, using cf autoroot with Odin, but never installed some other custom rom.
Friday i needed to install upgrades and make a big mistake, I've disabled the unlock oem option. Now the device don't boot anymore, showing the Custom binary blocked by FRP lock when try to boot and even when is in charge, and in recovery mode you can see dm-variety verification failed... error.
I've tried to flash a new stock firmware, downloaded using the Samfirm tool, with odin but stuck in NAND Wright.
I've read that with this two errors, the phone is most likely in a hard brick situation.
Some other informations: in recovery mode I have the following informations:
MMB29K.G935FXXU1BPH6
samsung/hero2ltexx/hero2lte
6.0.1/MMB29K/G935FXXU1BPH6
and at the bottom the "dm-verity" error message
in download mode:
Current binary: Custom
System status: Custom
FRP LOCK: On (that's my fault)
Hope someone can help, and thanks.
Sorry didn't read your post correctly.. since you are still on v1 bootloader
Follow this link :
https://www.techzai.com/fix-drk-device-root-key-for-samsung-galaxy-phones/amp/
In short, extract AP and copy boot.img and system.img to new folder, then rename boot.img to recovery.img and repack AP using only these 2 files (system.img and renamed recovery.img) or maybe repack system+renamed recovery+boot which means we flash boot.img 2 times.. if using only system and renamed recovery doesn't work, and maybe add userdata.img too if adding boot.img doesn't work..and try flashing in official odin (if it doesnt get flashed in official odin.. use prince comsy modified odin)
(before doing this download this firmware and apply above procedure on it :
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/EUR/download/G935FXXU1BPH6/89733/ )
(Auto tar 2.0 link use to repack files to tar :
https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file )
Don't tell me if you detect any viruses lol, i don't own any file, just helping to get your phone working again (delete all such files after using them)
Flash bl, csc, cp as usual alongwith this modified AP, use default odin options (don't tick nand erase or any other advanced option in odin)
And dont try to boot into recovery as there will be no recovery .. if lucky .. you will be able to boot phone to go in settings and enable oem unlock option.. if unlucky you will brick your phone even further like efs partition further damage/ nv data corruption (which could be fixed by a box)
So i told you the risks, i will not be responsible for anymore damage.
Note : don't update to newest/latest firmwares or higher bootloader (because it makes rooting and fixing device very difficult as firmware with a higher bootloader version cannot be downgraded to lower bootloader version) and also your dm verity is permanently destroyed so even if you are able to fix your phone by yourself you will always need to keep oem enabled and dm verity disabled to use it.. and upgrading to latest firmware will only create more problems
Good luck ..