SM-g935df hang with boot screen - Samsung Galaxy S7 Edge Questions and Answers

hello..SM-g935df suddenly battery low while updating firmware.now its hang with boot screen.FRP lock also on.I tried many firmware (7.0 and 6.0.1 etc)all firmware fail at flashing "recovery.img" in odin.in recovery mode i can see like below image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i reset the device.now its show like this image.please help me

https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!

JeffDC said:
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
Click to expand...
Click to collapse
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here result firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1

geeth said:
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result View attachment 4345010
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here resultView attachment 4345011 firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1View attachment 4345042
Click to expand...
Click to collapse
Head over to the OP's post and ring him up. I think after the first flash, as I get it, you have to somehow run the .bat file in adb, It is the .bat file that deletes the Persistence file/partition, where, as he explains, the FRP (Google enctypted file) is held. Once that is out of the way, FRP should be gone, then flash back your stock BL, or leave it on the U (Universal) BL if you wish?
That's my understanding. I don't think the OP's been around his post for several months. We are hoping he returns to answer and clarify some questions.

Related

Lost recovery but Rom OK?

I seemed to have lost my recovery but my phone is otherwise working.
I went from CM13 with TWRP, downloaded OS3 from the official oneplus web download as well as the "optional recovery" on the same page.
I wiped data/system/dalvik/cache and flashed the OS 3 zip.
I then flashed the stock recovery img.
Wiped again.
Rebooted to recovery from TWRP and got stuck with the oneplus logo. Completely non-responsive.
Fearing I had softbricked the phone, I started with ADB, got the Qualcom HUB listing under Device Manager and was about to start the process of updating Qualcom Drivers and running the recovery tool (having not been able to get fastboot to see the device) when a miracle happened and the phone started booting up on its own. After running setup, I rebooted, no problem.
I have since been able to use fastboot oem lock and confirmed the phone is locked (I wanted to get back to stock).
Everything is working fine EXCEPT I don't seem to have any Recovery at all. If I use the Developer Option for Advanced Recovery and boot into recovery, I get the oneplus logo. If I use Vol Down and Power I get the oneplus logo.
I think I have lost my recovery but recognise that I am out of my depth and don't want to stuff up the second chance I was given by trying to flash a recovery (I want stock receovery so I can get OTAs in the future). BTW, I read extensively before I tried this, looking at a number of different sites and followed instructions to the letter (or at least I thought so!).
Could someone who knows what to do please help to get my recovery back? It would be very much appreciated.
Edit: I managed to fix it. You have to use the Qualcomm tool and go back to OS2.2 and then update to OS3. See the link below and follow Method 1, doing everything exactly as set out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Meizu pro 5 have rooted rom but lost recovery - phone can boot pls help!

Hi
i was stupid enough to unlock my bootloader and flash recovery, then reflash back latest meizu stock via twrp , and flashing again the twrp recovery image,
i don't why, but the first init of the rom update ****ed my recovery up and now i lost recovery (even the stock, the phone just booting to the rom)
fastboot oem unlock isn't possible because i'm on locked bootloader rom.
i tried to flash the recovery via rashr with the backup i made and i can't becuase of busybox, i guess it's because the bootloader lock
is there any script or way that i can stock recovery back?
actually if lost the rom i lost my phone....
please help!
UPDATE: STILL WITHOUT SUCCESS TO FLASH THE RECOVERY BACK
i tried adb shell flashing, susscessed to flash system image , but via this method ( dd - of)
https://forum.meizufans.eu/topic/25...ional-firmware-on-your-chinese-mainland-meizu
ir flashed the system partition successfully but without the bootloader nor the recovery
but as it supposed to be , it won't flash recovery , when i'm doing the same for recovery i'm getting Operation not Permitted
hello try this link maybe it solve your problem good chance
https://forum.meizufans.eu/topic/5335/bricked-pro-5
i get token sign failed what should i do now?
prodaz said:
hello try this link maybe it solve your problem good chance
https://forum.meizufans.eu/topic/5335/bricked-pro-5
Click to expand...
Click to collapse
i get token sign failed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what should i do now?
i found a new link for you try this method. tuto is in english and chinese there are some tools and pdf file to help you.
https://mega.nz/#F!R8dSiT5T!08LHl2JKm5_u579uyAWfEw
Its the same!
Edit: I was wrong.
Up
deliad said:
Up
Click to expand...
Click to collapse
Any news on the phone's recovery?
I have the same problem... locked bootloader and TWRP that is not loaded...
just try this.good luck man.http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
tzzzz said:
just try this.good luck man.http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
Click to expand...
Click to collapse
nothing has changed
error token signature
Up
HI GUYS, please join to the discussion:
iv'e opened an investigation thread on the android general hacking forum, so, maybe we can get help from the devs / hackers on xda, because here i don't see anybody that listens to our problem.
http://forum.xda-developers.com/android/software-hacking/pls-help-to-meizu-pro-5-to-life-t3494293

Cannot restore system, stuck on bootloop

Hey guys,
i recently bought a OP2 from Ebay which is bricked (Stuck on bootloop). The phone wasn't able to boot into Recovery. Only thing worked was Fastboot. I managed to get stock recovery to work using this Guide (Method 3):
https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
Unfortunately it still stucks in a bootloop. I tryed flashing serveral Stock-ROM's. Does anyone know a solution to fix this?
ADB Sideload give me this output (everytime at around 94%)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm kind of new to this.
Greedings
Kynie
Make sure to update the fastboot/bootloader to the newer 3.0/hydrogenos version as all newer ROMs require this to boot.
How can i do this? I have stock bootloader v. 1.0 installed and not able to flash via fastboot cause the phone is locked. Cannot unlock because i'm not able to turn the phone on.
Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Click to expand...
Click to collapse
Thanks for the information. The OTA zip file do I have already. Sadly I can't find such an utility you are talking about. The only thing I found was a chineese (or I think it's chineese) tool which I already tryed but not worked. This tool just brings the stock recovery v 1.0 to life.
Or do you mean a diffrent tool?
In a similar position to you. Phone was working fine (only received it today and tried to get CM13 on it)
My bootloader is unlocked, but phone will no longer boot up, or go into recovery.
I can get it into FastBoot, but it doesn't show up anymore in ADB devices. When in fastboot, the device shows as "Android Device, Marshall London Bootloader interface"
If I switch the phone off and check Device manager it just shows as unknown device and then windows gives me an error message that its not functioning properly.
I have tried to follow this guide https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
but it won't allow me to update the device driver, even if I turn off signature for drivers.
The only thing I can get to load is Fastboot. I did at one point have a little penguin on the screen, but haven't replicated that again.
Can anyone help? I'm pulling out my hair
Are you sure you didn't just boot it up into fastboot-ish mode? To be able to flash using that tool you mustn't boot up the phone, make sure it's of and hold volume up when connecting the USB cable, this way the phone will enter chinese factory flash mode at which you can flash using the chinese tool. Also the drivers require you to disable driver signature in windows to install since it's not signed.
Got it working in the end. I just ran the application without bothering with the USB driver stuff and it detected the phone. Then flashed the stock rom and it's now booted.
Still can't get CM13 installed, as I get the error 7 in recovery and that's what got me in the mess!
Sent from my ONE A2003 using Tapatalk
I turned driver signature of and installed drivers succesfully. I run the chineese tool and it finishes succesfully but the phone is still in bootloop. This is frustrating...
Hello do you have find à solution ??

Bricked boot.img, but got Stock Recovery

Hello everyone!
So, after I replaced my SM-G935v with SM-G935FD I decided to root it, but accidentally installed a wrong boot.img using ODIN.
I can not access the comforting Download Mode with three-buttons to re-flash to the correct boot.img file, but I can access the Stock Recovery, and it can flash ZIP from ADB and SD.
I'm currently downloading ROM files for my S7 Edge to flash them using ODIN, but since I've only got access to Recovery, could some of expertise help me on what the hell I should do?
I'm looking for a way to make a flashable ZIP out of the boot.img I'm downloading, but I can't find anything. Is this a good plan, and if it is, how can I achieve it?
Should I proceed to make a USB Jig?
Can I do something like this?
Code:
fastboot flash boot boot.img
I've just bought this phone for eight hours, and I unfortunately can't return it to the seller!
This is what I get when I try the three-button combo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DRSDavidSoft said:
Hello everyone!
So, after I replaced my SM-G935v with SM-G935FD I decided to root it, but accidentally installed a wrong boot.img using ODIN.
I can not access the comforting Download Mode with three-buttons to re-flash to the correct boot.img file, but I can access the Stock Recovery, and it can flash ZIP from ADB and SD.
I'm currently downloading ROM files for my S7 Edge to flash them using ODIN, but since I've only got access to Recovery, could some of expertise help me on what the hell I should do?
I'm looking for a way to make a flashable ZIP out of the boot.img I'm downloading, but I can't find anything. Is this a good plan, and if it is, how can I achieve it?
Should I proceed to make a USB Jig?
Can I do something like this?
Code:
fastboot flash boot boot.img
I've just bought this phone for eight hours, and I unfortunately can't return it to the seller!
This is what I get when I try the three-button combo:
Click to expand...
Click to collapse
TWRP can flash img............, but I don't think stock recovery can do it..... because you need find a signed kernel and ram disk....... and there is no fastboot in samsung phone.... you should try kies..... maybe it can save you.... and idk about JIG
Mengx said:
TWRP can flash img............, but I don't think stock recovery can do it..... because you need find a signed kernel and ram disk....... and there is no fastboot in samsung phone.... you should try kies..... maybe it can save you.... and idk about JIG
Click to expand...
Click to collapse
Not kies...smart switch. Emergency recovery software. Need your Sansung serial number from the back of your phone....
Sent from my SM-G935F using XDA-Developers mobile app

help me

i made a mess, i can't install anything, i tried here to do repair installation for sansung a20s software, but it immediately failed, also it doesn't let me exit this screen anymore
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks i solved by flashing the original stock firmware again
To root your device, start by flashing TWRP, which you can find here. The TWRP .tar file goes in the AP slot of Odin.
Once you have TWRP installed, you should be able to flash Magisk, which you can find here.
how installa TWRP, i have error
this trying to put... twrp-3.7.0_9-0-a20.img
I didn't notice that OEM LOCK is ON.
You must unlock your bootloader to flash custom images.
ok i haveTWPR done
but after reload sisytem ...
this is very strange, for an old phone, I don't understand, I've never had all these problems ...
i m crazy
Did you flash vbmeta as well as TWRP? This might be the right file
I have to try again ,,,, but I still haven't figured out if anyone has been successful in rooting this device ,, I sansumg told everyone to do it
then, then yesterday I reflexed the original stok, now so I first do a TWPR and THEN this file that you are providing me?
yesss done good
now I need more help, I put TPWR then The file repairs vbmeta ,, ...., but it tells me that I don't have root permissions yet
do i have to give up?
Did you get a working twrp? Try booting into recovery (twrp) and then flash Magisk-v25.2.apk. If that works, reboot into system and install Magisk-v25.2.apk as an app. Then start the app and it will tell you whether you have root. If it doesn’t work, I don’t know what to do next. You may need to have the Magisk apk on a usb drive or microSD card for it to be visible in twrp.
the problem is that I put the TWPR gives me an error
vbmeta ,, then I put your tar file (
vbmeta_disabled.tar
2 KB · Views: 1) the phone starts, but in recovery I don't see TWPR the android menu looks normal
from this menu I tried to install the magic, but the installation fails
When you install twrp from Odin, disable automatic reboot from Odin options. Once you see that the flashing is completed, reboot the phone by holding vol- and power for 7 seconds, then immediately hold vol+ and power to boot into recovery. Otherwise twrp will get overwritten with stock recovery and you have to try again.
I am thinking that by reviewing the file (vbmeta_disabled) it overwrites the TWPR that I first put ,, in the revvr mod it always starts me with the classic menu
[email protected]
but every time I install a TWPR I have to insert after the file (vbmeta_disabled) because otherwise the phone always restarts with vbmeta error in download mod
Use 7-zip and add vbmeta.img from the tar above to the twrp tar and flash that
no work,,stay that way

Categories

Resources