Root Active s4 I537UCUCOC6 - Galaxy S 4 Active Q&A, Help & Troubleshooting

Greetings community, this is my first post.​
I would like to root in my Active I537, but none of the methods work for me, I have version 5.0.1 (buy the device with this version)
I'm willing to do whatever method works, greetings.

So You're Already on 5.0.1 and Want to Root?
blackbiking said:
Greetings community, this is my first post.​
I would like to root in my Active I537, but none of the methods work for me, I have version 5.0.1 (buy the device with this version)
I'm willing to do whatever method works, greetings.
Click to expand...
Click to collapse
Read this post entirely and make sure you understand before trying anything.
You can't root 5.0.1 directly, you have to downgrade to KitKat, root that, and then upgrade back to lollipop with a special KeepRoot Method. To downgrade to KitKat, download the following file to your PC and extract with 7zip or WinRar: https://www.androidfilehost.com/?fid=23991606952608110
Boot your phone into download mode. This is done by powering the phone off, then holding down vol- and power at the same time. Connect the phone to PC with USB. You have to flash all four files with Odin (attached to the bottom of this post) as shown in the following 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"
}
Please be aware that this process will erase any settings, data, and media saved to your phone's internal storage and restore it to its original factory condition, now on KitKat. This process also takes a long time (at least 5 or 10 minutes) and will cause your phone to reboot on its own, and to boot into stock recovery at least once. It is important you leave your phone alone while it is doing so, and definitely do not disconnect it until it boots into the KitKat setup wizard screen.
Once on KitKat you can root with towelroot, it's a one-click root app, very easy to use: https://www.androidfilehost.com/?fid=24052804347827826 You install that by allowing installation from unknown sources in your security settings, then just open the apk file with any file explorer. Once that's done, install the SuperSU app. Then you can use the following method to upgrade back to 5.0.1, but this time with root: http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355

Thanks so much! Rooted
thisisapoorusernamechoice said:
You can't root 5.0.1 directly, you have to downgrade to KitKat, root that, and then upgrade back to lollipop with a special KeepRoot Method. To downgrade to KitKat, download the following file to your PC and extract with 7zip or WinRar: https://www.androidfilehost.com/?fid=23991606952608110
You have to flash all four files with Odin (attached to the bottom of this post) as shown in the following image:
Please be aware that this process will erase any settings, data, and media saved to your phone's internal storage and restore it to its original factory condition, now on KitKat. This process also takes a long time (at least 5 or 10 minutes) and will cause your phone to reboot on its own, and to boot into stock recovery at least once. It is important you leave your phone alone while it is doing so, and definitely do not disconnect it until it boots into the KitKat setup wizard screen.
Once on KitKat you can root with towelroot, it's a one-click root app, very easy to use: https://www.androidfilehost.com/?fid=24052804347827826 You install that by allowing installation from unknown sources in your security settings, then just open the apk file with any file explorer. Once that's done, install the SuperSU app. Then you can use the following method to upgrade back to 5.0.1, but this time with root: http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
EDIT: I forgot to mention, to flash firmware with Odin, you need to boot your phone into download mode. This is done by powering the phone off, then holding down vol- and power at the same time
Click to expand...
Click to collapse

I fINALLY DOWNLOADED ODIN, I CANT GET MY PHONE TO sync up to odin though, i cant find any files off it or anything, then when i click power+home+vol down, it goes into a mode saying warning about downloading other software, i click continue and now it just sits ad a page of the android and saying downloading, top left says odin mode

Unknownlegion said:
I fINALLY DOWNLOADED ODIN, I CANT GET MY PHONE TO sync up to odin though, i cant find any files off it or anything, then when i click power+home+vol down, it goes into a mode saying warning about downloading other software, i click continue and now it just sits ad a page of the android and saying downloading, top left says odin mode
Click to expand...
Click to collapse
Did you connect the phone to your PC with the USB cable that came with the device? Because your description of the phone being in download mode sounds normal

thisisapoorusernamechoice said:
Did you connect the phone to your PC with the USB cable that came with the device? Because your description of the phone being in download mode sounds normal
Click to expand...
Click to collapse
So I finally got it but I don't think I got the right firmware since every time I get it and click start it fails it's driving me insane lol

Unknownlegion said:
So I finally got it but I don't think I got the right firmware since every time I get it and click start it fails it's driving me insane lol
Click to expand...
Click to collapse
Use the following link. You have to download the file and extract it with Winrar or 7zip, and then select all four files with Odin:
https://www.androidfilehost.com/?fid=23991606952608110

thisisapoorusernamechoice said:
Use the following link. You have to download the file and extract it with Winrar or 7zip, and then select all four files with Odin:
this is for ne3 i have nh4. is that okay?
this is what i have, a sgh-i537
android version is 4.4.2
baseband version is I537UCUCNH4
Click to expand...
Click to collapse

Unknownlegion said:
this is for ne3 i have nh4. is that okay?
this is what i have, a sgh-i537
android version is 4.4.2
baseband version is I537UCUCNH4
Click to expand...
Click to collapse
If you're on NH4 just root with the following method: http://www.w0lfdroid.com/2014/09/To...-and-Note3-Android-4.4.2-NF-or-Later.html?m=1
At the end of the directions, where it says to use the NH3 kernel, use the following NH4 kernel instead: https://www.androidfilehost.com/?fid=24052804347796155

thisisapoorusernamechoice said:
If you're on NH4 just root with the following method:/TowelRoot-Samsung-Galaxy-S4-S5-and-Note3-Android-4.4.2-NF-or-Later.html?m=1[/url]
At the end of the directions, where it says to use the NH3 kernel, use the following NH4 kernel instead:fid=24052804347796155[/url]
Click to expand...
Click to collapse
so i downloaded the file u gave me for nh4, got i t to passs. after it was done rebooting i went to towel root and clicked make it rain, but it says its not supported still. so im pretty stumped now lol

Unknownlegion said:
so i downloaded the file u gave me for nh4, got i t to passs. after it was done rebooting i went to towel root and clicked make it rain, but it says its not supported still. so im pretty stumped now lol
Click to expand...
Click to collapse
Read the website I linked to, you don't use the nh4 kernel till after you've used towel root. Before you use towel root you have to flash the i537 root kernel provided by the website

thisisapoorusernamechoice said:
Read the website I linked to, you don't use the nh4 kernel till after you've used towel root. Before you use towel root you have to flash the i537 root kernel provided by the website
Click to expand...
Click to collapse
I got it I just didn't flash back cause I didn't understand how after I rooted the phone now I gotta learn how to do all the rooted stuff. Thank you so much sir. Appreciate u r patience and time

Unknownlegion said:
I got it I just didn't flash back cause I didn't understand how after I rooted the phone now I gotta learn how to do all the rooted stuff. Thank you so much sir. Appreciate u r patience and time
Click to expand...
Click to collapse
Always happy to help and I'm glad to hear everything worked out. Once you're settled and feeling confident, here is how to get on lollipop rooted, if you want:
http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355

thisisapoorusernamechoice said:
You can't root 5.0.1 directly, you have to downgrade to KitKat, root that, and then upgrade back to lollipop with a special KeepRoot Method. To downgrade to KitKat, download the following file to your PC and extract with 7zip or WinRar: https://www.androidfilehost.com/?fid=23991606952608110
Boot your phone into download mode. This is done by powering the phone off, then holding down vol- and power at the same time. Connect the phone to PC with USB. You have to flash all four files with Odin (attached to the bottom of this post) as shown in the following image:
Please be aware that this process will erase any settings, data, and media saved to your phone's internal storage and restore it to its original factory condition, now on KitKat. This process also takes a long time (at least 5 or 10 minutes) and will cause your phone to reboot on its own, and to boot into stock recovery at least once. It is important you leave your phone alone while it is doing so, and definitely do not disconnect it until it boots into the KitKat setup wizard screen.
Once on KitKat you can root with towelroot, it's a one-click root app, very easy to use: https://www.androidfilehost.com/?fid=24052804347827826 You install that by allowing installation from unknown sources in your security settings, then just open the apk file with any file explorer. Once that's done, install the SuperSU app. Then you can use the following method to upgrade back to 5.0.1, but this time with root: http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
Click to expand...
Click to collapse
theres a confusion some posts say that your phone will reboot rooted and you say that it will reboot into the download mode so can you kindly tell me whats the truth and whats the difference?

syedharisiftikhar said:
theres a confusion some posts say that your phone will reboot rooted and you say that it will reboot into the download mode so can you kindly tell me whats the truth and whats the difference?
Click to expand...
Click to collapse
You don't have to worry about the download mode part. I've done this process dozens of times (for rom testing purposes) and I've always skipped the part about download mode

thisisapoorusernamechoice said:
You don't have to worry about the download mode part. I've done this process dozens of times (for rom testing purposes) and I've always skipped the part about download mode
Click to expand...
Click to collapse
so what you are trying to say is that it will not boot into the download mode? and it will boot up normally after flashing?

syedharisiftikhar said:
so what you are trying to say is that it will not boot into the download mode? and it will boot up normally after flashing?
Click to expand...
Click to collapse
Correct

thisisapoorusernamechoice said:
You can't root 5.0.1 directly, you have to downgrade to KitKat, root that, and then upgrade back to lollipop with a special KeepRoot Method. To downgrade to KitKat, download the following file to your PC and extract with 7zip or WinRar: https://www.androidfilehost.com/?fid=23991606952608110
Boot your phone into download mode. This is done by powering the phone off, then holding down vol- and power at the same time. Connect the phone to PC with USB. You have to flash all four files with Odin (attached to the bottom of this post) as shown in the following image:
Please be aware that this process will erase any settings, data, and media saved to your phone's internal storage and restore it to its original factory condition, now on KitKat. This process also takes a long time (at least 5 or 10 minutes) and will cause your phone to reboot on its own, and to boot into stock recovery at least once. It is important you leave your phone alone while it is doing so, and definitely do not disconnect it until it boots into the KitKat setup wizard screen.
Once on KitKat you can root with towelroot, it's a one-click root app, very easy to use: https://www.androidfilehost.com/?fid=24052804347827826 You install that by allowing installation from unknown sources in your security settings, then just open the apk file with any file explorer. Once that's done, install the SuperSU app. Then you can use the following method to upgrade back to 5.0.1, but this time with root: http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
Click to expand...
Click to collapse
i was trying this and it failed and now my phone wont boot saying no firmware please help i dont know what to do.
odin while doing xmitwrite fails.

N/A

Touch and go for a bit
I had some challenges with this, but it eventually worked. The first pass through, I couldn't install TowelRoot. Something in the OS was blocking it as a security threat, even after I set it to all 3rd party apps. I was able to get past this the second time. I theorize it had something to do with updates that installed OTA while I was trying to get Root Explorer installed. I also ran into a disconcerting hiccup while setting up SuperSU. It wanted to deactivate Knox (fine) but then hung up in the process. When I rebooted, everything seemed fine.
Anyway, I'm up on 5.0.1 now, thanks to this post, and I appreciate the effort that went into putting it together.

Related

[GUIDE] Injecting CWM into any kdz update

Hey guys,
I've managed to devise a method to inject the CWM recovery image into the LG Update tool during updating with a kdz.
The basic idea is explained in this post. I took it a bit further. During the updating process, you can replace the recovery image inside the updater's memory. Basically, you can use this method on any LG Updating tool. This guide uses KDZ Updater. The method is great for getting the latest firmware for your region and still get it rooted.
This procedure requires some quick actions in order to succeed. Read through it before attempting to flash. I'm not responsible for anything that might happen in the result of using this guide.
Needed files:
CWMInject
UPK
Latest CWM recovery image for P970
Cheat Engine
1. Run KDZ Updater from UPK with Windows Enabler on.
Select your KDZ file.
2. Run CWMInject with Admin privileges. Select KDZU process. Set CWM image to the recovery image file.
3. Run Cheat Engine. Select KDZU process. Change Value Type to Text and write ANDROID! in the search field.
4. Open Task Manager, go to Processes and sort processes by memory.
5. In KDZ Updater, press Launch software update.
6. Keep an eye on the KDZU process in Task Manager, if it starts growing, it means it has started to load the files into memory and you can move to the next step.
7. In Cheat Engine, press First Scan. If it doesn't find anything, you did this too early. It should find 3 addresses. The last one is what you need.
{
"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"
}
8. Copy the found address to CWMInject and press Write Memory. This needs to be done as quickly as possible from the time of finding the addresses.
9. Finish flashing.
Now your phone has CWM recovery installed. You can get into it with "adb reboot recovery". You need the Android SDK for that.
To root your phone, put this Superuser.zip on your SD card and use CWM to flash it.
You don't necessarily have to use KDZ Update. I tried this method with R&D Test Tool and the regular LG Mobile software update. You just need the right process name for CWMInject and Cheat Engine.
That is excellent man. Bin files? Nobody need it anyway. Lol. Profit!
Sent from my LG-P970 using XDA App
Updated the first post with the guide. Cheers
Confirmed, working with V20F from Orange Romania, using R&D Tool.
CWMInject.exe needs to be run as administrator, in case you're using Win as a non-privileged user.
As an interesting sidenote, I forgot to do a factory reset before (coming from Zeus v4.01b), so I got a bootloop. Easy way to get rid of that: flash a V10 based firmware, it won't recognize the ext4 data partition -> no bootloop. Did a factory reset from there, then repeated the flashing for V20F. Worked like a charm.
Amazing!!!!!!
Awesome! With R&D... the process is "LGUserCSTool". After flashing it boots directly to CWM.
CSE Web upgrade test: (Small server)(for a factory reset)
Flashed V20N with R&D.
It works like a charm. Thank you very much.
Great to see it working for everybody!
If you're feeling adventurous, you can test my updated CWMInject. It has a built in memory scanner, so you can just press Start after you've started updating.
Edit:
Oh yeah, it requires .Net Framework 4 now...
roltzy said:
Great to see it working for everybody!
If you're feeling adventurous, you can test my updated CWMInject. It has a built in memory scanner, so you can just press Start after you've started updating.
Edit:
Oh yeah, it requires .Net Framework 4 now...
Click to expand...
Click to collapse
Very nice. I guess the Cheat Engine is no more required.
ETA: maybe it would be a good idea to specify in the manifest that it requires admin privileges.
Yeah, good idea.
I guess not everybody disables UAC as the first thing after installing Windows
gabwerkz said:
Awesome! With R&D... the process is "LGUserCSTool". After flashing it boots directly to CWM.
CSE Web upgrade test: (Small server)(for a factory reset)
Click to expand...
Click to collapse
I have a Question!... When is the best moment to aply CWMInject?? i want to use R&
__________________________
i solve the question, really works so great!!!
I've usually applied it around the 10% mark, so it gets done at 16% or so. It's worked every time, for all the updating software, since the underlying flashing process seems to be the same for each one.
Yeah, it works very well and together with this trick http://forum.xda-developers.com/showthread.php?t=1473781 you can now flash KDZ if it is not for your region.
Didnt work with V20B_00.kdz for India
I did everything as stated in the first post. The Memory of recovery-clockwork-touch-5.8.1.3-p970 was also injected successfully within 10% of flashing. And phone rebooted with new the rom. However, I am not able to get into the CWM. I tried the vol+ hard key while booting, but CWM is not coming. Help!
advptg said:
I did everything as stated in the first post. The Memory of recovery-clockwork-touch-5.8.1.3-p970 was also injected successfully within 10% of flashing. And phone rebooted with new the rom. However, I am not able to get into the CWM. I tried the vol+ hard key while booting, but CWM is not coming. Help!
Click to expand...
Click to collapse
roltzy said:
Hey guys ...
Now your phone has CWM recovery installed. You can get into it with "adb reboot recovery". You need the Android SDK for that...
Click to expand...
Click to collapse
for short messages
What is this for?
What is this Android SKD? how is such injection of CWM useful?
It is simple. With CWM injection you can root every KDZ. And with KDZ firmware update fix, you can use R&D Tool and flash KDZ to your phone.
Nice thread.. My sister just got an optimus black, ( And i want to root it) does this method should be with the phone on download mode or what ??
Not very familiar with the way optimus root process is done. I own a GS2
EDIT: Well I did with the phone ON, and USB debug mode ON,/ OFF, also have tried doing [Remove battery,sim,SD] hit vol up and inert the usb cable to enter in download mode.. But always when I click Launch Software Update when it starts to decompress the KDZ file it just got frozen, and (Not Responding)
Any clue ? I´m trying to root a v20a (mexican) version.
Thanks.
I can't open CWMInject, I'm on Windows XP...
not what I did wrong, now my phone does not start this brick

[Q] Updating - need help! :(

I have a Kindle Fire HD 7" that was previously rooted. While it was rooted, I used KindleFree to disable OTA updates. Now, I deleted the su binary, uninstalled su, resetted to factory settings, and I can't update.
I downloaded the update and transferred it to "kindleupdates" in storage,
I went to settings > device > about and clicked update.
A brief screen showed up with "Installing OTA update", then it disappeared. The Update button became grey. When I went to the file manager I saw the update was deleted and a file called ".nomedia" was created. I need to update the software to 7.4.8. PLEASE HELP!
Purpose: I want to root, then install fire flash (requires 7.4.8), install TWRP, then install CM11 Unofficial.
Thanks!
EDIT: I saw this on the amazon website.
Update appears to start, but doesn't update the device
Issue: After selecting the Update Your Kindle button, the software update doesn't appear to work.
Cause: The update file may have been renamed, or you have duplicate files on your computer.
Solution: Delete the update file(s) on your computer and Kindle Fire, and then repeat the software update process. Verify that the firewall on your computer isn't blocking downloads from the Internet.
I have no idea what that means..
androidnewbie123 said:
I have a Kindle Fire HD 7" that was previously rooted. While it was rooted, I used KindleFree to disable OTA updates. Now, I deleted the su binary, uninstalled su, resetted to factory settings, and I can't update.
I downloaded the update and transferred it to "kindleupdates" in storage,
I went to settings > device > about and clicked update.
A brief screen showed up with "Installing OTA update", then it disappeared. The Update button became grey. When I went to the file manager I saw the update was deleted and a file called ".nomedia" was created. I need to update the software to 7.4.8. PLEASE HELP!
Purpose: I want to root, then install fire flash (requires 7.4.8), install TWRP, then install CM11 Unofficial.
Thanks!
EDIT: I saw this on the amazon website.
Update appears to start, but doesn't update the device
Issue: After selecting the Update Your Kindle button, the software update doesn't appear to work.
Cause: The update file may have been renamed, or you have duplicate files on your computer.
Solution: Delete the update file(s) on your computer and Kindle Fire, and then repeat the software update process. Verify that the firewall on your computer isn't blocking downloads from the Internet.
I have no idea what that means..
Click to expand...
Click to collapse
Delete the update files from the computer. Pretty straightforward. And btw im 99% sure you don't need 7.4.8 to use FireFlash. Just use Seokhuns guide to install it, keep the rom you want to flash on the KFHD's Sd card before hand, then install the rom, after using fireflash to get twrp plus second bootloader.
miztah1999z said:
Delete the update files from the computer. Pretty straightforward. And btw im 99% sure you don't need 7.4.8 to use FireFlash. Just use Seokhuns guide to install it, keep the rom you want to flash on the KFHD's Sd card before hand, then install the rom, after using fireflash to get twrp plus second bootloader.
Click to expand...
Click to collapse
Thanks, but fire flash DOES NOT work. I open it, it asks for root permissions, I grant it. Then a box pops up saying "fire flash has stopped." And I tried the mentioned tutorial but fire flash doesn't work. Fire flash crashes on startup.. allowed superuser permissions and reinstalled many times but I get a box that says "fire flash has stopped." I tried factory resetting, unroot + reroot, but no avail. I really want fire flash but it crashes on startup!
androidnewbie123 said:
Thanks, but fire flash DOES NOT work. I open it, it asks for root permissions, I grant it. Then a box pops up saying "fire flash has stopped." And I tried the mentioned tutorial but fire flash doesn't work. Fire flash crashes on startup.. allowed superuser permissions and reinstalled many times but I get a box that says "fire flash has stopped." I tried factory resetting, unroot + reroot, but no avail. I really want fire flash but it crashes on startup!
Click to expand...
Click to collapse
Try this instead of fire flash it does practically the same thing. Keep the rom you want to flash on the sd card before hand.
http://forum.xda-developers.com/showthread.php?t=2685414
miztah1999z said:
Try this instead of fire flash it does practically the same thing. Keep the rom you want to flash on the sd card before hand.
http://forum.xda-developers.com/showthread.php?t=2685414
Click to expand...
Click to collapse
Thanks, and again I have some questions..
Does this run on 7.2.4 without screwing things up? The thread mentioned downgrading to 7.2.3 bootloader.. this leaves me utterly confused.
How do I configure the Android SDK for fastboot? I have no idea how to work with that..
What if the device kicks into fastboot but I can't exit fastboot because the drivers aren't working? Then what do I do?
With flasher is it necessary to use fastboot in the process? Will the program kick the device into fastboot?
Is there any risk of the kindle not booting?
Thanks a lot!
BTW may I ask you a favor? If you wouldn't mind can you mind walking me through the process through some chat service, teamviewer, etc. It's fine if you can't too, just asking..
Thanks again
androidnewbie123 said:
Thanks, and again I have some questions..
Does this run on 7.2.4 without screwing things up? The thread mentioned downgrading to 7.2.3 bootloader.. this leaves me utterly confused.
How do I configure the Android SDK for fastboot? I have no idea how to work with that..
What if the device kicks into fastboot but I can't exit fastboot because the drivers aren't working? Then what do I do?
With flasher is it necessary to use fastboot in the process? Will the program kick the device into fastboot?
Is there any risk of the kindle not booting?
Thanks a lot!
BTW may I ask you a favor? If you wouldn't mind can you mind walking me through the process through some chat service, teamviewer, etc. It's fine if you can't too, just asking..
Thanks again
Click to expand...
Click to collapse
EDIT: If you have 7.2.4 you probably won't need to install the 7.2.3 bootloader due to the bootloader only actually changing when the 7.3.x updates came out. Proceed reading
EDIT: If you REALLY need help with this pm me and we can skype.
I'll write a step by step walk through for you. First I will answer your questions.
The program will downgrade by itself.
I am 99.9 percent sure this will work on 7.2.4, because i did it on 7.4.8.
If you install SDK properly Fastboot drivers will work. Drivers will work if SDK is installed properly.
You will need fastboot, and the program will do it by itself as long as drivers are installed properly.
As for risks... There is always a risk. Follow these guidelines when doing this stuff:
Follow Steps Closely
Don't rush it
Don't take risks
Last thing to keep in mind is to keep the rom you want on the device beforehand.
Lets get started.
Step 1: Install the Android SDK if you already haven't. (To check if you have open Command Prompt and type in adb--you should see a list of commands. If you don't see it, google "Install android sdk".)
Step 2: It will automatically install the 7.2.3 bootloader to prevent red screens, so open the flasher tool and backup(optional).
Step 3: Press Step 3. First it will install the 7.2.3 bootloader if you don't already have it. Then it will install the stack override. Then it will disable amazon updates.
PAY ATTENTION NOW FOR THE HARD PART
Step 4: Disconnect your KF. Then turn it off. Press enter, and then plug in your powered off Kindle.
Then it should be done!
miztah1999z said:
EDIT: If you have 7.2.4 you probably won't need to install the 7.2.3 bootloader due to the bootloader only actually changing when the 7.3.x updates came out. Proceed reading
EDIT: If you REALLY need help with this pm me and we can skype.
I'll write a step by step walk through for you. First I will answer your questions.
The program will downgrade by itself.
I am 99.9 percent sure this will work on 7.2.4, because i did it on 7.4.8.
If you install SDK properly Fastboot drivers will work. Drivers will work if SDK is installed properly.
You will need fastboot, and the program will do it by itself as long as drivers are installed properly.
As for risks... There is always a risk. Follow these guidelines when doing this stuff:
Follow Steps Closely
Don't rush it
Don't take risks
Last thing to keep in mind is to keep the rom you want on the device beforehand.
Lets get started.
Step 1: Install the Android SDK if you already haven't. (To check if you have open Command Prompt and type in adb--you should see a list of commands. If you don't see it, google "Install android sdk".)
Step 2: It will automatically install the 7.2.3 bootloader to prevent red screens, so open the flasher tool and backup(optional).
Step 3: Press Step 3. First it will install the 7.2.3 bootloader if you don't already have it. Then it will install the stack override. Then it will disable amazon updates.
PAY ATTENTION NOW FOR THE HARD PART
Step 4: Disconnect your KF. Then turn it off. Press enter, and then plug in your powered off Kindle.
Then it should be done!
Click to expand...
Click to collapse
Thanks a lot! I'll get started today.. though I am kinda confused.
I'm using this tutorial, and is it safe to use Step 13 to 20? Are those necessary? (Tutorial: http://www.theandroidroot.com/how-to-set-up-adb-and-fastboot-with-android-sdk-on-windows/ ) And OTA updater crashes, fire flash won't install too. Does this mean my system is corrupted and anything may happen? (Before I factory reset my KFHD7 was tweaked a LOT and remains may be left) Thanks! BTW my Skype id is androidnewbie123 .
EDIT: Nothing turns up when I type adb in cmd - I have installed the SDK too.
EDIT 2: ADB works, just had to run cmd from adb directory
EDIT 3: What happens if adb doesn't work for some reason in the middle of the tutorial?
Sorry for the immensely large number of questions, just too scared to start without full knowledge of what I'm doing...
And I wanna get started soon..
androidnewbie123 said:
Thanks a lot! I'll get started today.. though I am kinda confused.
I'm using this tutorial, and is it safe to use Step 13 to 20? Are those necessary? (Tutorial: http://www.theandroidroot.com/how-to-set-up-adb-and-fastboot-with-android-sdk-on-windows/ ) And OTA updater crashes, fire flash won't install too. Does this mean my system is corrupted and anything may happen? (Before I factory reset my KFHD7 was tweaked a LOT and remains may be left) Thanks! BTW my Skype id is androidnewbie123 .
EDIT: Nothing turns up when I type adb in cmd - I have installed the SDK too.
EDIT 2: ADB works, just had to run cmd from adb directory
EDIT 3: What happens if adb doesn't work for some reason in the middle of the tutorial?
Click to expand...
Click to collapse
adb wont stop working, adb doesnt work on regular cmd because u didnt set paths.
go to computer, right click and click propteries go to advanced system setting. then go to environ variables, then go to System Varuabels then scroll down to "Path". once u are tehre, click edit and at the end of the line, seperated by semicolon from other pahts, type in where adb is found. for me its " C:\SDK\Platform tools\" stop when u are at the folder its at.
miztah1999z said:
adb wont stop working, adb doesnt work on regular cmd because u didnt set paths.
go to computer, right click and click propteries go to advanced system setting. then go to environ variables, then go to System Varuabels then scroll down to "Path". once u are tehre, click edit and at the end of the line, seperated by semicolon from other pahts, type in where adb is found. for me its " C:\SDK\Platform tools\" stop when u are at the folder its at.
Click to expand...
Click to collapse
Thanks!
Do I need to use steps 13 to 20 on the tutorial I mentioned? And is it fine if you can help me throughout the process using skype? Thanks again
I am so nervous right now
Bump fo' last minute advice
Just do it following my instruction s
Sent from my Amazon Tate using xda app-developers app
Alright, just hope this won't fail..
Sent from my MB865 using XDA Premium HD app
miztah1999z said:
Step 3: Press Step 3. First it will install the 7.2.3 bootloader if you don't already have it. Then it will install the stack override. Then it will disable amazon updates.
Click to expand...
Click to collapse
Well,small correction. My tool installs the stack override and disables the amazon updates. THEN while in fastboot,it will install the 7.2.3 bootloader and other files.
miztah1999z said:
Just do it following my instruction s
Sent from my Amazon Tate using xda app-developers app
Click to expand...
Click to collapse
Do I need to set any ADB variable path/configure anything on my PC before I start? I read a lot of other threads and I'm confusing myself
I was thinking of finishing the scary stuff today (installing the bootmenu and recovery) so yeah.
SafinWasi said:
Well,small correction. My tool installs the stack override and disables the amazon updates. THEN while in fastboot,it will install the 7.2.3 bootloader and other files.
Click to expand...
Click to collapse
BTW I appreciate all the efforts for this tool from you
Does it work on a Kindle 7.2.4 where OTA doesn't work? Thanks.
androidnewbie123 said:
BTW I appreciate all the efforts for this tool from you
Does it work on a Kindle 7.2.4 where OTA doesn't work? Thanks.
Click to expand...
Click to collapse
No problem man. Just trying to help out people like you (and me)
And about your question:it should. Although the Flasher was made for software OS 7.4.6,it should work on any OS version. But it also might give you a bootloop. So be sure to keep a ROM zip and GApps on the sdcard so that you can just install the ROM in recovery.
SafinWasi said:
No problem man. Just trying to help out people like you (and me)
And about your question:it should. Although the Flasher was made for software OS 7.4.6,it should work on any OS version. But it also might give you a bootloop. So be sure to keep a ROM zip and GApps on the sdcard so that you can just install the ROM in recovery.
Click to expand...
Click to collapse
Alright, thanks. And one last thing.. as I posted above.. do I need to set any adb variable path or computer pre-requisites before flashing? Ty in advance I'm kinda new to this stuff..
androidnewbie123 said:
Alright, thanks. And one last thing.. as I posted above.. do I need to set any adb variable path or computer pre-requisites before flashing? Ty in advance I'm kinda new to this stuff..
Click to expand...
Click to collapse
Well,you do need the ADB drivers installed. If ADB cannot recognize your Kindle because of driver issues,then my tool can't do anything at all. Other than that,you don't need to do anything.
SafinWasi said:
Well,you do need the ADB drivers installed. If ADB cannot recognize your Kindle because of driver issues,then my tool can't do anything at all. Other than that,you don't need to do anything.
Click to expand...
Click to collapse
Thanks for the quick help
Now I can finally start after months of waiting xD
I just hope I don't get my Kindle Fire bricked..
Thanks again for this tool which simplifies the steps!
EDIT: Can't get into fastboot using the tool no matter what
I installed stack override and I got a message somewhere saying "failed no such directory found" ending with some "installation.sh" or something. I can't verify the device either. I only have a normal USB cable. When I plug that in my KFHD just turns on and doesn't go into fastboot. Please help! I only managed to backup the system and stuff. Only the stack override is installed now (I think)
Help! Ty
EDIT #2: Stuck on <waiting for device> and my device just boots normally... when connected to PC and powered off at that step.
I used http://forum.xda-developers.com/showthread.php?t=2588979 to install adb and fastboot drivers plus google phone drivers. I also have the SDK..
{
"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"
}

[GUIDE] LG L Fino Reflashing stock ROM (D290N, D295)

Flashing stock ROM on LG L Fino​
Since the device is pretty new and there is no other such guide for the Fino I decided to make one.
Flashing stock firmware on LG devices is universal (for the most part) so this guide will be pretty straight up.
This guide should be compatible with both the Dual Sim Fino and the regular one and all variants between them N/F/G etc.
I will try to make this as noob friendly as possible.
Click to expand...
Click to collapse
__________________
Flashing a stock ROM:
Can unbrick the device (only if softbricked)
Will remove root
Can Wipe user data
Can brick device (If done incorrectly)
__________________
STEPS:​
STEP 1: Download and Install the LG DRIVER from here.
You might want to restart your computer after driver installation.
STEP 2: Download LG FLASH TOOL 2014 from here and extract it IN a NEW folder somewhere.
STEP 3: Download a KDZ firmware file from here
BE SURE YOU ARE DOWNLOADING THE RIGHT FIRMWARE FOR YOUR DEVICE (D290N, D295 and so on) OTHERWISE YOUR DEVICE MIGHT BECOME A HARD BRICK!!! LOOK FOR THE DEVICE MODEL BEHIND THE BATTERY!
Click to expand...
Click to collapse
STEP 4: Extract the FIRMWARE.KDZ file IN the same folder as the LG FLASHTOOL 2014.
STEP 5: Enter DOWNLOAD MODE on the device. You can do that by connecting a USB cable to the computer and then pressing and holding the VOLUME UP button while inserting the USB in to the phone.
STEP 6: Start LGFlashTool2014.exe. You should have something like this open:
{
"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"
}
STEP 7: In type ALLWAYS choose CDMA.
STEP 8: IN KDZ browse to the KDZ file you extracted earlier and select it.
STEP 9: Select Normal or CSE Flash
Normal Flash: Flash the ROM on top of the current one ( Good for updating firmware)
CSE Flash: Flash the ROM after WIPING EVERYTHING. (Good if testing new ROM or restoring a brick)
Click to expand...
Click to collapse
STEP 10: After selecting either you will be transferred to another screen with data on it. Don't edit anything and just click START
STEP 11: After that you will be yet again transferred to another screen like this:
Dont change or tick anything and just click OK
STEO 12: After that the process of FLASHING will begin.
THIS PROCESS CAN'T BE STOPPED SO BE SURE YOU HAVE EVERYTHING NEEDED TO WAIT FOR 5-20 MINUTES FOR IT TO COMPLETE.
DO NOT UNPLUG THE DEVICE UNTIL IT HAS FULLY BOOTED!
Click to expand...
Click to collapse
If you get an error saying something about failed downloads and whatnot DO NOT CLICK ON ANYTHING! and wait about 15 minutes. The program might just display these errors but the process will continue.
Do not worry if the program says disconnected or crashes at the end of the procedure. This is normal
STEP 13: Enjoy your reflashed device
__________________
By following this guide you agree that I TAKE NO RESPONSIBILITY FOR BRICKED OR DAMAGED DEVICES.
You and only you decided to follow these instructions.
Click to expand...
Click to collapse
Download the KDZ you need here: https://lg-firmwares.com/
johnwilliam_a_k_a_trash said:
Nice tutorial!
Click to expand...
Click to collapse
Thanks
Glad to help.
Does anyone experimented issues installing drivers? I've installed several versions and it still not detecting/recognizing the device and searching for drivers in windows update. (Windows7, D290n).
---------- Post added at 12:36 PM ---------- Previous post was at 12:05 PM ----------
carmeloamg said:
Does anyone experimented issues installing drivers? I've installed several versions and it still not detecting/recognizing the device and searching for drivers in windows update. (Windows7, D290n).
Click to expand...
Click to collapse
SOLVED: After disabling windows update, uninstalling every single driver version for the device, unplugging network connection and reinstalling drivers (4.0.3) it worked. Thanks and hope help if it is your case.
Ok so i tried to flash kdz file but on 60% it say "The phone is disconnected from PC" What should i do?
cyber808 said:
Ok so i tried to flash kdz file but on 60% it say "The phone is disconnected from PC" What should i do?
Click to expand...
Click to collapse
You can start over... But this time check that the USB connection is stable and the drivers are all updated
Lg l fino hardbricked!
Hi! i'm a newbie here, can you teach me to unbrick a hardbricked lg l fino? no download mode and it says boot security error, it has been days solving this problem ...
micoevil said:
Hi! i'm a newbie here, can you teach me to unbrick a hardbricked lg l fino? no download mode and it says boot security error, it has been days solving this problem ...
Click to expand...
Click to collapse
Deppends if it really is hard bricked. Can you enter download mode?
meganukebmp said:
STEP 5: Enter DOWNLOAD MODE on the device. You can do that by connecting a USB cable to the computer and then pressing and holding the VOLUME DOWN button while inserting the USB in to the phone.
__________________
Click to expand...
Click to collapse
I have LG L Fino D295. I cannot enter to Download Mode as there is error message "error boot certification verify" and then the device goes black. By removing the battery, put it back and press power button the phone goes normally. Any solution for cannot entering the Download Mode?
I found this thread: http://forum.xda-developers.com/showthread.php?t=2582142 but I couldn't find the files needed (sbl1.img, aboot.img, rpm.img, tz.img) which I assume the stock files for LG Fino L D295. And not really sure this will help me to enter the Download Mode.
Just as background: when I update the firmware via OTA, the system says that my phone is suspected to be rooted. since then my camera is not working. Clear cache and data didn't help.
Any suggestion would be appreciated.
thenks bro
Hello, I have a problem because after installing TWRP on Lg l'fino from time changed the android I changed not at all aboot on orginale and call me zbrickował
I wanted to install in new home Stock for lg flash tool because tele enters into download mode but as it starts to upload new stock becomes 2% percent and pops it failed Tele. 100% charged and detectable packages for Windows
Could anyone help ?? Thanks in advance: D
My English is poor
rohanekpl said:
Hello, I have a problem because after installing TWRP on Lg l'fino from time changed the android I changed not at all aboot on orginale and call me zbrickował
I wanted to install in new home Stock for lg flash tool because tele enters into download mode but as it starts to upload new stock becomes 2% percent and pops it failed Tele. 100% charged and detectable packages for Windows
Could anyone help ?? Thanks in advance: D
My English is poor
Click to expand...
Click to collapse
Try reinstalling LG driver and try plugging in another USB port on your PC.
So I tried to do some driver version I installed, each USB port podłanczałem and all the time is this problrm on your computer is at 2% and continue on your 0% and nothing happens, I wanted to also add that when I turn on the tele. normally it shows the logo lg and the phone vibrates at some time after 2 times,Lg phone detects a mobile phone but the phone installs the first time you connect it does not want to load up to the end,
maybe this is the problem that you have Windows 10 ?? Maybe it is going to change a recovery program ?? and not by the emulator
---------- Post added at 02:49 PM ---------- Previous post was at 02:27 PM ----------
proudlytm said:
Try reinstalling LG driver and try plugging in another USB port on your PC.
Click to expand...
Click to collapse
So I tried to do some driver version I installed, each USB port podłanczałem and all the time is this problrm on your computer is at 2% and continue on your 0% and nothing happens, I wanted to also add that when I turn on the tele. normally it shows the logo lg and the phone vibrates at some time after 2 times,Lg phone detects a mobile phone but the phone installs the first time you connect it does not want to load up to the end,
maybe this is the problem that you have Windows 10 ?? Maybe it is going to change a recovery program ?? and not by the emulator
I flashed my d290g with a d295 firmware to install a rom on it. Now I'm trying to flash the original firmware with the flash tool but I can't manage to flash it, I've tried adding the d290 unlocked bootloader but it's still not flashing. Is there anyway to force the flash tool to install the firmware without checking the model of it or to make a flasheable zip for TWRP with the d290g firmware?
LG L Fino Hard Bricked
Hi. Sorry for me english.
I have LG L Fino (D290N) and me phone hard bricked. when I instal TWPR with aboot.img and rashr application me phone reboot and I have purple screen with DBI Apps Watchdog Reset or black screen all time. No have logo LG, only black screen. No have download mode, recovery mode, fastboot mode. Cant reperair with LG Support tool because have error with me baterry not full charging.
What I must doo to unbricked my phone ? Please help me
To everyone that has hard bricked their phone:
There is no fix of hard bricked LG L Fino we are aware of as of now!
The only way out is to give your phone to warranty service and get it replaced or get its motherboard replaced!
Please, note that you should be very careful when typing these two commands, installing aboot and recovery!
You are doing this at your own risk!
D290 firmware link dead.. File not found... Please post another mirror link.. I need this firmware urgent.... D290
Abdul.wahid9001 said:
D290 firmware link dead.. File not found... Please post another mirror link.. I need this firmware urgent.... D290
Click to expand...
Click to collapse
Links are not dead. Just download for another region.
i can'tf find custom ROM for this device. How did you found?
Hiparci said:
i can'tf find custom ROM for this device. How did you found?
Click to expand...
Click to collapse
Me and my friends made it.

[FRP] Google Verification Bypass

Hey,
I just received an old tablet (SM-T813) that the IT department at work was selling off. However, when I went to setup the tablet, I was met with the Google Verification Screen. I went to the department and they had no idea whose email it previously belonged to so there is no way I can find out who to reach out to to sign in. I have looked online and seen the old ways to bypass it but it seems they've all been patched. I tried
1.) Turn off hot spot when it says software update
2.) Use rootjunky/Realterm to open dialer (I have wifi only so dialer doesnt show up)
3.) Sidesync (Doesnt show up on phone even though phone is recognized on computer)
4.) I have tried using Odin and flashing the newest firmware from Sammobile but the verification screen still shows up during setup
5.) Access to get to settings from Google keyboard or Voice doesnt seem to work.
I know this has been posted before but I wanted to know if there has been any new tricks or tips since new patches have come out. I'm running 6.0.1 Marshmellow and just want to be able to use this tablet. I dont have any data on it so I am willing to 100% wipe it. Thanks
skatekid1792 said:
Hey,
I just received an old tablet (SM-T813) that the IT department at work was selling off. However, when I went to setup the tablet, I was met with the Google Verification Screen. I went to the department and they had no idea whose email it previously belonged to so there is no way I can find out who to reach out to to sign in. I have looked online and seen the old ways to bypass it but it seems they've all been patched. I tried
1.) Turn off hot spot when it says software update
2.) Use rootjunky/Realterm to open dialer (I have wifi only so dialer doesnt show up)
3.) Sidesync (Doesnt show up on phone even though phone is recognized on computer)
4.) I have tried using Odin and flashing the newest firmware from Sammobile but the verification screen still shows up during setup
5.) Access to get to settings from Google keyboard or Voice doesnt seem to work.
I know this has been posted before but I wanted to know if there has been any new tricks or tips since new patches have come out. I'm running 6.0.1 Marshmellow and just want to be able to use this tablet. I dont have any data on it so I am willing to 100% wipe it. Thanks
Click to expand...
Click to collapse
I'll come back to you in a bit. I'm at work right now. I have something you can try.
Which firmware build are you running?
I was able to reset a tab A SM-T580 as your description in (1), however after a software upgrade, I test this method again and it failed. Samsung fix it by not letting me continue without Wifi connection to verify the Google account. You can try but I am not able to find the newest working method to bypass this FRP. I did more than 10 times but failed miserably until using my ID and password used with this tablet to unlock it.
Anyway, if you don't mind pay $10 for someone do the work
http://www.ebay.com/itm/Remote-Goog...848348?hash=item4b07596d1c:g:EYoAAOSwmfhX73K8
ashyx said:
I'll come back to you in a bit. I'm at work right now. I have something you can try.
Which firmware build are you running?
Click to expand...
Click to collapse
When I boot to the recovery screen it says I'm running 6.0.1/MMB29M/T813XXU2APK6.
skatekid1792 said:
When I boot to the recovery screen it says I'm running 6.0.1/MMB29M/T813XXU2APK6.
Click to expand...
Click to collapse
1. Install T813XXU1APD4_eng_boot.tar via ODIN
The device should boot with ADB Enabled. Connect the USB cable and use the command below using ADB in a Terminal. I suggest to copy and paste.
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
2. Now Open Settings and then from about menu tap 7 times on build number to get devolper mode enabled . Enable OEM Unlocking, now Factory Reset From Settings .
3. If Above command does not work try the following commands:
adb shell am start -n com.google.android.gsf.login/
or
adb shell am start -n com.google.android.gsf.login.LoginActivity
You can also try the tool below after installing the eng boot:
GSM Flasher ADB Bypass FRP Tool
.
Does your file work only for the T813 ? When install using Odin, it's for BL or AP ?
Beut said:
Does your file work only for the T813 ? When install using Odin, it's for BL or AP ?
Click to expand...
Click to collapse
Yes T813, flashed in AP.
Why do you ask?
I tried to flash the ADB enable file which for SM-T580 and it failed to install
FRP is enable, not allow to download non-FRP boot binary
{
"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"
}
Beut said:
I tried to flash the ADB enable file which for SM-T580 and it failed to install
FRP is enable, not allow to download non-FRP boot binary
Click to expand...
Click to collapse
Where did you get it and which firmware is your device running?
ashyx said:
Where did you get it and which firmware is your device running?
Click to expand...
Click to collapse
My current firmware is the latest AP_T580UEU2APL4 for Tab A 10.1, SM-T580. It seems Samsung has patched all loopholes from recent update. I have tried various methods but none is working.
The enable ADB I downloaded from here
http://www.gsmplayer.com/adb-enable-files/
Beut said:
My current firmware is the latest AP_T580UEU2APL4 for Tab A 10.1, SM-T580. It seems Samsung has patched all loopholes from recent update. I have tried various methods but none is working.
The enable ADB I downloaded from here
http://www.gsmplayer.com/adb-enable-files/
Click to expand...
Click to collapse
So what is your current status, you are blocked at Google verification?
Can you post that file so I can take a look?
ashyx said:
So what is your current status, you are blocked at Google verification?
Can you post that file so I can take a look?
Click to expand...
Click to collapse
Yes it's blocked at Google verification, the new firmware will not allow to go further without internet connection. Reconnect, it will go back to previous steps until the step of Google verification,
ashyx said:
1. Install [] via ODIN
The device should boot with ADB Enabled. Connect the USB cable and use the command below using ADB in a Terminal. I suggest to copy and paste.
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
2. Now Open Settings and then from about menu tap 7 times on build number to get devolper mode enabled . Enable OEM Unlocking, now Factory Reset From Settings .
3. If Above command does not work try the following commands:
adb shell am start -n com.google.android.gsf.login/
or
adb shell am start -n com.google.android.gsf.login.LoginActivity
You can also try the tool below after installing the eng boot:
[]
.
Click to expand...
Click to collapse
After I flash T813XXU1APD4_eng_boot.tar with Odin onto my tablet, it gets stuck in a boot loop. When I power it on, it shows the Samsung Logo screen and then the battery power screen. I cant get the setup process to start so that I can use a Terminal to type in those commands.
skatekid1792 said:
After I flash T813XXU1APD4_eng_boot.tar with Odin onto my tablet, it gets stuck in a boot loop. When I power it on, it shows the Samsung Logo screen and then the battery power screen. I cant get the setup process to start so that I can use a Terminal to type in those commands.
Click to expand...
Click to collapse
Looks like the boot.img is not compatible with your firmware build.
I'll see what I can do about getting the up to date eng boot.
skatekid1792 said:
After I flash T813XXU1APD4_eng_boot.tar with Odin onto my tablet, it gets stuck in a boot loop. When I power it on, it shows the Samsung Logo screen and then the battery power screen. I cant get the setup process to start so that I can use a Terminal to type in those commands.
Click to expand...
Click to collapse
If you need the stock BL ( Boot Loader ) , use Odin and load it to BL, then start.
http://www.mediafire.com/file/7k0ohync9eeslnb/SM-T813+Bootloader.rar
BL_T813XXU2APK6_CL9829844_QB11715585_REV00_user_low_ship_MULTI_CERT.tar
Beut said:
If you need the stock BL ( Boot Loader ) , use Odin and load it to BL, then start.
http://www.mediafire.com/file/7k0ohync9eeslnb/SM-T813+Bootloader.rar
BL_T813XXU2APK6_CL9829844_QB11715585_REV00_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
even with the boot loader put into Oden, it is still having the same issues.
skatekid1792 said:
even with the boot loader put into Oden, it is still having the same issues.
Click to expand...
Click to collapse
You can try the AP and BL, AP is from Sammobile. If it works fine before, it should boot normally after re flash the stock AP and BL.
ashyx said:
Looks like the boot.img is not compatible with your firmware build.
I'll see what I can do about getting the up to date eng boot.
Click to expand...
Click to collapse
where could I find the eng boot that is compatible with my firmware build? Even when I recovery boot and go to the "apply update from adb", the commands I run all say error:closed in the terminal
I'm in the same boat sm-t580 usa version with a frp lock and since it doesn't have a sim you can't get the dialer to work or any of the other techniques. The question is will it let you via odin downgrade the software or not. Are there any other things to try to get a browser window to pop up, even if I could get the sandbox browser I usually can get past that but right now I can't get anything to work.
thanks
Update I downgraded to an earlier august release via Odin but still none of the old ways to break in are working, anyone have any suggestions please let me know.
Thanks

Question Custom Binary Blocked by OEM Lock - Edit: it was the bootloader

Today the A33 5G 128GB arrived, to flash twrp on it i had to enable oem unlock and usb debugging first in develeoper options.
To do that i had to complete the setup first, it's sick that the phone did NOT even let me complete the setup without connecting to the internet... this is out of control.
Now, i have oem unlock enabled aswell as usb debugging.
{
"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"
}
Next i connect the phone to PC and booted in download / odin mode.
Then i tried to flash this a33x_experimental_twrp.tar created by Zillion with odin, however as you can see on the next screenshot... the phone says "Custom Binary Blocked by OEM Lock"...
Why does the Phone say Custom Binary Blocked by OEM Lock even when i have it enabled in developer options??!
The Phone-Model is SM-A336B/DSN if that matters? I contacted my service provider from who i bought this phone and they told me that they are selling only this model.
Any help is welcome ...
My last hope is that someone from this forum can help me get twrp and lineage running, otherwise i'll have no choice but to return the phone within 14 days. No way i will use this device with the sick psycho spyware it contains.
PS: My only idea that might be worth a shot is booting twrp from adb terminal on pc, but i'm not sure how that works, how do i flash twrp permanently and how do i flash lineageos from adb, while i might be able to flash lineageos i'm not sure if that would work with the stock recovery..?
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
You can also use Adb ( Adb reboot download)
Privacydroid said:
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
Click to expand...
Click to collapse
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
V0latyle said:
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
Click to expand...
Click to collapse
Thank you Sir. i totally forgot about the bootloader, and i didn't know how it works on the newer models (android 12), thanks to your easy insturctions i was able to unlock the bootloader.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Privacydroid said:
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Click to expand...
Click to collapse
See Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
V0latyle said:
See Magisk installation instructions:
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
Click to expand...
Click to collapse
Well, i tried flashing twrp right now without using magsik, might have been a bad idea.. there's some error now.
Not really a surprise.. i never managed to brick a phone by all the idiotic things i'f done, no clue how to perceed now as the phone keep rebooting to the exact same screen with the exact same error message.
Did i damage the recovery?
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Arealhooman said:
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Click to expand...
Click to collapse
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
Privacydroid said:
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
View attachment 5790277
Click to expand...
Click to collapse
Yes.
Guide to Extract Stock Recovery:​
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Btw its in the AP file
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
Indeed the twrp i tried to flash is experimental and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Arealhooman said:
Yes.
Guide to Extract Stock Recovery:​
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Click to expand...
Click to collapse
Thanks, i managed to re-flash the stock firmware!
I actually didn't want to whole system (the os) the be re-flashed but only the recovery, however when i extract the AP file i do not get any recovery.img file.
`
Edit: i see recovery.img.lz4 (can i use that aswell to re-flash stock recovery, i never saw .lz4 whatever that is.
I tried flashing twrp with odin by placing it in the AP slot, so since that didn't work would it be worth a shot trying to flash it with adb via pc instead? Or is magisk a hard requirement now to bypass Vaultkeeper to be able and flash twrp?
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
actually theres a way of repacking using lz4 images, but i dont really know how to do it
Privacydroid said:
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
View attachment 5790319
Indeed the twrp i tried to flash is experimentla and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Click to expand...
Click to collapse
Wich device is that
*A33 TWRP was never meant for final users
The latest build was just a testing one

Categories

Resources