AT&T to JME boot/recovery fix - Galaxy Tab Android Development

Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders

thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?

quickk said:
thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?
Click to expand...
Click to collapse
I can confirm that this works, but, since we don't have stock bookloaders for at&t, its a one way trip. If you go back to the stock at&t firmware that I built, it will boot blank and you wont be able to see the stock recovery screens.
Its not perfectly safe in that if you fail to flash JJ4 bootloaders you can brick your tab. But once you have them, your tab becomes perfectly compatible with the euro firmware.

So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Sent from my GT-P1000 using XDA App

alexnoalex said:
So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Click to expand...
Click to collapse
I only know the results. Anyone who has flashed them back, either through Odin, Heimdall or dd has created a brick.

alexnoalex said:
Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders
Click to expand...
Click to collapse
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?

Jeepsdaddy said:
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?
Click to expand...
Click to collapse
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment jj4_bootloaders.zip

rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment 496999
Click to expand...
Click to collapse
Yes I did the RotoBackup per your instruction.
I'd prefer to wait until it is no longer a one way ticket. I need to be able to return to stock. The way I understand it now is that I can easily return to stock from my current state. Is that correct?

From Chat. To test with JME v4

Jeepsdaddy said:
From Chat. To test with JME v4
Click to expand...
Click to collapse
What are we testing with the swype?

Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.

rangercaptain said:
Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.
Click to expand...
Click to collapse
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.

Thank you Roto-Amigo. The jj4 bootloaders flashed though odin in the pda spot, now the at&t tab has the logo restored, the black screen and white line is gone.

Failed to update
Hi!
I tried this with the attached file, and had no success. As I'm quite unfamiliar with Odin, I will post an image of the failure but I lack debugging know-how with this tool. I'm willing to do whatever, but don't know what "whatever" is.
I appreciate any advice, especially with the information-gathering process. (Note: I did download again, from a different computer, with the same result.)
{
"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"
}

Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.

rangercaptain said:
Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.
Click to expand...
Click to collapse
Sheesh, I had not been in download mode. In my (weak) defense, I had only done this once - and that's to apply JME4. I'll get better. The patch is applied and all looks well! Thanks for your indulgence, and for the prompt!
I knew the drivers were correct since nothing has changed on this PC (haven't used it) since applying JME4 to the Tab. I'll have a quick search for chainfire's bootloader patch.

rotohammer said:
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.
Click to expand...
Click to collapse
Hello rotohammer, sorry to bother you but I'm having a problem that I cannot seem to fix. Can you kindly see my post to see if you can help me? You seems like the one who knows the a lot about the AT&T Galaxy Tab. Thanks in advance for your help!
http://forum.xda-developers.com/showthread.php?p=11333386#post11333386

fixed me up!
rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
....
I only recommend this firmware for AT&T Tabs that have the screen problems.
View attachment 496999
Click to expand...
Click to collapse
totally fixed my blank screen booting! thanks!!
ATT Galaxy Tab, stock to Roto JME v1
Fixed Blank Boot w/Line w/jj4 bootloaders

hi guys,, i have tab that stuck at galaxy tab logo,, it cant access recovery mode but download mode is still ok.. ive tried many thinks including flashing pit and rotov4. but no luck. it always 'pass' but stuck at galaxy tab logo..
so my question is, can my tab ( arabic tab) be flashed with this jj4 so it can be normal again?..
thanks

Related

ClockworkMod Recovery for Galaxy S (BETA BEWARE)

WARNING: From koush' IRC channel it seems this version may be (permanently?) bricking devices.
At the time of this writing only a single working flash has been reported, and several (full?) bricks.
--Chainfire
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
{
"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"
}
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
932e5f7a9f09c9bc33b14a527f642933
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Wow!... Looks great!
Wanna try after going back home!
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Koush said:
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
Installation instructions:
Install Odin3
Start Odin3
Press PDU
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Click to expand...
Click to collapse
Can I assume this kernel wasn't compiled with ext3/4 support?
achio1115 said:
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Click to expand...
Click to collapse
I'm guessing, but considering this replaces the zImage that mimocan's fix provides anything you have on moved to ext3/ext4 will not be accessible.
To reverse reflash with the mimocan kernel.
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Chainfire said:
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Click to expand...
Click to collapse
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
damianarnold said:
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
Click to expand...
Click to collapse
I can confirm that, this mod won't work if you have mimocan's kernel applied.
Does it work if you "unapply" it ? Can you get your phone back functional again ?
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
raspdeep said:
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
Click to expand...
Click to collapse
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
damianarnold said:
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
Click to expand...
Click to collapse
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Chainfire said:
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Click to expand...
Click to collapse
Every single app. you've installed will need to be reinstalled, it's as if the device is completely cleared of any settings/config.
Basically you need to restore from backup.
If you see this screen
follow these commands while odin3 is opened.
"SIM+SD out, put the battery in. Plug in USB. Hold down both Volume keys, and then push power. Hold it. From the phone > pc screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power. " That should put you in download mode so you can install the recovery again.
Then flash this kernel to fix any slowness
http://android.eugenekay.com/Vibrant/LeshakKernel_9_01b9.tar
Eugenekay couldn't link because he only has 4 posts so I'm doing it for him
This might not apply to i9000 users but I posted it just encase.
Also any flashing done in odin formats everything. That is why recovery is needed in order to try and get zip updates. Zip updates wont allow a whole rom flash just modifications.
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
so are there gonna be roms in zip ?
or this recovery is gonna handle tars as well?
buddy01 said:
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
Click to expand...
Click to collapse
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
not working on JF7, keeping on rebooting
Chainfire said:
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
Click to expand...
Click to collapse
fair enough.
hkfriends said:
not working on JF7, keeping on rebooting
Click to expand...
Click to collapse
Does the same thing on JG5...
When I first applied it, it rebooted itself twice in a row and booted fine. It ran for a good few hours... restored apps. from titanium backup. Did a reboot again. (just to be safe.) At that point, it kept rebooting itself... and then I pretty much gave up and flashed the stock JG5. (couldn't head to work w/o a working phone, lol) Anyone got it to work so far?

[ROM][D802]80220B EUR Open KITKAT Flashable ZIP With Custom Recovery Working!

This is only what has worked for me i take no responsibility for anyones phone catching fire after following my guide/advice. Tested myself on a UK D802 16GB on Three Network! Confirmed working on 32GB devices now too!!
This needs formatting to make it easier to read. I will get around to it but here is the basic info needed!
Please READ this entire first post before asking questions that are already answered.​
Today i have managed to flash the European Open Kitkat rom and root it and keep TWRP recovery. It worked for me but can't guarantee the same results for you.
Prerequisites. (Skip this if you already have rooted JB rom with custom recovery)
First i downgraded to Jellybean using this guide. I downgraded to "UK Open 16GB D80210B_00.kdz" i'm not sure if that's required though.
Then I rooted it using IORoot.
Then i installed TWRP using Freegee from the Play Store.
From here you are ready to flash or you can start from here if you already have root and recovery on Jellybean.
You need these three files.
1. My modded Stock rom zip.
Mirror 1 | Mirror 2
2. Savoca Modded Boot.img.
3. SuperSU ZIP.
Now to flash! (Take out your simcard first.)
1. Boot into TWRP and flash the modded stock rom DOWNLOAD 1. It will take a while and the screen may turn off during this, just press power button. Ignore the failed error!
2. Now go to main TWRP screen and select Reboot Recovery. (Wouldn't mount system otherwise!)
3. Now go to Mount and make sure System is ticked. (Not sure if required but do it anyway!)
4. Now flash Savoca's modified boot.img DOWNLOAD 2.
5. Again go to Mount and make sure System is selected.
6. Now flash SuperSU ZIP DOWNLOAD 3.
7. Now i wiped data here not sure if it's required as the rom wipes system but do it anyway!
8. Replace sim and reboot and all should be well!
If you have NO MOBILE NETWORK i got this error and that's why i recommended removing sim card. I had to repeatedly toggle wifi on and off, and airplane mode and restarted a few times. Not sure what fixed it but don't panic it DOES work.​
Bugs and Fixes!
Audio Hissing/Crackling on Headphones.
This is present on all Kitkat roms currently. Some users don't get it most do. Type of headphones seems to be a factor. The following fix is temporary and will revert after a reboot. So needs to be repeated if your phones reboots for any reason.
Type in phone dial pad 3845#*802# and it will show Hidden Service Menu.
Click on "ELT Test", select "Manual Mode" and select "Test Start".
With headphones plugged in select "Audio Loopback" and than select "Test Start".
Blow gently into the microphone and keep on this test 20 seconds or more.
Once done back out and play music. Enjoy!
No LTE/4G anymore?
It seems to require a change of bands for some to get LTE working. There is a value to edit in build.prop. You can do this manually with a root explorer and setting correct permissions after changing, I've found the easiest way is to download JRummy Build.prop editor from market.
Open the Build Prop Editor app.
Find the value "ro.telephony.default_network" and select it.
Notice the property value will be set to "9". Change this to "11" and let the app reboot phone.
If you still don't have LTE try again but change the value to "13" and let the app reboot phone.
Bluetooth Battery Drain
This is NOT real battery drain so please don't worry about it. It is a falsely reported statistic. I get battery life on a par with 4.2.2. Around 8 hours screen on time which is fantastic! If you have battery drain please try a full wipe, don't restore apps from another rom do it manually. Take a look at your apps.
How is it done?!
The modded zip is stripped down to include only the System, Modem and Cust partitions. These are all that is required for Kitkat to play nice with Savocas modified boot.img. I edited the updater-script to remove the entries for all partitions except those listed above and repacked it up nicely to flash. So it is possible to do this with any future updates too. The Cust partition is necessary in case your partition has old carrier stuff still on there, this flashes a clean Cust partition.
Thanks to:
LenAsh for the flashable zip i modded.
Savoca for the modded Boot.img and modules.
Chainfire for SuperSU.
Jesus for blessing all the little children.
it would be great if you also make one for the 32gb version
anyways, great work, dude!
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
superbonto said:
it would be great if you also make one for the 32gb version
anyways, great work, dude!
Click to expand...
Click to collapse
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
paniczklos said:
I'm flashing it right now and looking up your address at the same time in case it won't work ;]
How long should it take to boot ?
Click to expand...
Click to collapse
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
ephumuris said:
As i've said it seems like there isn't a difference between md5's of 32gb and 16gb versions of Kitkat i just wouldn't want to say test it... But in theory it should work just fine.
Let me know how it goes...you know just to give me a running start I assume you're 16GB user? It doesn't take long to boot but if it loops make sure you have wiped data in recovery. It is safe to do factory reset in standard recovery too as i tried it when trying to get my network back on!
Click to expand...
Click to collapse
I'm preparing a dead fish to throw it on your doormat ;p
I'm on 12th minute of booting - LG logo and led flashing green-to-blue.
And yes I'm 16GB
How to use the standard recovery ?
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated.
{
"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"
}
Sent from my LG-D802 using Tapatalk
SPBoss said:
Hey TC i have a lg g2 16gb that i bought from amazon. I am also on the three network in the uk. I do not get 4g option on my phone. Sorry for OT but i havent met anyone else on here using three and g2. Any help would be appreciated. View attachment 2630159
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
What rom are you running? I get the option for gsm/wcdma/lte auto. Although no 4g for me on Three in Hull yet.
badchip said:
Can you please tell us how to mod the original EUR kdz? I can't download 2 gigabytes now and I already have the kdz file. Is there any guide?
Thanks ephumuris
Click to expand...
Click to collapse
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
ephumuris said:
Is it repeatedly making the boot sound? Hold power button and volume down until LG logo flashes up, then release power button and press again whilst keeping hold of volume. You should get a white screen. Just press power twice i think that should reset it.
I'm pretty sure it didn't take me 12 minutes to boot
Click to expand...
Click to collapse
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
paniczklos said:
Doing that boots the TWRP. i've wiped the data like a satan, in every possible way. There's no boot loop - it's just booting and booting and booting. I think I'll have to go back to stock and repeat. Or is there any way to upload files to the phone through recovery (I remeber there was this option in clokcwork recovery ) ?
Click to expand...
Click to collapse
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
ephumuris said:
I'm not sure if there is an option in TWRP i've certainly not seen it. I find it strange that you are getting stuck at boot screen... Maybe it matter which JB rom you come from?
My original one was 80210B Euro open rom.
"UK Open 16GB D80210B_00.kdz"
Click to expand...
Click to collapse
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
ephumuris said:
I'm guessing there is some sort of tool to extract the KDZ files and then all you need out of that is system.img and modem.bin and cust.bin... Easy to make an update script or i can upload one for you. I've never needed to extract a KDZ though...
Click to expand...
Click to collapse
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
paniczklos said:
D80210A_00.kdz - it's EUR open + OTA update to E version.
I'm trying do sideload the files through ADB ;/
Click to expand...
Click to collapse
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
badchip said:
Thanks, I found this guide but it doesn't mention the download from Savoca. Should I just follow it (and use the KKROM_template.zip)? Or what do you recommend? I really can't to flash KK with root on my device
Click to expand...
Click to collapse
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
ephumuris said:
The starting rom is the only thing i can think of that could make a difference if you followed instructions exactly all the factors are the same besides that!
It would help if anyone else has downloaded it and flashed successfully or unsuccessfully to let us know!
Click to expand...
Click to collapse
I'm downloading the UK open EUR and I'll start over.
ephumuris said:
That guide will give you a rooted Kitkat rom but no custom recovery. Which is a risky position to be in
Although the tool would be useful in that thread it would allow you to get the system.img, modem.bin and cust.bin you need. I could then provide a blank update zip with just the correct updater-script for you?
Click to expand...
Click to collapse
I would very much appreciate that. I have used the tool to extract the kdz and dz. I have the files in screenshot now.
Whats the proper next step?
Thanks for your help
edit: The meta-inf folder is from the KK template provided in that thread, I suppose I don't need that.
Hi!
Firstly thanks for this!
and secondly i have to say that i already flashed to my LG G2 32gb and works like a charm... btw i also did it with another way:
1-Downgrade to 4.2.2.
2-when your in v.4.2.2 root and recovery.
3-i used lastest CWM version from Philz.
4-FLash your Rom.zip
5-reboot to recovery. (Dunno if this is really necessary but just in case i did it too)
6-Flash Savoca Patched
7-Flash Root
8-Reboot
9-ENjoy EUR 20b =)
Thanks!
Great to confirm working on 32gb too. Badchip you might have to wait til later unless you can use that existing meta inf folder. I've just left for work so not at laptop.
Try deleting every file but only keep.
Meta inf folder.
System.IMG
Modem.bin
Custom.bin
Zip those up and flash them. Should work if the update script is right in meta inf folder.
@iall5tar What base jellybean rom did you downgrade to?
And regarding custom recovery it should work with any cwm philz or twrp. I just referenced twrp as that's what I use.
Sent from my LG-D802 using Tapatalk
What you mean about folder meta-inf? im not a expert i just want to give a try and it worked xD

[q] can i return to stock?

I just bought a Galaxy S3 from someone and it was already rooted. I am not able to add this phone to my Sprint account because of it. SO I looked up threads on returning the phone to stock and they all say if you have this new update you cannot go back to stock because of this knox warranty and warranty. When I loaded the boot screen thing it says warranty: 0. Or something like that.
So is there a way I can revert back to stock and UNroot my phone??
michaelemerica said:
I just bought a Galaxy S3 from someone and it was already rooted. I am not able to add this phone to my Sprint account because of it. SO I looked up threads on returning the phone to stock and they all say if you have this new update you cannot go back to stock because of this knox warranty and warranty. When I loaded the boot screen thing it says warranty: 0. Or something like that.
So is there a way I can revert back to stock and UNroot my phone??
Click to expand...
Click to collapse
The phone being rooted has nothing to do with activating the phone with Sprint.
If you mean by boot screen download/bootloader mode and you see warranty bit 0, sounds like you already have kitkat (with knox).
Go into settings\about phone and see what your android version is.
And yes you can go back to stock un-rooted.
Get back about your version of android and then you can go from there.
I have version 4.4.2.
The reason I believe this is the reason I cannot activate for Sprint is because I sold a rooted phone to a friend and they could not activate it. I got the phone and unrooted it back to stock and it was able to be put on their account.
But yeah, I think it will work after I am able to unroot it. I'm just nervous bc all of the threads I have found have a warning telling me not to use their method if I have that Knox Warranty in the bootscreen. They said it will hard brick. But most of those threads are from a few years ago. I guess because it's an older phone.
If you could find me a method to return it to stock / unroot I'd appreciate it so much.
That's a new one on me.
I've never heard of root being the cause of activation problems. As long as you are on a tw rom it should work. A quick search would have given you this though http://forum.xda-developers.com/showthread.php?t=2738533
[FULL RESTORE][TAR] Stock ND8 Odin FLASHABLE [4.4.2]
michaelemerica said:
If you could find me a method to return it to stock / unroot I'd appreciate it so much.
Click to expand...
Click to collapse
Ok,
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Then as metalfan78 said, go and get DR CDMA's stock tar file. You will Odin that after you back up.
Get it Here:
http://forum.xda-developers.com/showthread.php?t=2738533
It will restore you completely to stock, un-rooted with stock recovery.
Then use Holo backup to restore.
Thats it.
Does Holo backup work good? I have only used titanium backup for the past 5 years.
Well, I use TiBu exclusively but I wanted to have an alternative incase something went wrong. So just before I finally moved to ND8 I gave it a try and it worked perfectly.
Nice, I'll have to give it a try sometime.
Just note, when you Odin the ND8 tar, it'll wipe your internal storage (not your microSD), so if you've saved any pictures or downloads to the internal storage, copy them to your SD and / or PC / cloud.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
HEY GUYS IT WORKED!
I'm not sure if my phone had a custom rom on it from the previous owner or what. It's an almost brand new phone, no scratches or anything. But my last phone did this same thing only it was easier to find the file to un-root. I want to say it's a Samsung thing... but that could be false. My last phone was a Samsung Epic.
But anywayyy. You guys solved my problem 100% and I appreciate you guys taking the time to help me. XDA is the best. I come here for most everything.
THANK YOU.
michaelemerica said:
HEY GUYS IT WORKED!
But anywayyy. You guys solved my problem 100% and I appreciate you guys taking the time to help me. XDA is the best. I come here for most everything.
THANK YOU.
Click to expand...
Click to collapse
That's great.
Now for the sake of the masses, explain exactly what you did.
jhill110 said:
That's great.
Now for the sake of the masses, explain exactly what you did.
Click to expand...
Click to collapse
-----------
I bought a phone from a friend and called Sprint Customer Care to make sure it wasn't lost/stolen. It wasn't but they still weren't able to activate it because they said my device wasn't supported by Sprint and was not a Sprint device. (It definitely was. It had a Sprint model #, Said Sprint when I booted up, and said Sprint on the back of my phone)
I tinkered with my phone and realized it was Un-rooted by being able to go into Odin download mode. You can go into download mode by simultaneously pressing the power button, home button and volume down key. If it works you are rooted. There may be other ways to check, but that's how I did it.
I was having trouble un-rooting my phone because many threads I came across said I couldn't Un-root my device with their method if I had Knox Warranty on my phone. Their methods were for older android versions. (They said it will brick my device if I did it that way.)
You can figure this out by going into download mode by simultaneously pressing the power button, home button and volume down key. If your device says Knox Warranty or Warranty Bit on the screen then you have the update. SO USE THIS METHOD TO UNROOT / RETURN TO STOCK.
I asked XDA and they gave me this handy little website that allows you to un-root and return to stock with instructions. http://forum.xda-developers.com/showthread.php?t=2738533
***BEFORE YOU DO THIS BACKUP ALL YOUR DATA WITH HOLO BACKUP SO YOU DONT LOSE ANYTHING***
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Click to expand...
Click to collapse
The only other problem I ran into while using this method is downloading the .tar.md5 file. The website wouldn't load the Captcha for me to enter to begin the download. So I looked around and the other one I found was downloading WAY too slow.
SO I found and used this one: http://www.androidfilehost.com/?fid=23487008491966461
It worked perfect.
Instructions:
1. Extract Download file
2. Put phone into download mode (power off, then power button + Volume Down + Home Button (website didn't mention holding the home button but you have to with the S3), then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load File L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5 into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
Click to expand...
Click to collapse
The only thing they forgot to mention and it left my phone stuck on the Samsung boot screen is you must go into Recovery Mode (power off, then Power button + Home + Volume up) and CLEAR THE CACHE.
Reboot your device
Once it boots up call Sprint or talk to a representative online to activate your device and they will walk you through it.
VOILA, YOU ARE GOOD TO GO.
Just so you know, you can get into download mode whether you're rooted or not, being rooted has nothing to do with being able to boot into download mode
http://i1076.photobucket.com/albums/w450/flastnoles11/tapatalk_1379735598798_zpsae07fa91.png
michaelemerica said:
The only thing they forgot to mention and it left my phone stuck on the Samsung boot screen is you must go into Recovery Mode (power off, then Power button + Home + Volume up) and CLEAR THE CACHE.
Click to expand...
Click to collapse
Glad you got it all sorted. I figured that's all you needed.
It doesn't always get stuck like that for everyone. That's a generally good way to fix that kind of problem any time it does happen, though.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Will this work with 4.3 w/knox?
jhill110 said:
Ok,
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Then as metalfan78 said, go and get DR CDMA's stock tar file. You will Odin that after you back up.
Get it Here:
http://forum.xda-developers.com/showthread.php?t=2738533
It will restore you completely to stock, un-rooted with stock recovery.
Then use Holo backup to restore.
Thats it.
Click to expand...
Click to collapse
Will this also work on Android version 4.3?
I have 4.3 with Knox and have rooted my phone and also have loaded Philz Touch 6 (CWM Base Version: V6.0.4.5).
I've attached a screen shot of my complete phone info. I would like to return to stock and upgrade to 4.4.
Thanks!
David
{
"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"
}
abqdavid said:
Will this also work on Android version 4.3?
I have 4.3 with Knox and have rooted my phone and also have loaded Philz Touch 6 (CWM Base Version: V6.0.4.5).
I've attached a screen shot of my complete phone info. I would like to return to stock and upgrade to 4.4.
Thanks!
David
Click to expand...
Click to collapse
Yes, it will work. The tar link is the 4.4 stock tar. Just backup using holo, or backup of your choice, flash the tar, then philz, reroot, profit
Sent from my SM-G900P using XDA Free mobile app

[Q] [HELP] Voicemail broken in 4.4.4

I flashed 4.4.4 and i cant get the voicemail button on the dialer to work. Everytime i press it it shows a menu to add the voicemail number then i go into the settings and its disabled.
I am enclosing screenshots to better describe the problem. I cant post links because of post count. So please copy and paste into your browser to view the images.
puu.sh/cQp2F/3c1b377c2e.png
puu.sh/cQoAV/13f823059b.png
jobrien2001 said:
I flashed 4.4.4 and i cant get the voicemail button on the dialer to work. Everytime i press it it shows a menu to add the voicemail number then i go into the settings and its disabled.
I am enclosing screenshots to better describe the problem. I cant post links because of post count. So please copy and paste into your browser to view the images.
puu.sh/cQp2F/3c1b377c2e.png
puu.sh/cQoAV/13f823059b.png
Click to expand...
Click to collapse
I can't see the images.
You didn't say how or which 4.4.4 you flashed.
Was it the stock firmware, or a custom ROM? How did you flash: OTA, TWRP, CWM or ODIN?
What were you running before?
Did you do a wipe before you flashed?
Have you tried flashing the full stock firmware twice, without rebooting which is recommended with 4.4.4
Rob
rlichtefeld said:
I can't see the images.
You didn't say how or which 4.4.4 you flashed.
Was it the stock firmware, or a custom ROM? How did you flash: OTA, TWRP, CWM or ODIN?
What were you running before?
Did you do a wipe before you flashed?
Have you tried flashing the full stock firmware twice, without rebooting which is recommended with 4.4.4
Rob
Click to expand...
Click to collapse
Hello,
I uploaded the images to imgur if you have any trouble viewing them. I would place full links but the forum wont let me. Copy and paste please.
i.imgur.com/GfLr6KI.png
i.imgur.com/8JGxMV3.png
I was on 4.4.2 before
Also I add another screenshot which shows my software versions
i.imgur.com/u9z8pLt.png
I did a full wipe. Actually not sure, i used CWM and used the option on the menu to do a "clean wipe for a new rom".
I flashed stock 4.4.4 firmware using ODIN.
Then i odin CF auto root, then i odin CWN.
No, i havent flashed twice without rebooting. how do i accomplish that? everytime i flash it reboots. Also how can i perform a full wipe?
jobrien2001 said:
Hello,
I uploaded the images to imgur if you have any trouble viewing them. I would place full links but the forum wont let me. Copy and paste please.
i.imgur.com/GfLr6KI.png
i.imgur.com/8JGxMV3.png
I was on 4.4.2 before
Also I add another screenshot which shows my software versions
i.imgur.com/u9z8pLt.png
I did a full wipe. Actually not sure, i used CWM and used the option on the menu to do a "clean wipe for a new rom".
I flashed stock 4.4.4 firmware using ODIN.
Then i odin CF auto root, then i odin CWN.
No, i havent flashed twice without rebooting. how do i accomplish that? everytime i flash it reboots. Also how can i perform a full wipe?
Click to expand...
Click to collapse
I've attached what my Call Settings says, not the same as yours, and I'm running stock 4.4.4. Mine say "Voice Mail", yours says "My Carrier"
{
"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"
}
My Phone Info shows the same info as yours.
If you did a Wipe for ROM from CWM that should do it.
As to how to flash twice:
Flash the first time, make sure that the ODIN check box for reboot is off. When flash is complete, remove the battery by pulling it, don't press any buttons. Then, wait minute or two, and replace the battery. Go directly to Download Mode and flash a 2nd time. Then, you can let the phone boot into the system.
At that point, before you flash anything else - try the Voicemail.
One, more thing where did you download your 4.4.4 firmware? These are the two that should work:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
http://www.sammobile.com/firmwares/download/34779/M919UVUFNH7_M919TMBFNH7_TMB.zip/
Rob
Hi again,
I think i got the file from the first link the mega one. I just run check on it i got:
M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
md5 8c0e22bc2acccb82418a7cd97121968f
sha1 4fd6bb73fed26f5adc73edb9e168ad119f7dc0a1 d2636786
I am going to flash twice and report back.
well i flashed twice with odin, all stock, same problem.
Is there an alternate dialer i can use that replaces the built in one?
jobrien2001 said:
well i flashed twice with odin, all stock, same problem.
Is there an alternate dialer i can use that replaces the built in one?
Click to expand...
Click to collapse
Does Visual Voicemail work?
Could it be your SIM? How old/new is your SIM.
Another thought is that since you are on a stock ROM, the T-Mobile store may be able to help or calling 611. You could tell them you took the OTA update, and this is what happened.
Rob
lordena and
rlichtefeld said:
Does Visual Voicemail work?
Could it be your SIM? How old/new is your SIM.
Another thought is that since you are on a stock ROM, the T-Mobile store may be able to help or calling 611. You could tell them you took the OTA update, and this is what happened.
Rob
Click to expand...
Click to collapse
Its unlocked and from another carrier. And yes the SIM card is new 2 weeks maybe. Think that could be it? i dont recall the voicemail working on the new sim.
jobrien2001 said:
Its unlocked and from another carrier. And yes the SIM card is new 2 weeks maybe. Think that could be it? i dont recall the voicemail working on the new sim.
Click to expand...
Click to collapse
I would guess that non-TMO carrier has more to do with it than the version. You didn't say which other company's network you were using, but you may want to ask on this thread about the issue:
http://forum.xda-developers.com/galaxy-s4-tmobile/help/using-t-mobile-m919-att-network-t2880349
Rob
jobrien2001 said:
Its unlocked and from another carrier.
Click to expand...
Click to collapse
Wait a minute..... Um that's your problem most likely. Regardless what carrier you're on you need to flash the firmware for your model. What model or what carrier is your phone originally from.
ShinySide said:
Wait a minute..... Um that's your problem most likely. Regardless what carrier you're on you need to flash the firmware for your model. What model or what carrier is your phone originally from.
Click to expand...
Click to collapse
The phone is originally t mobile SGH-M919. I bought an unlock code and my current carrier is movistar (telefonica) peru.

2023 SM-G955U/U1/W Rev8 One Click Root/Safestrap Inject Method

Root Method For S8+ U/U1/W Series Phones Rev8 Bootloader
New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation
Paypal email is [email protected]
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It. Do Not Come In Here And Post This Is Not Working Until You Have Tried It With The USB2 Mini Hub!
You Must Start From Stock U Firmware. IT Seems To Be The Less Likely To Brick Your Device As Explained In The Disclaimer!​Disclaimer Please Read!!
This may brick your device there is a problem especially with s8 and note 8 models where the tz partition becomes corrupted and on some occasions after flashing combination firmware your phone will become bricked and as of now there is no way to fix it. There is no way to predict if it will happen. It doesn’t seem too happen very often on s8+ but it does occasionally happen on the other 2 models so do this at your own risk. I would say it probably happens 10 percent of the time on s8 and note 8 especially when on bit 6 or higher firmwares. S8+ it rarely happens too but it still may. If you take the risk and it happens do not pm me asking how to fix it as of time I posted this there is no way to fix it
Please Read Notes
OEM Toggle Does Nothing On US Model Phones
You will most likely need a USB 2 mini hub for Odin to work if using windows 8 or higher. I would temporarily disable windows defender or antivirus software while performing the procedure with your computer.
You cannot have root on any rom except a nougat rom also flashing custom boot images cannot be done or using systemless magisk. Hiding root or running modules cannot be done. There is no oem unlock and even if there is you cannot unlock your bootloaders or run any aosp based roms.
You can be on any firmware to achieve safestrap but to run a rooted rom you will be limited to using a special nougat android 7 rom. You can have safestrap on pie android 9 which gives you some ability to modify system files flash zips etc and have access too data and other partitions that are normally blocked but you can not run root on android 9 because root on android 9 requires a modified boot image
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Additional Help Can Be Found In The Telegram Channel
Telegram Channel For 8 Series Root
Downloads
Odin3_v3.14.1_3B_PatcheD.7z
SM-G955U_VZW_G955USQU8DUJ1.7z -- Stock U Firmware Flash First In Odin
SAFESTRAP_S8_PLUS_GUI_INSTALLER.7z - GUI 1 Click Method-Recommend!
Alt Method
Safestrap_S8_Plus_Cmd_Line.7z - Command Line 1 Click
Directions Once On Stock U Firmware
If using Safestrap_8_Series_Cmd_Line follow instructions on Cmd screen.
1. Download files and unzip SAFESTRAP_S8_PLUS_GUI_INSTALLER.7z
2. Plug phone into computer and allow access too phone data
3. Run the SAFESTRAP_8_SERIES.exe file. In program choose your model of phone in drop down box then click Root Button and select COMBINATION_FA70_G955USQU8ATG1.tar.md5 file too flash it is packed in the zip you downloaded from above. Everything else is automatically done for you just follow any pop up that come up.
{
"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"
}
4. Phone will reboot too download and flash combo firmware and then reboot. Click dialog stating that it has rebooted and it will inject safestrap all automatically
5. When done you will have a minimal system with safestrap recovery
Instructions For Installing Rom
System Images
system_g955_nougat.7z - Nougat Image That Can Be Rooted
Pie With Safestrap Stock Roms Un Rooted Found Here
Canadian Roms Found Here
1. From here you will either a nougat or pie system image to your phone which will be flashed in safestrap. Reboot to safestrap using the safestrap control app once in safestrap choose wipe then advanced wipe and wipe data. Then goto home screen of safestrap using install tab and the the flash image tab at bottom. Choose system image you copied to phone. System images get flashed too system partition.
2 My nougat system images are not pre rooted if you want for root you will also need too flash a root zip in safestrap.
Root Zips For Nougat Image
EFTSU_System-v20.4_12_28_22.zip​SuperSU_System_12_28_22.zip​Phhs_SuperSU_S8_S9_Series.zip​3. You can enter safestrap anytime on nougat by simply rebooting to recovery which will enter safestrap or by using the safestrap control app
Fingerprint Fix For Nougat Roms
SM_G955U_FINGERPRINT_FIX.exe
4. If fingerprint not working reboot phone too download mode and run this SM_G955U_FINGERPRINT_FIX.exe
Pie With Safestrap Roms
Full Guide found Here
Video Tutorial
Thank You Liset Pedraza
Method In This Video To Obtain Safestrap Has Changed But The Process Of Using Safestrap Still Pertains
S8_Series_Install_Root.mp4
drive.google.com
Credits
klabit87 - Basically Everything
GSMCHEN - The root method
elliwigy -The root method
afaneh92 -Safestrap and too much too mention[/MEDIA]
oakieville - 1 click method
S8 SM_G950U/U1/W Can Be Found Below
2023 SM-G950U/U1/W Rev8 One Click Root/Safestrap Inject Method
Root Method For S8 U/U1/W Series Phones Rev8 Bootloader New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation Paypal email is [email protected].com Before Starting...
forum.xda-developers.com
N8 SM_N950U/U1/W Can Be Found Below
[NEW METHOD][ROOT] [Extreme Syndicate] [Snapdragon][N950U/U1][V8 Bootloaders]
Root Method For S8/S8+ And Note 8 Series U/U1/W Series Phones Rev8 Bootloader This may brick your device there is a problem especially with s8 and note 8 models where the tz partition becomes corrupted and on some occasions after flashing...
forum.xda-developers.com
​
so if i remain at nougat i should be able to flash custom roms? Also, i'm currently facing "no service" problem on my g995u. Any ideas if going back to nougat would rectify the issue?
jrkruse said:
Rooted Nougat Rom​
This is last nougat rom made for S8 it is prerooted with flashfire and safestrap preinstalled. It has CSC stuff for all carriers added. Its debloated slightly with knox removed. Some stuff may not work but im not sure as I cannot test but this stuff may include fingerprint and or face recognition. If stuff doesnt work it probably related to using pie modems and non-hlos on a nougat rom which you have no choice.​
Downloads
system_s8plus_brb1.7z
BL_G955_NOUGAT_V7.tar.7z
Includes Fingerprint and Face Unlock fix for above nougat rom. Just flash in BL slot in odin after everything else
Magisk_System-v20.4.zip This is system magisk not the normal systemless magisk so magisk hide and modules will not work!
SuperSU_System.zip
Safestrap-4.12-T01-DREAMQLTE_PIE.zip Will boot straight to safestrap only for pie roms
Safestrap-4.12-T01-DREAMQLTE_NOUGAT.zip Will Give you the safestrap splash screen on boot
Directions
Safestrap Method
1. Extract system.img from the system_s8plus_brb1.7z and copy to phone also copy either SuperSu_System.zip or Magisk_System-v20.4.zip reboot to safestarp and flash system image
2. Flash either SuperSu_System.zip or Magisk_System-v20.4.zip
3. Reboot to download and flash BL_G955_NOUGAT_V7.tar.md5 in odin
4. If you get constant rebooting to safestrap flash Nougat safestrap zip while in safestrap
Non Rooted Pie Rom With Safestrap Can Be Found Here
Click to expand...
Click to collapse
unfortunately i got myself a bricked device. no bootloader, no recovery, no charge, nothing...
kkins95 said:
unfortunately i got myself a bricked device. no bootloader, no recovery, no charge, nothing...
Click to expand...
Click to collapse
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
jrkruse said:
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
nope. no sign of life comming from the phone. just a flicker of white line when i hold volume down and power button. thanks for the response.
kkins95 said:
nope. no sign of life comming from the phone. just a flicker of white line when i hold volume down and power button. thanks for the response.
Click to expand...
Click to collapse
So what exactly happened?
Sent from my iPad using Tapatalk
jrkruse said:
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
jrkruse said:
So what exactly happened?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
i was on a g995u1 firwmare(bootloader v7) although i was having issues with "no signal". i thought maybe if i follow your guide to return the rom back to nougat my network would return to normal.
i only flashed this file "BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V7.tar.md5".
ps. i did tick the "nand erase" in odin.
the flash completed but my phone went black and did not reboot again.. i disconnected hoping to get it back to download mode again but nothing was working. i have tried using volume down and power keys but this only causes the a little part of the screen to flicker for less than a second.
my battery was 99%. I dont have qualcomm drivers installed. i am installing one as we speak, i have seen some threads with similar issues like mine but no solutions.. thanks for your response..:crying::crying::crying:
kkins95 said:
i was on a g995u1 firwmare(bootloader v7) although i was having issues with "no signal". i thought maybe if i follow your guide to return the rom back to nougat my network would return to normal.
i only flashed this file "BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V7.tar.md5".
ps. i did tick the "nand erase" in odin.
the flash completed but my phone went black and did not reboot again.. i disconnected hoping to get it back to download mode again but nothing was working. i have tried using volume down and power keys but this only causes the a little part of the screen to flicker for less than a second.
my battery was 99%. I dont have qualcomm drivers installed. i am installing one as we speak, i have seen some threads with similar issues like mine but no solutions.. thanks for your response..:crying::crying::crying:
Click to expand...
Click to collapse
It happens once in awhile for no reason. Nand erase may have had something too do with it. I never use nand erase except if going back too totally stock from a modified system. I responded too your pm. You’re phone can probably be fixed with edl files but you are going too have too take your phone apart and jump some test points to make phone enter edl mode
Sent from my iPhone using Tapatalk
jrkruse said:
It happens once in awhile for no reason. Nand erase may have had something too do with it. I never use nand erase except if going back too totally stock from a modified system. I responded too your pm. You’re phone can probably be fixed with edl files but you are going too have too take your phone apart and jump some test points to make phone enter edl mode
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
ive been searching for the edl points for the s955u but to no avail. ive taken apart my phone but cant find any reference online for the edl test points. i dont want to start testing randomly because something i have no idea about might happen..
kkins95 said:
ive been searching for the edl points for the s955u but to no avail. ive taken apart my phone but cant find any reference online for the edl test points. i dont want to start testing randomly because something i have no idea about might happen..
Click to expand...
Click to collapse
I use to have pics and stuff but I lost them on a hard drive that failed. I can tell you they are on the bottom side of the board and you have to pry back a metal heat shield to get too them
Sent from my iPhone using Tapatalk
jrkruse said:
I use to have pics and stuff but I lost them on a hard drive that failed. I can tell you they are on the bottom side of the board and you have to pry back a metal heat shield to get too them
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
kindly help identify them if visible or point out what i am to do next. thanks alot....
kkins95 said:
kindly help identify them if visible or point out what i am to do next. thanks alot....
Click to expand...
Click to collapse
You have to take board out and flip it over. The points are on the bottom side
Sent from my iPad using Tapatalk
jrkruse said:
You have to take board out and flip it over. The points are on the bottom side
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
OK, Thanks for the response. i see two large heat sinks with the larger one at the top and the smaller at the bottom. i assume the points would be hidden underneath the bottom sink. now i have to figure out a way to pry those metals off... so much work..lol..
Will this work on all V7 Bootloaders?
I am currently on DTF4 and noticed your on the Verizon page you posted for the DTB3 Bootloader. Thanks for your time and efforts.
jrkruse said:
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Click to expand...
Click to collapse
jrkruse said:
Rooted Nougat Rom​
Click to expand...
Click to collapse
Thanks this worked for me! Is there a guide on how to reverse everything if I wanted to make the phone normal again? Like it would be factory out of the box?
lonewolf1738 said:
Thanks this worked for me! Is there a guide on how to reverse everything if I wanted to make the phone normal again? Like it would be factory out of the box?
Click to expand...
Click to collapse
Just flash stock firmware in odin
Sent from my iPhone using Tapatalk
I have version 8 files so will make stuff when I get a chance
Sent from my iPhone using Tapatalk
@NateNMad
yeah its on the same bootloader G955USQU7DTF4
[ROOT] [Extreme Syndicate] [Snapdragon][G955U/U1][V7 Bootloaders]
If anyone is thinking on updating phones now is the time. The method of unlocking bootloaders on US variants works one s10/s20 and n10/n20 phones. Read the whole article too get info and yes it works I have a bootloader unlocked sm-g975u s10+ with twrp and magisk installed.
https://www.xda-developers.com/samsung-galaxy-note-20-ultra-root-us-unlocked-snapdragon-865/
Sent from my iPhone using Tapatalk

Categories

Resources