Hello all.
I'm new to modifying my android (Galaxy S7 G930A) and could use some help. I have successfully rooted my phone, but have had some issues trying to flash a custom recovery. I was trying to flash TWRP but for some reason it didn't work, and I would always boot into the stock recovery.
Today, I screwed something up while trying to figure out my host of issues (I was also trying to figure out why I kept getting a "dm-verity verification failed" notice when flashing). Using the TWRP Manager app, I tried to install the recovery that way and it kept giving me an error that it was either already installed or encountered an issue of some kind. Knowing it wasn't installed, I looked for a different route. Long story short, I downloaded Flashify and then manually downloaded and flashed the TWRP recovery img and a "no-verity-opt-encrypt" file - which I read would fix the dm-verity error I was receiving.
I believe that's all I did before this recovery boot issue starting occurring.
Now, when attempting to boot into recovery (no matter what way, through an app, manually, etc) the blue text "Recovery Booting..." appears for half a second and then disappears. If I'm holding down the buttons it will flash again and disappear again, over and over. If I don't hold down the buttons, when it disappears the phone boots up as normal. So now I can't seem to access recovery at all. I wanted to try going the hard/factory reset route, but obviously can't because I can't access recovery.
Also, I don't know if this is related or not, but now my laptop will not recognize my phone at all. Doesn't give me any options - it will charge, but no connection. I was hoping to load it into Odin and do a stock reset to start from scratch before flashing a custom ROM.
Edit: I tested and connected to a different computer just fine, so there's obviously some miscommunication going on between my phone and laptop.
Can anyone help me out here? Sorry for the long post, I'm just really frustrated. :crying:
Related
Hi All.
So I'm not new to rooting / ROMs (nor am I an expert, as you'll see), but somehow have totally screwed up my tab. I've now honestly done so many things to try to recover, that I couldn't begin to summarize how I got into this mess, but I'll try.
Model is GT-P5113. Most recent working ROM was SlimLP 5.1
I went to flash CM12.1 (using CWM) and God only knows what happened. After it flashed, I tried to reboot and it would only go to CWM recovery. If I chose to reboot device, it would only shutdown, not reboot (This was actually one of the issues I was having with SlimLP as well, so I don't think the flashing had anything to do with that???)
After many attempts at reinstalling CM and SlimLP (I used the same Zip that had worked previously with SlimLP, and the flashing would say installed) it would still only boot to recovery. I finally said, screw it, I'll just start completely over
So attempted to go back to stock 4.2.2 using Odin3.09. Got the stock ROM off SamMobile site. ODIN seemed to flash,but again when it would go to reboot, it would just power down and a charging battery would show up. So I would unplug from the computer, push power button. When it powered up, it would say Installing system update, then after the status bar moved a bit, it would say Error and shut down. When I restart, it very briefly says installing system update, then show the dead android with a red triangle and No Command, and it would boot to the stock android system recovery (I assume CWM was taken off in the process). In yellow, under the stock recovery it says
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
I've tried installing the other ROMs again, this time with TWRP, but only for it to boot to recovery after the Samsung Tab 10. 1 logo.
I have no clue where to go from here. No clue if I'm still rooted (doubt it). At this point I don't care. I just want a functioning tab. I've spent hours searching, but nothing works. I'm open to any / all ideas.
Thanks
Aw, show me a little love, bros. Someone' gotta know something. I'm not above begging / pleading.
I can give more info, less info, post somewere else. Just let me know,and help me resuscitate my tab.
thanks again!
Hi all! I have been trying to fix this tablet for weeks. It's an SM-T580 Galaxy Tab A 10.1 tablet. It's actually my girlfriend's tablet and she tried to root it first and she royally screwed it up and I am having a lot of trouble cleaning it up.
So, when I got to it, she already had it stuck on the downloader mode and if you tried to boot it, it went to the blue screen that says "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software."
So here is everything I did as well as I can remember it:
1. Tried every version of smart switch and KIES software. It does not recognize it ever.
2. Tried to flash custom recovery, but FRP lock is still enabled. She must not have correctly changed the settings in the tablet before beginning the root.
3. Tried to flash stock firmware, but it says it needs to be repartitioned. I downloaded what I thought was the pit file, and repartitioned the chip, but it still won't successfully boot. I tried several different cables and ports.
4. Tried to flash probably 10 different firmwares to see if anything would stick. Used several different versions of Odin all the way from 1.3 up to 13.5. Nothing will successfully boot.
5. Found stock recovery (I believe) and got stock recovery on there but when i get to recovery it says it can't mount anything. It gets a huge list of errors like "can't mount E..." I am able to ADB sideload, but so far nothing I try to sideload works because it says it has the wrong footer and the wrong signature.
Am I boned? She left it plugged in for like a week at least, so my assumption is the emmc chip burned out. Any and all help massively appreciated!
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
gabeblack said:
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
Click to expand...
Click to collapse
You need to clear the cache after flashing to get out of the boot loop.
Use the download key combo to restart. As soon as the screen goes black move to Volume up+home+power.
In the recovery menu choose clear/ Wipe cache, then choose reboot.
I apologize for not updating this thread before when it was still recent. The fact is that I didn't manage to fix my phone; clearing the cache after flashing did nothing to stop the loop.
I ended up taking the phone to the people who have fixed it in the past and after more than one month, they gave up. So I got my phone back and I want to try to give it another go before I just sell it for parts.
Unfortunately, my phone has come back even worse. Now it has no Recovery Menu to speak of, at least none that I can access; after a few seconds of the blue text on the top saying that it's entering recovery mode, it then proceeds to a blue screen saying: "Security Error: This phone has been flashed with unauthorized software and is locked.". I can still access Download Mode.
I have attempted flashing a few firmwares that I believe should have worked with my SM-G930U. Odin listed the attempts as "pass" and, after restarting and going back to the Download screen, it says the binary is Official. However, after trying to restart the phone normally, it starts displaying the blue screen again, and then, after going to Download mode, the binary is reverted to "Custom".
I believe right now the order of the day is to get the recovery menu to work again so I can do all the cache cleaning that seems to be required after flashing firmware. Any ideas at all on how I should proceed? Is there something specific I should download to fix the recovery menu?
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Drunkpilot said:
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Click to expand...
Click to collapse
Never rooted, was using the phone legit before it froze and entered boot loop. I flashed all 4 files, multiple times.
Someone tried fixing my phone a few days after I replied to this thread and some progress seems to have been made, but now the phone cannot get past a black screen with a "SBL Error! rdx_init!" in red text, and "upload mode" in yellow text. Still cannot access Recovery Mode, but Download Mode still works.
I did a little Googling on rdx_init errors and it seems I need a firmware dump from another G930U or something like that...any ideas on how I can proceed?
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
STA1NL3SS said:
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
Click to expand...
Click to collapse
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
gabeblack said:
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
Click to expand...
Click to collapse
I thought I had one in my phone, but I don't. If you look at the thread where you downloaded the Root_V12, you will see it. It's near the end of the thread somewhere.
Okay. I was messing around with my firmware which I've done in the past. I've had a few problems then due to my phone model being obscure (Samsung Galaxy S6: SM-S906L). I've always had a copy of the firmware saved to my computer in the event of a bootloop or a similar issue, I figured I could just flash it with Odin to fix it. I have also done this in the past. After accidently wiping my phone, I went to re-install Magisk, but noticed my phone trying to push an update. I let it go through without much though and after it finished saw it didn't change much. I carried on with re-installing Magisk when I figured I might as well fix some problems I had with booting the phone (I would have to boot it into download mode then recovery to get it out of a bootloop each time I turned it off). I carried on with flashing my saved firmware to fix the problem. Everything flashed fine except the bootloader. It's come to my understanding now that because I let the update carry through with my phone, my saved firmware is no longer compatiable dispite the fact that it didn't change my android version. So now I have a bootloader installed that is meant for a higher update without my known ability to downgrade. Due to the obscurity of my phone model, I can't find anything to bring my firmware up to what my bootloader is at. So now my phone is stuck in a bootloop with the ability to access download mode, but recovery mode simply gives me a "recovery is not seandroid enforcing" error. I would greatly appreciate it if someone has any advise they could give me.
Hello everyone,
This is my first post on this forum, sorry in advance if the format is not correct.
Here's my problem: I was given a SM-J710FN that displayed an overheating problem on the screen while the phone was not heating at all, as well as buttons at the bottom of the phone were not working anymore.
I reset the device to factory default, erased the data from the recovery mode and flashed the 8.1 Oreo version with a ROM STOCK J710FXXU6CSK1
After all these manipulations, the buttons still did not work and the overheating message still appeared, preventing the phone from being charged even when it was switched off.
So I thought of programmed obsolescence, and thought it was worth trying to downgrade the phone to 7.0 from version 8.1.
Could you help me on this subject and tell me what you think?
Sorry for the up
try flash a custom rom, it does not need buttons, like this https://www.google.com/url?sa=t&source=web&rct=j&url=https://m.youtube.com/watch?v=veWLleEULe4&ved=2ahUKEwigx7TjmoTvAhVUIIgKHWbJCjIQ28sGMAJ6BAgFEBc&usg=AOvVaw3xJ6phS4kotjx4fk6Ypfuq
home button work or not
Thank you for the answer, I really appreciate it
Here is the update since I followed the Youtube link you sent me:
I have transferred the Custom ROM (Pixel-AB-11-20200909-ErfanGSI.img-0125.7z) as well as H-VENDOR_V1.0.zip to the mobile phone via a USB cable plugged to my PC in the root of the phone in order to proceed to its installation.
I then used Odin to flash Orange Fox (also TWRP on other attempts) with AP, but when I get to the Orange Fox recovery screen, the .zip files do not appear in the files. When searching on the Internet, it is advisable to flash via Fastboot, but despite several attempts, I cannot detect the phone with Fastboot, but only ADB. Even the manipulation saying to install the drivers manually from the device manager doesn't work because a message saying that the file to be used doesn't contain a driver is displayed. (android_winusb.inf)
And I also notice that after having flash TWRP or Orange Fox, the phone can no longer boot on the system.
Have you got any advices?
I continued my tests on my side, I was able to better understand how TWRP and Orange Fox work, in fact to make it usable, you first have to FORMAT the /data (not swipe), so, make TWRP / Orange Fox operational.
I was then blocked during the installation of the personalized ROM with the error of the /vendor, following my research, it would be necessary to install a .zip dedicated to that (Mokee from what I saw)
But I did something I shouldn't have done, and I flashed the zip "twrp-3.2.1-0-20180414-codeworkx-dumpling" from the Orange Fox recovery, and since then, the phone is stuck at startup, and when I try to access Download Mode, I get stuck at the Warning Message because my volume buttons don't react.
Is it possible to do something about it or the phone will be forever bricked?
up