Triforce to 5.1 JFLTE-GPE to Soft brick - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

I hate to be the guy asking about a soft bricked phone but I can't seem to find anything in the other soft bricked threads that helps me.
I was trying to go from Triforce to 5.1 JFLTE-GPE. When I flashed I had no APN. I read that factory resetting through recovery then reflashing could help with that but it didn't seem to help. I managed to do that 2 or 3 times without any effect, then CWM informed me on a reboot that I might've lost root. I told it to try to recover root and rebooted. No change. I go to start CWM again and it doesn't start. I used ODIN to renew root and reinstall CWM. Now it wont go past the S4 screen.
Since then, I'm getting errors any time I try to flash a new rom. I can't seem to side load a rom from Odin either. I keep getting FAIL(Auth) errors. L720_OD2_Pre-Rooted_Firmware.tar doesn't work for me. I'm unsure if I should be trying to flash other versions instead. I'm using Odin 3.07.
When I use CWM recovery to try and directly flash Zips the 3 that I've tried always fail. Half the time it's telling me it's a bad signature. When I toggle signature verification it fails.
I have no idea what's going on anymore. Help?

crowbahr said:
I hate to be the guy asking about a soft bricked phone but I can't seem to find anything in the other soft bricked threads that helps me.
I was trying to go from Triforce to 5.1 JFLTE-GPE. When I flashed I had no APN. I read that factory resetting through recovery then reflashing could help with that but it didn't seem to help. I managed to do that 2 or 3 times without any effect, then CWM informed me on a reboot that I might've lost root. I told it to try to recover root and rebooted. No change. I go to start CWM again and it doesn't start. I used ODIN to renew root and reinstall CWM. Now it wont go past the S4 screen.
Since then, I'm getting errors any time I try to flash a new rom. I can't seem to side load a rom from Odin either. I keep getting FAIL(Auth) errors. L720_OD2_Pre-Rooted_Firmware.tar doesn't work for me. I'm unsure if I should be trying to flash other versions instead. I'm using Odin 3.07.
When I use CWM recovery to try and directly flash Zips the 3 that I've tried always fail. Half the time it's telling me it's a bad signature. When I toggle signature verification it fails.
I have no idea what's going on anymore. Help?
Click to expand...
Click to collapse
You can only Odin the same or newer firmware, since you are on OH1, you can only Odin OH1. Also use TWRP for recovery as it's been the only that has been updated for Lollipop which is probably why you're getting all the errors.
{
"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"
}

Related

Endless amounts of failure with Odin flashing - GT-I9505

*##### EDIT #####*:
Who would have thought that running Windows with VMWare Fusion on Mac OS X could mean that Flashing tasks aren't always a possibility... Tried on a nearby Windows computer and it worked completely fine..! How disappointing, sorry the waste of post, could a Mod please delete this.
Cheers again.
_____________________
Hello all.
I have a Galaxy S4 GT I-9505 which, to date, has shown me that it seems to be impossible to revert it back to stock firmware, of any kind...
I have tried numerous different stock firmwares and every single one has failed. I came from a Rom called 'Foxhound' and was a newly released 4.4.2 at the time, so I'm guessing KNOX has done something to the bootloader which has deemed my device in limbo - to my knowledge.
The thing is, I've come across a leaked 5.0.1 firmware for this device, so I thought I'd download it, only to notice that the Odin flash file wasn't a single TAR file but a series of other files that correspond to the functions of Odin.
From this point on, I decided to try and flash the Bootloader file by itself, and that WORKED. Of course, the only progress I was getting from this was the basic boot logo at the beginning of powering on the device.
Seeing as I was unable to boot into recovery, I thought I'd try and download an Odin flashable CWM Recovery, and this also WORKED.
The thing is, whenever I attempt to flash a full Rom through Odin, it will go through the inevitable error that it does with all attempts.
Here are some images:
{
"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 beyond frustrated by this as I can't deem the phone usable until I have it up and operational, and it is basically worth nothing in this state.
I would be endlessly grateful if someone would be able to point out what the possible issue may be, I would be beyond thankful!
Best regards,
Try to use Odin 3.09

[Q] Can't boot any ROM!

Well, I think I need some help with this one.
So, I have been using Resurrection Remix as my daily driver for a while now (to be able to run lollipop). As I noticed the G2 now has an official lollipop build, so I wanted to install that(cam sucks on most ROMs and overall stability isn't always great). Since I figured the best way would be to go back to stock, and then run the OTA updates.
I made a backup of my current rom, found this, and tried the TOT method. Everything ran fine, but when the 85% reboot thing happened, it booted straight into TWRP. Decided to reboot to system via TWRP, but after showing the LG logo for about 5-10s, it goed straight back into recovery. Since i figured the install failed or something I decided to factory reset, and restore from my backup. TWRP says the restore is succesful, but it still won't boot into my ROM. Reinstalling any ROM doesn't work either
Already tried this, no result(, and I'm afraid of trying the above guide again, but let me know if i should just try again)!
I do have access to my recovery and download, and ADB still works. The only thing I see is that instead of this:
{
"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"
}
Mine says this:
(My PC is in Dutch )
(The LG Driver on the guide was an older version than the one on my pc still, but I don't think that will cause a problem).
Hope my phone isn't gone forever, and thanks for helping in advance!!
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
You should edit the title to include the word (solved) or (fixed).
Sent from my LG-LS980 using XDA Free mobile app
Scrytal said:
Well, I think I need some help with this one.
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
Click to expand...
Click to collapse
Hi, i can't boot any rom too,
I can access my download mode and recovery mode (twrp),
But i can't boot any custom rom,
And ADB can't recognize my phone,
I tried to back to stock using LG Flash Tool 2014 (the kdz ones), but nothing works,
And the official lg tool link is broken

Can't Re-Unlock the Bootloader

I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"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"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!
deleted
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems
I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.
I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!
scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)

Boots only to TWRP - Need help fixing

Hi there. About a year or so ago I went about flashing my Tab but it went wrong and now all I can do is get it to boot to TWRP. Would someone be so kind as to tell me step by step what to do to get it back working? I'd prefer it to go back to stock ROM without TWRP or other 3rd party flash programs but I'll take what I can get. Help appreciated.
This is what I get when it boots:
{
"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"
}
Bump.
fuzzyreets said:
I'd prefer it to go back to stock ROM without TWRP
Click to expand...
Click to collapse
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?
DHGE said:
Did you try booting to DL-mode (via adb reboot for example) and flash a stock ROM with ODIN?
Click to expand...
Click to collapse
I got a reply! Thank you!
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.
fuzzyreets said:
No I didn't try that. To be honest I used to flash android stuff all the time but kind of having been doing much of that stuff the last few years so I don't remember how to do any of that. If you were so kind to provide me a link or walkthrough on what to do that would be HUGELY appreciated. Thanks for the reply.
Click to expand...
Click to collapse
What was the goal when you started down the path of installing TWRP? It seems like you might have been part way there if you got that far?
There are Lineage install instructions here. <-- More importantly Odin Download if you don't already have it.
If you decide to try Lineage, the latest builds require new firmware found here. It can also be obtained by returning to stock and updating.
Anyways If you are in TWRP, in the restart menu there is an option to restart to download. If will reboot to a black screen, just hit the power button once when the screen goes off. Before you do this, you need to obtain stock firmware, from somewhere. (Sammobile or something like that) You will also need Odin, link above.
As with anything proceed at your own risk.
Once you have those files, you can extract the firmware. They will be labeled and go into those spots in Odin, AP, BL, CSC, then you should be able to hit start. I'm going from memory, as I haven't had to restore mine since I got it (and looking at the files in stock firmware file).
Idk how relevant this is anymore but I had this same issue after I install lineage 18, there's a multi-disabler zip I got awhile ago that fixes all my flashing problems related recovery loop. Just Google that zip, flash it then format and restart. That what I've done easy fix, this assumes you followed the basic steps to properly flash whatever it is you're trying to.

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol
Maybe the rom is incorrect have you checked the region and model number etc?
Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked
Could you provide ODIN logs?
{
"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"
}
it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one
TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.
Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?
It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.
no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox
Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin

Categories

Resources