Related
This method creates the ability to debloat the Verizon GS7 (non-Edge Snapdragon) by modifying @jrkruse's method for the S7 edge posted here. Huge thanks to jrkruse for making the GS7 what it should be without massive bloat.
After my OP, he and @CVertigo1 evolved the method to fix the safetynet fail issues, so it now should work perfectly. I personally have not yet tried the updated method but will do so tomorrow. I'm copying instructions from the CVertigo1 thread here, but also keeping the old instructions below in post 1.
Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay.
New CVertigo1 method:
CVertigo1 said:
Yet again, all thanks go to @jrkruse for this one. I have modified his zip to work on the Verizon S7 flat. The ROM is silky smooth since it uses the factory kernel. I'm going to tweak his instructions to work for the flat. I can confirm that SafetyNet passes using this method.
Download
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
S7_SU_2_79_Root_Unroot_WO_Tweaks.zip
VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip
Install Instructions From Any Build
Warning: This will wipe your device. Some of these instructions are redundant, but they will ensure that everything goes as planned. If you don't follow them to the T, don't complain.
1) Unzip Odin and the firmware bundle zips. Boot the phone into download mode and flash the G930T BL, AP, and CP files in Odin.
2) Don't bother logging into any accounts, as the phone will get wiped again. Copy the FlashFire.apk and VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip to your SD card.
3) Shut off the phone and boot into download mode (volume down, home, and power). Flash the S7 Nougat root kernel in the AP slot in Odin. This file was in the firmware bundle.
4) When the phone reboots, unlock developer options and enable USB debugging. Unzip the S7_SU_2_79_Root_Unroot_WO_Tweaks.zip and run root.bat from your PC.
5) Now install FlashFire. Go into FlashFire settings and click option to allow flashing Bootloaders.
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
7) Now click install zip and choose VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip Make sure to click mount system when FlashFire asks. View attachment 4073928
VERY IMPORTANT NOTE: MAKE SURE TO UNCHECK INJECT ROOT AFTER ADDING THE ZIP!!!!!!!- Thanks @dclutter1
8) The phone will restart and FlashFire will flash the firmware first(it will take a couple minutes to find and flash everything), then the Aroma installer will start.
9) In Aroma, select wipe data(DO NOT KEEP SU)
10) The phone will say custom status on first boot, but it goes away after setup and reboot.
Click to expand...
Click to collapse
older method just for the record
Here is an OLDER METHOD with ADB install
Download stuff:
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
ROM: There are two basic options to choose from:
PlayStore Rom - so called because it has almost NO apps and you download what you want from the PlayStore. Has an experience very similar to the Pixel.
Hybrid ROM - close to Samsung Stock experience by massively debloated
Method:
Reboot phone to recovery wipe data
Reboot to bootloader
In odin flash:
In BL slot: BL_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT.tar.md5
In AP slot: AP_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5
In CP slot: CP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT.tar.md5
Leave CSC slot Blank
Go through setup don't add any accounts your going to wipe again when finished reboot back to bootloader
In odin Flash Engineering Boot.img from above (in AP slot)
When phone reboots and computer reconnects to phone Open HYBRID_PLAYSTORE_ROM.zip folder
Click Verizon_TMO_PlayStore_Install.bat
When done click press to continue the phone will reboot back to download mode
In odin flash:
In CSC slot: CSC_VZW_G930VVZW4BQA2_CL10280325_QB12417265_REV02_user_low_ship_MULTI_CERT.tar.md5
In AP slot: G930TUVU4BQB1_Boot_Recovery_Image.tar.md5.tar
Phone will reboot to recovery and fail
In Recovery click Mount System
Wipe data
Reboot phone
During Boot Phone will Say Custom Status this will change after phone is setup and a reboot is performed
Once through setup open Rom Control App
Navigate to Phone and Settings
Click on IMS Settings
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Click Back Button until your back to Phone and Settings Menu in Rom Control
Choose Activate Advanced Calling
Make sure under Advanced Calling that HD and Video calls are enabled
Activate WifiCalling
Known issues:
Safety net check fails (so Venmo does not work)
Some sites are blocked. Turning on "data saver" in Chrome settings worked for me but not everyone
I found that I had to go into settings > applications > phone and explicitly choose the phone as my default application for calls before it would correctly create a notification when the phone rang.
Some slightly more varsity moves:
Keeping apps from your stock:
You can modify the .bat file to not remove any apps you want to keep.
For example, I wanted to keep the "always on" display, so I deleted these lines from the .bat file:
Code:
adb shell rm -r /system/priv-app/AODService_v20
You can also further delete apps. Essentially during steps 5 - 7 above, the phone is rooted. During that time you can remove other packages. (My advice would be to pull them to your computer so you can push them back if needed)
For instance, I wanted to remove Hangouts, the AOSP browser (I use Chrome) and VisualVoiceMail. So I repeated step 5, then did:
Code:
adb root
adb remount
adb pull /system/app/VisualVoicemail
adb shell rm -r /system/app/VisualVoicemail
adb reboot bootloader
Then repeat steps 9 - 11
Wipe CACHE, (NOT data)
Reboot
Cool, cant wait to walk a friend thru this.
Just got up and running on PlayStore, everything seems good except I can't get the call recording to work. Thanks for putting this together
Sent from my SM-G935V using Tapatalk
JPSloan1 said:
...
7. Click Verizon_TMO_PlayStore_Install.bat.
...
Click to expand...
Click to collapse
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
thrillerbee said:
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
Click to expand...
Click to collapse
Yes It appears he updated his method to one that uses a different kind of temporary root as well as flashable files. I'll have to look at it and see if it's customizable the way the other one was, but it looks like you found the correct playstore ROM zip from before. Here is the other ROM. Sorry for the confusion.
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
t1231 said:
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
Click to expand...
Click to collapse
I tried but the .zip kept failing so maybe I didn't create it right.... So ultimately I did not bother and my service seems just fine at the moment.
Hobson318 said:
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
Click to expand...
Click to collapse
I think that would work (and wouldn't think you need to bother with the engineering bootloader steps either then) but to be honest it might be safer to ask jrkruse, because I don't deeply understand it - really just adapted his method for the S7 flat.
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
S3NTYN3L said:
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
Click to expand...
Click to collapse
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
JPSloan1 said:
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
Click to expand...
Click to collapse
Step 10.
Hmm, It seems that I wasn't holding the buttons down long enough.
If DL = Damn Long, then, yes, I agree.
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
S3NTYN3L said:
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
Click to expand...
Click to collapse
If ROM control didn't install manually it's because the .bat file didn't execute correctly. Did you modify it? Did it successfully acquire root and execute all the commands all the way through to the "click to continue" prompt? OR did it give error messages along the way? (There will be a few during the remove steps because it's removing packages that only exist on the S7 edge, not flat.
I would try it again if you have the patience.
I didn't modify anything.
I only recall a few minor errors regarding removal of non-existent directories.
Yes, the script went through to the end.
Yes, the phone had root and the TMobile rom wouldn't let me forget it, lol.
It kept complaining the whole way through.
JPSloan1 said:
Basically this method temporarily roots the phone to modify the packages installed, removes a ton of them, and then reverts. So with this method, Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay
Click to expand...
Click to collapse
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
CVertigo1 said:
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
Click to expand...
Click to collapse
Yeah attached. I think I also have this problem as do those in the other thread, and that's why I get an error on device check with Venmo.
I thought you posted that Samsung Pay worked for you in the OP.
CVertigo1 said:
I thought you posted that Samsung Pay worked for you in the OP.
Click to expand...
Click to collapse
I followed the method in the OP, installed Play Store version. Samsung Pay is working for me.
Sent from my SM-G935V using Tapatalk
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs
Hi everyone, this all started when I tried to flash a patched boot image for root and seemed to get worse from there. There's no data on the phone that I care about so just wiping it and getting it to boot would be preferable.
I've tried using the skipsoft toolkit (I have the ultimate version if that helps any) to try and get it to flash a freshly downloaded stock image, but for whatever reason after answering all the questions it extracts everything, does all the checks, then says "device is not set" and just jumps back to the main menu.
I've tried downloading the factory image right and running the flash-all script, it goes through the entire process which looks promising, but then just reboots the phone, I get the nice "your device is corrupt" message, press the power button to continue, but then it just hangs at the white "Google" splash screen with the little unlocked icon at the bottom, and doesn't move past that.
I know the version that I had on here prior to the problems was 8.0.0 (OPD1.170816.010, Sep 2017), so that's the one I've been trying to work with.
Not really sure where to go next, hoping someone has some advice for me.
Thanks everyone.
how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again
Never use a toolkit, they can hide error messages and displays that can help diagnose some issues. Always try the step by step methods to rescue provided by the excellent guides available here.
uicnren said:
how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again
Click to expand...
Click to collapse
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..
krash2k said:
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..
Click to expand...
Click to collapse
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.
uicnren said:
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.
Click to expand...
Click to collapse
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.
krash2k said:
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.
Click to expand...
Click to collapse
:good:
uicnren said:
:good:
Click to expand...
Click to collapse
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)
krash2k said:
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)
Click to expand...
Click to collapse
honestly, Im not sure. But I also didnt think it would make a difference when flashing the stock images back, but it does. I guess anything is possible.
Yep.. it definitely did. I guess this is a lesson for knuckleheads like me who start messing around before properly updating everything.
I just did all of the same things I did earlier, and it booted fine, with root. Lots of wasted hours over a dummy move.
Thanks again for all the help!
I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?
State.of.mind said:
I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?
Click to expand...
Click to collapse
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:
Badger50 said:
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:
Click to expand...
Click to collapse
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command
State.of.mind said:
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command
Click to expand...
Click to collapse
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
On second thought I think that it didn't work because I didn't have the factory image unzipped inside of the platform tools folder? The good news is that I'm up and running
v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?
nickmilla15 said:
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?
Click to expand...
Click to collapse
Go back to the basics. Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december). Add that folder to your path statement/environment. Download the FULL image (not OTA). Open that zip file and extract into the same ADB/fastboot folder. Do not unzip the included, nested zip file! Open flash-all.bat and remove the -w switch and SAVE. Boot your phone to the bootloader, and then run the script either way (clicking or fastboot window). There are SO MANY better guides/tutorials out there to follow step-by-step. Maybe read/post in those if you have any further issues. Best of luck.
v12xke said:
Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december).
Click to expand...
Click to collapse
This was my mistake when I was having all of those problems. I was using older versions of adb/fastboot. Everything looked like it was installing alright but then it would just keep bootlooping.. was very frustrating. It was a relief when replacing those binaries with the updated ones worked flawlessly.
if you have managed to get it work then have fun otherwise just use deuces script as per the instructions provided in op.
This is NOT my work (Ianmacd) and guide is written by Mr Pickles all credits to him for his install method.
Also this is just a copy and paste but the guide is well written and TWRP should cause less issues.
I'm sure Gieti94 is just perhaps busy with other commitments, credit also to him for his fantastic efforts.
Just a new space for the currently working TWRP so all don't get in a pickle.
----------------------------
Download Maintained By Pickles (best all in one convenient place) will have everything necessary for twrp functionality. Credit to pickles.....:good:
http://bit.ly/2VlcqYd
Excellent installation Guide below
Install Guide
---------------------------
- NOT A SINGLE STEP IS UNNESSECARY
- DO THEM _ALL_ EXACTLY!
- ALL YOUR DATA WILL BE GONE - BACKUP!
---------------------------------------
DO NOT INSTALL MODPACK FROM SOLDIER - IT BREAKS TWRP!
---------------------------------------
If you have any problems - contact @PiCkLeS or on Telegram by PiCkLeS or @rp4k
---------------------------------------
All development is by @ianmacd (Ian Macdonald).
---------------------------------------
0 - No matter what you have today, no root or Magisk-only solution or TWRP with Magisk-solution, do ALL the steps..
1 - Make sure you copy the "Magisk_Manager_Ian_install.apk" file and "Multidisabler-g97x_by_Ian.zip" file to your sd-card before you start!
2 - Download latest firmware via Samfirm or Frija or in any way you can, and unpack.
3 - Boot your phone to Download mode (Power+Bixby+VolDown) and remember to have the USB connected to your computer, it won't boot to DL-mode otherwise
4 - Keep autoboot etc in Odin settings, put each file in its place (AP, BL, CSC etc) and _dont_ use HOME_CSC, use CSC-only-file.
5 - After Odin is done, your phone will reboot automatically - let it! It can feel like forever, but let it do its restarts and stuff until you are in system-setup
6 - Do the setup as per usual, CONNECT TO WIFI but you can safely just say Skip on sign in and other stuff
7 - When setup says its all finished and you get to the standard launcher - go into Settings and enable Developer settings
8 - This step IS necessary.. If you don't do this step, you might get in pre-normal rrm state and you will have wait 7 days to try again: Enter Developer settings and look for the "OEM Unlock" switch - if you are rooting for the first time, Enable it. If you already have root since before or unlocked your bootloiader before, just confirm that its Enabled and graded out.
9 - If you already have an unlocked bootloader, skip to step 12. If not, continue with step 10.
10 - IF you never have unlocked your bootloader before, Power off the phone and boot into download mode again. You will see the long press volUp option for unlock bl, do that.
11 - IF you never have unlocked OEM before, boot the phone again, do the setup without signing in etc but connect to wifi, enable dev settings, go into dev settings and check that OEM now is enabled and grayed out.
12 - Reboot the phone in recovery mode (Power+Bixby+VolUp and keep holding until you are in stock recovery. Choose and do a factory reset.
13 - Reboot to bootloader with option in Recovery.
14 - Flash the tar you got (S10x-TWRP+Magisk_fixed_by_Ian.tar I Odin in the AP-slot. DISABLE auto reboot in Odin first!
15 - When the tar has flashed - Do as instructed on the phone, hold Power+VolDown for a few seconds and AS SOON AS THE SCREEN GOES BLACK -> quickly press power+bixby+volUp for a _long_ time, and I mean it can feel as if its a full minute! After a while you will see TWRP starting with its start screen, you can now let go and enter TWRP.
16 - FORMAT data, then WIPE data AND Cache. DO NOT LET IT REBOOT
17 - Flash "Multidisabler-g97x_by_Ian.zip" from SD card
18 - Go back to start screen of TWRP, Choose Reboot, Choose Recovery - YOU MUST ALWAYS CHOOSE REBOOT TO RECOVERY and _NOT_ system!
19 - Let the phone reboot into system, it will do some reboots it self, and again it will feel like it takes FOREVER - Just let it do its thing and DO NOT PRESS ANY KEYS!
20 - When your phone is finally done booting, just do the normal setup/signing for real this time.
21 - When you are done and in system/launcher, install "Magisk_Manager_Ian_install.apk" from SD card and verify that you now have Magisk Manager installed.
22 - Start Magisk Manager and say YES to what it says, it will do some stuff and then say "Rebooting in 5 seconds" - LET IT BOOT AND DO NOT TOUCH ANY KEYS this time either..
23 - Now when booted to system, start Magisk Manager and see that you have all green and its installed.
24 - Now you have root.
** Every time you reboot manually, be prepared to hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and let it reboot, you will have root.
** Every time you power off the phone, when you power ON again, hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and it will boot with root.
** Every time you want to enter TWRP-recovery, do as above but KEEP HOLDING THE KEYS UNTIL TWRP-start screen shows then release. Remember to choose reboot to recovery afterwards and you will boot with root.
** IF you screw up and forget or miss the key combo, just let it boot to system, immediately when system is up - reboot again and do the key combo and all is fine again.
This is me just trying to get an emergency first aid space, nothing more, I'm NOT trying to take any credits or dismiss Gieti94.
Thanks All
Duncan1982 said:
This is NOT my work (Ianmacd) and guide is written by rp4k all credits to him for his install method.
Click to expand...
Click to collapse
This is my tutorial and not r4pk. And I'd prefer that you use the download I provide here and no where else to make sure the right files gets downloaded when updated.
http://bit.ly/2VlcqYd
/P
Yea I can keep the OP updated, this is just an emergency first aid thread, thanks to Pickles for his well written guide.
I'm really not wanting to offend anyone, just for all to make life a bit easier....
very nice to have a reliable twrp solution, pitty that we don't have too many things to flash in recovery
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
And yes I never said I wrote the guide I just added myself for helping people
rp4k said:
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
Click to expand...
Click to collapse
I understand. But that doesn't seem to be a big problem for any one else and the bigger problem is that you risk having a link that is being used by the people only see it here and don't read anywhere else, or this message, and end up with old information or even worse, outdated files.
I can help you get the files on PM but please remove these links outside of my drive, which I maintain every day and keep up to date. It's not for vanity, it's for safety.
For now please edit your text and remove the link. All must use v1.1 of the multidisabler zip by Ian.
/P
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Duncan1982 said:
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Click to expand...
Click to collapse
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
PiCkLeS said:
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
Click to expand...
Click to collapse
I fully appreciate and understand that, the reason I created as I have plenty of time to maintain, and will keep it up to date I have been around for quite some time, if you look at my posts (search) I have had almost every device you can think of, currently have the Vivo IQOO also, I have enough experience to understand the important and implications.
I don't want your PM's to be going crazy so I'll fully respect your decisions and will keep everything updated also. But it is better if everything is tody and not one thing here and there, OP has been updated with your direct link, is this cool?
Just thought by creating this thread that it might help, my sincere and good intentions are hopefully evident
PiCkLeS said:
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
Click to expand...
Click to collapse
Can I install multi Disabler 1.1 withouth lost data?
zubi182 said:
Can I install multi Disabler 1.1 withouth lost data?
Click to expand...
Click to collapse
Yes just flash it in twrp, nothing will be lost.
/P
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
mistermidas said:
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
Click to expand...
Click to collapse
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
rp4k said:
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
Click to expand...
Click to collapse
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
mistermidas said:
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
Click to expand...
Click to collapse
Sorry I responded when I was half asleep. My fault.
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
mercifool said:
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
Click to expand...
Click to collapse
Yes, just do exactly all the steps and use the new files in the link and you will be fine.
//P
deleted
Carotix said:
hi ,
do you have the OEM switched to on?
if not , you need it ..... if you can't get it because you are waiting the 7 days , you can make this trick
open settings and set the date 8 days before ... then reboot
so you can enable OEM in developer settings
Click to expand...
Click to collapse
Hi there, are these instructions for Exynos only or can I apply it to Snapdragon as well, please advise. Thank!
Hi there,
I've combined some custom-kernel-like tweaks into a single flashable .tar file and I wanted to share it with you.
This .tar file contains:
-patched vbmeta image
-working magisk root with full Android 11 support
-magisk manager helper preinstalled
-a cleaned up boot screen + no bullsh*t on boot screen
-a cleaned up unlocked bootloader screen + no bullsh*t on unlocked bootloader screen
Prerequisites
-an unlocked bootloader
-firmware version CTL1 (A11)/BTJ3 (A10) or newer
-Odin 3.XX.X
-all data backed up
-fully functional brain
-stock recovery and firmware (this will not work if you have a custom recovery or run a custom rom)
STOCK BASED ROMS LIKE BEYONDROM WILL ALSO NOT WORK!
PLEASE NOTE:
-I am not responsible for a bricked device, please make backups and make sure to
always have the official firmware if something goes wrong
-flashing this requires you to factory reset your phone or else the phone won't boot
Instructions:
-unlock your phone's bootloader
-boot into download mode
-in Odin uncheck auto-reboot
-put the .tar file into the AP slot (If it doesn't work try USERDATA)
-after flashing boot into recovery with the key combination
-select factory reset and confirm (This will wipe everything from your phone)
-after factory reset reboot into system
-setup the phone and restore your backup (if you made one)
-Install Magisk and you're good!
If you have any problems
Please don't just comment "Doesn't work" and instead tell me about
the errors you encountered, your software info and other information
you think would be helpful.
Happy flashing!
If you still have questions make sure to ask them below
DOWNLOAD CTL1+: https://1drv.ms/u/s!AtNTTTF5vqOe73aVGDPSRGr5aria?e=dICFlS
DOWNLOAD BTJ3+: https://drive.google.com/file/d/1KqOGRbAy4fY1ghro4HoP-eDDYh4G7b5Z/view?usp=sharing
Tried it on my friend's phone,works great.Thanks
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
@[email protected] said:
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
Click to expand...
Click to collapse
This doesn't say anything. Can you tell me what custom ROM you are running? If you are on rooted stock also tell me.
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
@[email protected] said:
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
Click to expand...
Click to collapse
Geeeeeez! Update your phone! You have to have OneUI 2.5 BTJ3 or OneUI 3.0 CTL1 at least. What are you doing on 2.1? If you don't update, this will break your phone.
Okay buddy,ty..will do that.
Hi again m8,can i update Android 11,,One GUi 3.0,RP1A200720.012 G988B...
And ,or which file i have to use??
@[email protected] said:
And ,or which file i have to use??
Click to expand...
Click to collapse
Depends on the version. I don't want to be rude but how did you even manage to root your phone with this lack of knowledge?
If you update to Android 11/One UI 3.0 you chose the One UI 3.0 one. If you only update to 2.5 you chose 2.5. Remember to check the end of your firmware number:
There are supported firmware endings:
One UI 2.5:
-BTJ3
-BTJ4
One UI 3.0:
-CTL1
-CTL6
-Any One UI 3.0 firmware above that.
Download SM-G988B / Galaxy S20 Ultra 5G SM-G988B in Samfw - Samsung firmware download
Pick your CSC there, chose the newest one preferably (A11), press "Download on website", unzip it and flash it with Odin while in download mode. You should know how to do that.
After it's finished, complete setup (do not restore any backups yet!) and go into download mode again. Flash the file as AP or USERDATA (whatever works) and perform another factory reset. Done.
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
BCityModz said:
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
Click to expand...
Click to collapse
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
JanBoyGamer23 said:
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
Click to expand...
Click to collapse
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
JanBoyGamer23 said:
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
Click to expand...
Click to collapse
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
BCityModz said:
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
Click to expand...
Click to collapse
That can't be an issue with the script as it doesn't modify anything related to the camera
JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
Ok I may have to make a copy of my girls phone and flash original back to the phone and go again.
JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
yea IDK, did it all over again, even booting up to make sure the cam was working. same thing black screen when i open the camera app.
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
Short answer: Yes
Long answer: You are unlocking your bootloader and flashing a custom image so you lose your warranty and trip knox
frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
If you want to use s health: Download build.prop editor, grant it root access and and change the value of 'ro.config.tima' from 1 to 0