Database Info

Nvidia Shield- How Can I Avoid The Kill Switch?

I have my old Nvidia shield tablet and i have WiFi off and powered off.
I've been reading you can stop the kill switch from i guess changing the boot loader or operating system?
I new to this stuff.
Could someone just give me some directions on how to go threw this process please.
I don't know if it's to late cause i have the most recent update? but like i said it's turned off and WiFi is off and i heard that the kill switch is sent over the internet to your device and you don't have to confirm it.
So i hope my system is safe until i can do what ever you guys advise me to do.
Thank you...

treat your old tablet before connecting the new one to internet
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)

If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.

I used my new tablet and the both were working for the day, both have no problems so far.
I've been reading that they are sending out kill switches in 4 segments, by using the last 2 digits of the serial numbers system.
So mine hasn't gone threw yet i don't think.
So i need to root it?
Then delete the OTA file?
Then flash a custom firmware?
Thanks guys...

Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.

Jarocks said:
If your new tablet is never activated then in theory the killswitch should never be sent out. So as far as I can see flashing a custom rom on the new device before letting it boot into android or connect to the internet should prevent device from showing as having been activated.
Also blocking Nvidia's OTA servers on the network level (you'll need custom firmware on your router) should do the trick as well.
Block all of these:
Code:
23.32.163.186
e886.g.akamaiedge.net
ota.nvidia.com.edgekey.net
ota.nvidia.com
Also it might be worth looking into whether flashing nomoreOTA.zip on the new tablet works to the same effect.
Click to expand...
Click to collapse
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.

Snah001 said:
Just root it, do a full wipe=factory reset in TWRP and flash a custom Rom like Bliss and you will be OK.
Click to expand...
Click to collapse
I see lots of root programs, is there a best one?
Can you flash with TWRP?
And someone said all i have to do is...
"Full Process
1) Unlock Bootloader.
2) Flash TWRP Recovery.
3) Get the no more OTA.zip from XDA and flash it via TWRP
4) Check if the update option is removed from Settings, if not flash it again.
Done! "
Is that ok also?
Thank you...

You need to root to flash twrp?

EowynCarter said:
You need to root to flash twrp?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader to fastboot flash anything.

amartolos said:
No, but you do need an unlocked bootloader to fastboot flash anything.
Click to expand...
Click to collapse
Yeah, that the conclusion i reached.
Flash done, now runing bliss pop. First start got me loads of errors. I went until i realized i had forgotten to wipe. It's been a while since i last played with custom roms.

oliwek said:
Just for info, I found out today that, even if my new tablet was also flashed with nomoreOTA.zip, and even if I did it before there was any internet connexion from it, my old tablet is now flagged and an urgent OTA (in fact the kill switch) is waiting to be sent to it. Of course it still works, thanks to nomoreOTA.zip. But Nvidia did flag the old tablet after 10 days use of the new one (maybe they check serial numbers of tablets connected to grid or to another Nvidia server). Both my old and my new tablets are still working.
Click to expand...
Click to collapse
Well, that's disappointing

oleg77 said:
Hello. You have to delete a folder (/system/apps/TegraOTA if you are on last firmware, with OTA 3.1) but to do this, you need root as folders in /system are not visible for the normal (unrooted) user. Or you flash a custom firmware, and flash nomoreOTA.zip that you'll find in the same forum : http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489
Be sure to act before you use your new tablet, and ideally do the same to the new one before connecting it to internet. Then the kill switch maybe will not even be sent to you/your old tablet.
:fingers-crossed:
edit : do a search here for 'root shield tablet lollipop' if you need info to get root or flash custom recovery : http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
Note also that if you choose to (and succeed to) flash another (custom) ROM, such as Blisspop, you'll be safe as those custom roms avoid the kill switch (no /system/apps/TegraOTA folder in them)
Click to expand...
Click to collapse
Ok i followed the http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
I got to "On the tablet, select "recovery reboot"
But i didn't see it so i selected reboot, i rebooted and was on stock i think?
1) I can see that a few more steps and i'm rooted.
But i'm nervous to try this again from that point.
Should i just start at unlocking the boot loader?
2) Is rooting the device permanently unlocking the boot loader?
3) can i just no OTA from unlocking the boot loader part?

Ok i got to side loader and in the command it says error can't find device and there's an android guy on his back with a red statement mark.
So I'm in developer USB.
I have unlocked the boot loader
I'm flashing the recovery
And i get to restart in recovery.
Then i get the menus to side load the supersu.zip
I renamed it with out caps, i even made a folder in C:\Program Files\Minimal ADB and Fastboot.
Cause it installed at C:\Program Files (x86)\Minimal ADB and Fastboot.
just to avoid the (x86)
when i try and leave the menu to reset it asked me to root, but i had the error so don't want to brick it if rooting with an error on side loading supersu.zip
What do i do?
Thank you...

says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.

l337g0g0 said:
says
loading: 'supersu.zip'
error: device '(null)' not found
And no android guy on his back this time.
A hat with a refresh orange symbol.
Click to expand...
Click to collapse
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
You have unlocked bootloder and installed cwm recovery so yay! Download the SuperSU file on your tablet. Make sure you know where it downloaded to. Boot your tablet o to fastboot menu using the power/vol down. Select recovery mode using volume then power to select. Chose install zip then from sdcard (not the sdcard1) chose 0/ then search for where you put SuperSU and select it. Install. Then navigate to reboot. If asked to fix root pick yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have an SD card ATM. LOL
Why is the command with ADB not working?

l337g0g0 said:
I don't have an SD card ATM. LOL
Why is the command with ADB not working?
Click to expand...
Click to collapse
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.

frenziedfemale said:
You don't need a card the sdcard referee to is your internal memory on your tablet. Not sure why ADB isn't working but I had a similar issue with cwm once.
Click to expand...
Click to collapse
Ok that installed it.
WOW thank for that.
I guess I'm rooted, how do i test it and what does being rooted do for me?
Thank you....

Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk

frenziedfemale said:
Did you go back and flash the nomoreOTA zip? That is the most important part!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i just flashed nomoreOTA.zip.
It said the file was deleted and was a success.
I guess i can use the internet now?
I'm so nervous to turn the internet on and have the thing reset...
Did i need to run supersu to keep it rooted or always rooted until i use supersu to full unroot.
Thank you...

Cannot restore to stock using Mobile Upgrade Q.

Hi! I have a Idol 3 (6045I variant) and everytime I try to restore to stock using Mobile Upgrade Q it gets to the part where it says "Searching the server for latest available software" then the phone turns on normally and it says "Download update software package failed. Please check your internet connection." and it does this on two computers that I have tried with two different upgrade Q versions. Could someone please help me identify the problem?

It seems Alcatel abandoned our device.

It seems Alcatel abandoned our device.
Ha, ha...
Look the reason you are getting the message is because you restored your phone once on IP 240.4.4.xx.x.xx.xx. If you use another IP address you would not get that message. So, use a vpn or change you IP or use someone else's internet connection. It has happened to me more then once and was very frustrating as until I figured it out. Go to google and type in "What is my IP address" and start their.
HEY OFF TOPIC but can you believe that XPOSED is finally released for Nougat!!!!

vq8acsxht said:
It seems Alcatel abandoned our device.
Ha, ha...
Look the reason you are getting the message is because you restored your phone once on IP 240.4.4.xx.x.xx.xx. If you use another IP address you would not get that message. So, use a vpn or change you IP or use someone else's internet connection. It has happened to me more then once and was very frustrating as until I figured it out. Go to google and type in "What is my IP address" and start their.
HEY OFF TOPIC but can you believe that XPOSED is finally released for Nougat!!!!
Click to expand...
Click to collapse
This doesn't seem to be the case because even after using a different internet connections and a vpn it still throws out an error message and after updating to a newer version of upgrade q it says "There is no greater version available to upgrade your phone" which doesn't make any sense.

chewyboy0 said:
This doesn't seem to be the case because even after using a different internet connections and a vpn it still throws out an error message and after updating to a newer version of upgrade q it says "There is no greater version available to upgrade your phone" which doesn't make any sense.
Click to expand...
Click to collapse
Good, it says "There is no greater version available to upgrade your phone" now do a factory reset of the phone. If you did not destory the recovery partition you should be good to go.

chewyboy0 said:
Hi! I have a Idol 3 (6045I variant) and everytime I try to restore to stock using Mobile Upgrade Q it gets to the part where it says "Searching the server for latest available software" then the phone turns on normally and it says "Download update software package failed. Please check your internet connection." and it does this on two computers that I have tried with two different upgrade Q versions. Could someone please help me identify the problem?
Click to expand...
Click to collapse
Use this program here ...
https://mega.nz/#!9UdDGJLI!9S87X0wH0OEc3nKSd7dZHCES7RpDW8iWpPnPSqCPLzs (I'm trying to think of how this goes by memory so bare with me)
make sure you have the drivers installed. extract the file and the password is in the txt file. I can't remember the exact steps, but I think it will do some type of update or you go to "get version" if you don't see 6045 in the device list. once it's there you can go to the grey box besides get version that says update or download or something. my brain heh I can't remember, but then you click that and it will bring you back to stock. I did it on my 6045O flawlessly. It brought me right into the latest update. also if you go into the program files and go to the Sugar software folder after it's downloading the latest firmware for your phone and you go to the bin folder you should see a downloaded folder with your model number plus some other numbers and letters. copy that to your desktop. once that's done find the file starting with "R" that is the recovery image. delete that and replace it with twrp recovery image and just name it recovery. go back into the main Sugar folder in the program files and replace the folder with your model number with that folder. you also see a folder named download. that is the downloaded firmware you can delete that folder and just leave the modded folder with your model number containing the twrp recovery image. meanwhile, go through the setup process on your phone and skip all the steps you can and go into the phone. go to the about device and tap on the build number to unlock the developer options. make sure the OEM bootloader unlock is toggled and I just changed the usb debugging also although I don't think that's necessary. go back into the Sugar program and then go to just the update or whatever it is beside the get version and click that and it will update the phone with the latest firmware and it will put the custom recovery on it. make sure once it's done downloading you unplug it and turn it off then go into recovery mode by holding the power down and volume up until the main logo comes up then let go of power and keep holding volume up until twrp boots up. make sure you already have the latest SuperSU zip on your sdcard. go to the terminal or sometimes one comes up from the beginning and enter the systemless supersu line/code or whatever you call it and then hit enter or if it will go straight into twrp first do a factory reset in the advanced wipe tab then the systemless supersu terminal line code and then install the supersu zip. that's it. your back to the latest firmware and rooted. oh and btw, I forgot if you have to be in download mode when you are using the Sugar program. I play around in several phones so forgot at the moment. If you need to go into download mode just plug in the usb as your holding power, volume up and down at the same time and then when it goes into the download mode screen hold volume up for 5-10 seconds until the screen goes black. I hope it helps and sorry if any of this is confusing. It can be a bit advanced for some.

Mobile Q doesnt work here too.
With or Without VPN cant download the update package :/

irinae said:
Mobile Q doesnt work here too.
With or Without VPN cant download the update package :/
Click to expand...
Click to collapse
Press and hold the Volume up button, then briefly press the Power button. Keep pressing the Volume up button. Scroll to the desired language using the Volume down button, then press the Power button. Scroll to wipe data/factory reset by pressing the Volume down button.
Then try to do an update OTA.
If you are running stock and have for the last 6 months or so, their are not any new updates???
Just curious why you would think their is an update??
Also, "There is no greater version available to upgrade your phone" chewyboy0 admitted that Mobile Q software does work because Mobile Q software had to go out to the Alcatel servers to check which version he had.
Finally, Also, you gave no reference of whether you are running stock ROM, Rooted?? TWRP?? or for that matter whether you Samsung Galaxy phone can be plugged into the Mobile Q software. In other words, your coming up a little short on details.

I am running a custom ROM and I wanted to go back to stock for various reasons but I will try one of the methods above.

Brian9285 said:
Use this program here ...
https://mega.nz/#!9UdDGJLI!9S87X0wH0OEc3nKSd7dZHCES7RpDW8iWpPnPSqCPLzs (I'm trying to think of how this goes by memory so bare with me)
make sure you have the drivers installed. extract the file and the password is in the txt file. I can't remember the exact steps, but I think it will do some type of update or you go to "get version" if you don't see 6045 in the device list. once it's there you can go to the grey box besides get version that says update or download or something. my brain heh I can't remember, but then you click that and it will bring you back to stock. I did it on my 6045O flawlessly. It brought me right into the latest update. also if you go into the program files and go to the Sugar software folder after it's downloading the latest firmware for your phone and you go to the bin folder you should see a downloaded folder with your model number plus some other numbers and letters. copy that to your desktop. once that's done find the file starting with "R" that is the recovery image. delete that and replace it with twrp recovery image and just name it recovery. go back into the main Sugar folder in the program files and replace the folder with your model number with that folder. you also see a folder named download. that is the downloaded firmware you can delete that folder and just leave the modded folder with your model number containing the twrp recovery image. meanwhile, go through the setup process on your phone and skip all the steps you can and go into the phone. go to the about device and tap on the build number to unlock the developer options. make sure the OEM bootloader unlock is toggled and I just changed the usb debugging also although I don't think that's necessary. go back into the Sugar program and then go to just the update or whatever it is beside the get version and click that and it will update the phone with the latest firmware and it will put the custom recovery on it. make sure once it's done downloading you unplug it and turn it off then go into recovery mode by holding the power down and volume up until the main logo comes up then let go of power and keep holding volume up until twrp boots up. make sure you already have the latest SuperSU zip on your sdcard. go to the terminal or sometimes one comes up from the beginning and enter the systemless supersu line/code or whatever you call it and then hit enter or if it will go straight into twrp first do a factory reset in the advanced wipe tab then the systemless supersu terminal line code and then install the supersu zip. that's it. your back to the latest firmware and rooted. oh and btw, I forgot if you have to be in download mode when you are using the Sugar program. I play around in several phones so forgot at the moment. If you need to go into download mode just plug in the usb as your holding power, volume up and down at the same time and then when it goes into the download mode screen hold volume up for 5-10 seconds until the screen goes black. I hope it helps and sorry if any of this is confusing. It can be a bit advanced for some.
Click to expand...
Click to collapse
Hey I think this is working its currently downloading at 27% I will let u know the progress. Thanks so much!!

chewyboy0 said:
Hey I think this is working its currently downloading at 27% I will let u know the progress. Thanks so much!!
Click to expand...
Click to collapse
This one work but it was way simplier to restore to factory default via the Mobile Q like before.
Bah i don't care anymore my 5.5 battery does strange things so i get a Xiaomi Mi5 from work to replace it.

I am from india, using 6045k, lost duel sim support duo to flashing of marionette's Rom. Still trying to get duel sim back, tried eluga firmware also, but unfortunately i didn't get any error at 45%. Now i am using flyos 2.0, its working like charm. But only one sim is there, i tried several software upgrader versions, but server is not connecting, its always stuck at 20%.
Pls help me.

Siraj Enriq said:
I am from india, using 6045k, lost duel sim support duo to flashing of marionette's Rom. Still trying to get duel sim back, tried eluga firmware also, but unfortunately i didn't get any error at 45%. Now i am using flyos 2.0, its working like charm. But only one sim is there, i tried several software upgrader versions, but server is not connecting, its always stuck at 20%.
Pls help me.
Click to expand...
Click to collapse
Currently Alcatel has disabled the posibility of reflashing a stock ROM with Mobile Upgrade Q, so the only way is by flashing via TWRP or Sahara tool.
I have a 6045Y in latest stock MM (Build 22) and i'm incapable of performing a flash with Mobile Upgrade Q in order to clean my modified /system, the worst thing is that there is no flashable zip of this version which contain many critical fixes. I'm too very annoyed with this change of policy of Alcatel/TCL, they want me to buy a new smatphone but I'll not give them that pleasure, the Idol 3 5.5 is the best smartphone i've ever had in terms of hardware, it's a shame...

ciclolars said:
Currently Alcatel has disabled the posibility of reflashing a stock ROM with Mobile Upgrade Q, so the only way is by flashing via TWRP or Sahara tool.
I have a 6045Y in latest stock MM (Build 22) and i'm incapable of performing a flash with Mobile Upgrade Q in order to clean my modified /system, the worst thing is that there is no flashable zip of this version which contain many critical fixes. I'm too very annoyed with this change of policy of Alcatel/TCL, they want me to buy a new smatphone but I'll not give them that pleasure, the Idol 3 5.5 is the best smartphone i've ever had in terms of hardware, it's a shame...
Click to expand...
Click to collapse
Did u tried sugar mtk tool??

Siraj Enriq said:
Did u tried sugar mtk tool??
Click to expand...
Click to collapse
No, could you share the link? Thanks in advance.

ciclolars said:
No, could you share the link? Thanks in advance.
Click to expand...
Click to collapse
Thank god, today I got my phone to stock rom, by using q5.1.8.
Actually, yesterday only i heard about q.5.1.8, its been a year that i was trying to do this. Appart from q5.1.8, i connected VPN to U. S. Now everything is fine.
I dont know which one helped me, that the q5.1.8 or the VPN. :laugh:
Thanks to all.

Siraj Enriq said:
Thank god, today I got my phone to stock rom, by using q5.1.8.
Actually, yesterday only i heard about q.5.1.8, its been a year that i was trying to do this. Appart from q5.1.8, i connected VPN to U. S. Now everything is fine.
I dont know which one helped me, that the q5.1.8 or the VPN. [emoji23]
Thanks to all.
Click to expand...
Click to collapse
How exactly did you managed to do it? Is it possible to reflash the stock ROM?

ciclolars said:
How exactly did you managed to do it? Is it possible to reflash the stock ROM?
Click to expand...
Click to collapse
Actually, software upgrader can do the job. But the problem was slow server speed. Use q. 5.1.8, simply connect your in switch off condition, and try upgrading, if its not working, try VPN. I tried psyphon VPN connected to USA. In india serveris very slow.
6045k still running on lilopop, thats why people go going for stock roms.

Siraj Enriq said:
Actually, software upgrader can do the job. But the problem was slow server speed. Use q. 5.1.8, simply connect your in switch off condition, and try upgrading, if its not working, try VPN. I tried psyphon VPN connected to USA. In india serveris very slow.
6045k still running on lilopop, thats why people go going for stock roms.
Click to expand...
Click to collapse
In my case, Mobile Upgrade Q display a message that says I'm currently in the latest software version so it doesn't allow me to reflash stock ROM. My device is a 6045Y build 22 MM.

ciclolars said:
In my case, Mobile Upgrade Q display a message that says I'm currently in the latest software version so it doesn't allow me to reflash stock ROM. My device is a 6045Y build 22 MM.
Click to expand...
Click to collapse
Try Sugar Mtk tool
https://mega.nz/#!9UdDGJLI!9S87X0wH0...8iWpPnPSqCPLzs
Details is there on this thread.
I never tried it, try it. Read above msg by member Brian9285

I bricked my S7... can it be fixed?

So I modded the hell out of my stock rom and eventually broke it. After failing to flash the stock firmware about 50 times I gave up and put Lineage OS on my phone. Eventually I decided I wanted to try putting the stock back on and somehow screwed up my IMEI crap and don't have a backup. Basically all my phone can do is run stock rom but without any mobile network support or the same thing with Lineage OS. I've spent hours trying to fix it but nothing's worked. I checked just about every guide I've been able to find and none of them work. the issue is either not fixed or there's some kind of an error/change during the process that makes it so I can't continue. I downloaded some combination file that is supposed to help fix the issue but it won't flash via ODIN like the guide says so i can't do that.
I really need this phone up and working again. Anyone got any ideas? As of right now I have a paper weight that I can browse the internet on.
Update: I fixed it by flashing Android 8.0.0 firmware onto my phone instead of 7.0.0. I'm not sure why that fixed it because even lineage OS couldn't get my IMEI number but it's working now.

PimpWithALimp95 said:
So I modded the hell out of my stock rom and eventually broke it. After failing to flash the stock firmware about 50 times I gave up and put Lineage OS on my phone. Eventually I decided I wanted to try putting the stock back on and somehow screwed up my IMEI crap and don't have a backup. Basically all my phone can do is run stock rom but without any mobile network support or the same thing with Lineage OS. I've spent hours trying to fix it but nothing's worked. I checked just about every guide I've been able to find and none of them work. the issue is either not fixed or there's some kind of an error/change during the process that makes it so I can't continue. I downloaded some combination file that is supposed to help fix the issue but it won't flash via ODIN like the guide says so i can't do that.
I really need this phone up and working again. Anyone got any ideas? As of right now I have a paper weight that I can browse the internet on.
Update: I fixed it by flashing Android 8.0.0 firmware onto my phone instead of 7.0.0. I'm not sure why that fixed it because even lineage OS couldn't get my IMEI number but it's working now.
Click to expand...
Click to collapse
Quickest way to solve the issue as you've found out is to flash latest stock for device. Bootloader was the source of your problems, once upgraded it cannot be downgraded no matter what. All these bull sh1t guides saying you can just end up with a bricked phone.
Now BACK UP your EFS partition so this doesn't happen again.

cooltt said:
Quickest way to solve the issue as you've found out is to flash latest stock for device. Bootloader was the source of your problems, once upgraded it cannot be downgraded no matter what. All these bull sh1t guides saying you can just end up with a bricked phone.
Now BACK UP your EFS partition so this doesn't happen again.
Click to expand...
Click to collapse
I am planning on install a One UI Based rom on my S7, my phone is running stock without any rood or something like this.
How to flash the Rom without making a stupid thing that will brick my phone? i mean how to start all the process from zero?
And another thing i wonder about, what is the IMEI thing that you guys talked about?

rheh104 said:
I am planning on install a One UI Based rom on my S7, my phone is running stock without any rood or something like this.
How to flash the Rom without making a stupid thing that will brick my phone? i mean how to start all the process from zero?
And another thing i wonder about, what is the IMEI thing that you guys talked about?
Click to expand...
Click to collapse
1. Go here to download TWRP an install it via ODIN,
https://twrp.me/Devices/Samsung/
2. In TWRP select backup and choose only EFS and back it up to your external card (preferably also to your PC)
that will backup your IMEI etc

Huzaifa_Aziz said:
1. Go here to download TWRP an install it via ODIN,
https://twrp.me/Devices/Samsung/
2. In TWRP select backup and choose only EFS and back it up to your external card (preferably also to your PC)
that will backup your IMEI etc
Click to expand...
Click to collapse
EFS?

rheh104 said:
EFS?
Click to expand...
Click to collapse
Encrypted File System

rheh104 said:
EFS?
Click to expand...
Click to collapse
I think you need to go tutorial section first. And start from scratch. You won't be able to find the cotrects steps on dumb luck. Thank me later.

Huzaifa_Aziz said:
I think you need to go tutorial section first. And start from scratch. You won't be able to find the cotrects steps on dumb luck. Thank me later.
Click to expand...
Click to collapse
Send me a link to it please, thanks!

rheh104 said:
Send me a link to it please, thanks!
Click to expand...
Click to collapse
You have Exynos or Qualcomm variant?
I would suggest you start off from here
[LINK]https://forum.xda-developers.com/galaxy-s7/help/help-thread-question-noob-friendly-t3341138[/LINK]

rheh104 said:
Send me a link to it please, thanks!
Click to expand...
Click to collapse
I hope you have read about ODIN and FLASHING recovery by now,
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 go here and flash the TWRP RECOVERY and then install any custom ROM. or
Get original Firmware from Sammobile.com and Flash it via ODIN

H E L P

just uninstalled magisk from the app, and my phone is just restarting and not turnin on

plese tell us more;
what phone?
do you have a PC at hand?
have you used SP flash tool, the qualcomm equivalent or Odin?
are you familiar with firmware files?
the usual procedure for fixing this is flashing a working system image and wiping cache/dalivk/data or a complete firmware image instead

Qwerty_in_me said:
plese tell us more;
what phone?
do you have a PC at hand?
have you used SP flash tool, the qualcomm equivalent or Odin?
are you familiar with firmware files?
the usual procedure for fixing this is flashing a working system image and wiping cache/dalivk/data or a complete firmware image instead
Click to expand...
Click to collapse
i fixed it by re flashing magisk patched using odin

Qwerty_in_me said:
plese tell us more;
what phone?
do you have a PC at hand?
have you used SP flash tool, the qualcomm equivalent or Odin?
are you familiar with firmware files?
the usual procedure for fixing this is flashing a working system image and wiping cache/dalivk/data or a complete firmware image instead
Click to expand...
Click to collapse
but the wifi isnt working

if you're using a cellphone to type this, connect it to the computer vith a cable, go to Settings > WiFi and connections > Hotspot and Teathering > and turn on USB teathering
also, answer the questions, no info is useless info

Qwerty_in_me said:
if you're using a cellphone to type this, connect it to the computer vith a cable, go to Settings > WiFi and connections > Hotspot and Teathering > and turn on USB teathering
also, answer the questions, no info is useless info
Click to expand...
Click to collapse
the previous proplem is solved, thats y i didnt answer

Qwerty_in_me said:
if you're using a cellphone to type this, connect it to the computer vith a cable, go to Settings > WiFi and connections > Hotspot and Teathering > and turn on USB teathering
also, answer the questions, no info is useless info
Click to expand...
Click to collapse
and im using pc to write these msgs, the mobile's wifi thats not turning on

aight lad, send me a screenshot of settings > about phone
this sounds like the wifi drivers aren't where they should be
also; ANSWER THE FIRST QUESTIONS PLEASE!!!

Qwerty_in_me said:
aight lad, send me a screenshot of settings > about phone
this sounds like the wifi drivers aren't where they should be
also; ANSWER THE FIRST QUESTIONS PLEASE!!!
Click to expand...
Click to collapse
1 - the phone : Samsung m11
2 - yes I have PC at my hand
3 - I used odin
"The Screenshot" -

I think I was right about the drivers (magisk mounts the partitions differently sometimes breaking links) so just reflash the stock ROM, if you don't have that at hand look for it on Hovatek or other firmware providers (I think Samsung provides ROMs themselves)

i dont know how to refresh the rom( the rom is the AP file that i flashed it?) ,

Qwerty_in_me said:
I think I was right about the drivers (magisk mounts the partitions differently sometimes breaking links) so just reflash the stock ROM, if you don't have that at hand look for it on Hovatek or other firmware providers (I think Samsung provides ROMs themselves)
Click to expand...
Click to collapse
He may need 'to do a full Odin restore with data wipe' due to restoring images on Sammy... :
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86022423 PW

[RECOVERY] TWRP for Samsung Galaxy A41 [SM-A415F] [BINARY 1 & 2]

TWRP Recovery Project for the Samsung Galaxy A41 [Only for Android 11 Devices, will be upgraded soon.]
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the SM-A415F.​
I am not responsible for any bricked imei, when flashing TWRP backup the EFS & NVRAM partitions to be safe, do not root until having an actually good working backup, if you signal goes restore your backup, if you didn't have a previous backup I got a fix for you , flash your firmware as always but on the CP slot in Odin Flash Tool get the CP slot from a CUD4 firmware corresponding your CSC code.
Click to expand...
Click to collapse
A mantainer is required for this device, I just revived the project but someone with the device needs to mantain it.
Download - You'll always find the latest release in here: https://github.com/Galaxy-MT6768/android_device_samsung_a41xx/releases​Known Issues / Report Issues - https://github.com/Galaxy-MT6768/android_device_samsung_a31nsxx/issues​Telegram support group - http://t.me/a31nsxx​
How to install​
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
​Flashing Disabled vbmeta (To boot a modified system)​
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
​Sources​
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/Galaxy-MT6768/android_device_samsung_a41xx
Note: The device tree should be compatible with SHRP too
Click to expand...
Click to collapse
Special thanks to:​
TeamWin for the Recovery Project.
Akhil1999 for his kernel.
Zillion for re-doing Akhil's lost device tree.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.

I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?

Catoplepas said:
I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?
Click to expand...
Click to collapse
Yeah, just reflash stock firmware via Odin.
Also I should update this build, the latest isn't actually the latest.

Wait until v1.2.0 gets released

Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop

LolUnis said:
Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop
Click to expand...
Click to collapse
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis

Zillion said:
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis
Click to expand...
Click to collapse
Doesn't work the phone still goes into bootloop

LolUnis said:
Doesn't work the phone still goes into bootloop
Click to expand...
Click to collapse
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.

Zillion said:
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.
Click to expand...
Click to collapse
Where can I find the link of the Telegram group?

LolUnis said:
Where can I find the link of the Telegram group?
Click to expand...
Click to collapse
It's a public group

Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.

bestnugnification said:
Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.
Click to expand...
Click to collapse
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.

Zillion said:
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.
Click to expand...
Click to collapse
I guess I'll just repair the screen even if It's not actually worth it. Thanks though.

Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.

abcuky said:
Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.
Click to expand...
Click to collapse
The latest version works on both Android versions