I fallowed the rooting procedure from https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
But unfortunately ended up with the same no network problem no matter what I tried. Please help me with this problem.
Note: I tried backing up (after flashing twrp recovery) and restoring (after installing Magisk) esf. But it still won't work.
Follow this
https://forum.xda-developers.com/an.../test-disable-defex-security-samsung-t3851487
MarkTejo said:
Follow this
https://forum.xda-developers.com/an.../test-disable-defex-security-samsung-t3851487
Click to expand...
Click to collapse
It worked. I had to basically use Magisk 17.3 in order to bypass this issue. Thanks for the link.
The problem is with the supersu and magisk , Installing it cause unknown Baseband ! better use Magisk 17.3 Version to root J7 prime on 8.1
My phone J7 PRIME SM-G610F/DS lost network after flash of stock Oreo and root with Magisk v17.1.
It has no IMEI numbers, no network, baseband version Unknown, noSD card access. When dial *#06# it shows only S/N number which is not the one written on the back of the phone. I have been flashing all kind of stock roms but nothing bring back the IMEI.
Any help Please!!!
Try flashing magisk uninstaller. You need magisk 17.3 for oreo anyway. If you are not flashing stock rom with odin you should do that to reset everything back to true stock.
kjslabber said:
Try flashing magisk uninstaller. You need magisk 17.3 for oreo anyway. If you are not flashing stock rom with odin you should do that to reset everything back to true stock.
Click to expand...
Click to collapse
I have try this - flash different stock roms with ODIN, install Magisk uninstaller in TWRP, then flash stock rom again. Nothing work. I try flash custom rom in TWRP same result. I try wipe data, format data all kind of combinations nothing work. After ODIN finish flash procedure phone exit download mode goes to blue screen with the android dude and says installing update, after finish that it reboots - shows the SAMSUNG start screen and than again the blue screen with the android dude but this time the dude is dead and has big exclamation sing on top of him and says Error! The phone try to install something but never go to 100 percents and after that it boots to stock recovery. In recovery say:
No Support SINGLE-SKU
-- delete_omcnw_code. . .
Supported API: 3
Works perfect Magisk 17.1 in Stock Oreo 8.1.0
JHAM2005 said:
Works perfect Magisk 17.1 in Stock Oreo 8.1.0
Click to expand...
Click to collapse
can u please explain your procedure and say your model?
i have sm-g611ff and i have no sim network and external sd card not recognizing issue.
bartonn1 said:
can u please explain your procedure and say your model?
i have sm-g611ff and i have no sim network and external sd card not recognizing issue.
Click to expand...
Click to collapse
My phone was successfully rooted with the Magisk 17.1, but no more network and SD card, no baseband version. I have been downloaded and flashed over 20 different stock roms via Odin - nothing can brings it back. It says Secure Download enable if this matter!
PUSTINQ said:
My phone was successfully rooted with the Magisk 17.1, but no more network and SD card, no baseband version. I have been downloaded and flashed over 20 different stock roms via Odin - nothing can brings it back. It says Secure Download enable if this matter!
Click to expand...
Click to collapse
you are saying that even with magisk 17.3 it didnt solve your problem?am i right? then whats those photos you attached.
bartonn1 said:
you are saying that even with magisk 17.3 it didnt solve your problem?am i right? then whats those photos you attached.
Click to expand...
Click to collapse
I have try with Magisk 17.3 the phone is rooted like with the 17.1 but no networkq no sd card, baseband version unknown. The photos are not mine.
PUSTINQ said:
I have try with Magisk 17.3 the phone is rooted like with the 17.1 but no networkq no sd card, baseband version unknown. The photos are not mine.
Click to expand...
Click to collapse
thx a lot mate:good:
PUSTINQ said:
My phone was successfully rooted with the Magisk 17.1, but no more network and SD card, no baseband version. I have been downloaded and flashed over 20 different stock roms via Odin - nothing can brings it back. It says Secure Download enable if this matter!
Click to expand...
Click to collapse
I think you've downloaded the wrong one. You must based your download on your build number of your phone. Just go to sammobile download the stock rom of your phone remember your bulid number. Unzip the downloaded file then place it to their designated place in odin
gengki said:
I think you've downloaded the wrong one. You must based your download on your build number of your phone. Just go to sammobile download the stock rom of your phone remember your bulid number. Unzip the downloaded file then place it to their designated place in odin
Click to expand...
Click to collapse
I don't know what is the original build number!!! That is why I have been download from SAMMOBILE random stock roms but no one fix it!
OK! I have manage to bring my phone back to life.
First I use this file:
https://forum.xda-developers.com/android/general/guide-restore-imei-fix-corrupted-efs-t3116217
after that the phone could not start properly it was saying:
E:failed to mount /efs (Invalid argument)
I fix that with this tread:
https://forum.xda-developers.com/ga...fs-invalid-t2858056/post77380206#post77380206
After that the phone start with the proper IMEI numbers when dial *#006# but no S/N. But works perfect. I am happy!!!
PUSTINQ said:
OK! I have manage to bring my phone back to life.
First I use this file:
https://forum.xda-developers.com/android/general/guide-restore-imei-fix-corrupted-efs-t3116217
after that the phone could not start properly it was saying:
E:failed to mount /efs (Invalid argument)
I fix that with this tread:
https://forum.xda-developers.com/ga...fs-invalid-t2858056/post77380206#post77380206
After that the phone start with the proper IMEI numbers when dial *#006# but no S/N. But works perfect. I am happy!!!
Click to expand...
Click to collapse
Hello.
I will try your method.
Could you tell me what version of android you had when you made it?
Thanks for your time.
garciarena said:
Hello.
I will try your method.
Could you tell me what version of android you had when you made it?
Thanks for your time.
Click to expand...
Click to collapse
Android 7.0
No network after rooting
Sm g611f was running android 7. I rooted and lost network. I flashed stock android 9 but nothing worked. I also tried rooting the android 9 and also 7 with the latest magisk but still no network. Both the imei's and baseband are there.
JHAM2005 said:
Works perfect Magisk 17.1 in Stock Oreo 8.1.0
Click to expand...
Click to collapse
Which rom is this?
Related
OK people i won't talk much, i by mistake in twrp went to wipe then advance wipe and selected everything in there (including system)( i got a 158 mb update to v10d software i did that but it kinda failed cuz it rebooted once and got to twrp and stayed on it forever all other reboots take me to twrp and nothing else and then i wiped everything after trying many times cuz i was mad ).
SO yeah now there's no os installed in it.
BTW i have l90 D410 the dual sim version v10c software rooted and unlocked bootloader with guides from XDA only.
To fix myself i tried downloading CM 11 and tried flashing the zip from twrp at first i got w7ds error telling my device is not w7, so i searched a bit and got something which said change updater script and edit "w7" to "w7ds" in the first few lines. So i did that and tried to flash again but then i got MD5 does not match
WHAT should i do?
ATM im just stuck on twrp with no os installed in my l90 or say i have a completely wiped l90 with twrp recovery and a sd card (8 gb) and when trying to reboot twrp says your device doesnt look rooted install supersu to root it (obviously swiping to install dont work), other twrp functions are working good.
HELP PLSsssss most appreciated.
regards,
[IND]sattu
sattu_96 said:
OK people i won't talk much, i by mistake in twrp went to wipe then advance wipe and selected everything in there (including system)( i got a 158 mb update to v10d software i did that but it kinda failed cuz it rebooted once and got to twrp and stayed on it forever all other reboots take me to twrp and nothing else and then i wiped everything after trying many times cuz i was mad ).
SO yeah now there's no os installed in it.
BTW i have l90 D410 the dual sim version v10c software rooted and unlocked bootloader with guides from XDA only.
To fix myself i tried downloading CM 11 and tried flashing the zip from twrp at first i got w7ds error telling my device is not w7, so i searched a bit and got something which said change updater script and edit "w7" to "w7ds" in the first few lines. So i did that and tried to flash again but then i got MD5 does not match
WHAT should i do?
ATM im just stuck on twrp with no os installed in my l90 or say i have a completely wiped l90 with twrp recovery and a sd card (8 gb) and when trying to reboot twrp says your device doesnt look rooted install supersu to root it (obviously swiping to install dont work), other twrp functions are working good.
HELP PLSsssss most appreciated.
regards,
[IND]sattu
Click to expand...
Click to collapse
Did you try installing stock rom with kdz files using guides to be found on L90 general (I think) section?
sattu_96 said:
To fix myself i tried downloading CM 11 and tried flashing the zip from twrp at first i got w7ds error telling my device is not w7, so i searched a bit and got something which said change updater script and edit "w7" to "w7ds" in the first few lines. So i did that and tried to flash again but then i got MD5 does not match
Click to expand...
Click to collapse
What thread did you get your recovery from, @Quarx CM11? There is an option in TWRP on the page that's displayed right after selecting files to install, "Zip file signature verification". Make sure it's unchecked. Unchecking that option should bypass the MD5 verification and allow the installation. Unfortunately, you may have to continue with editing the updater-script on new installs.
I'll speak with @shoxxy and @Quarx about creating recoveries for the dual sim devices so that we can prevent this error from happening anymore. This will mean that there will eventually be 2 different sets of recoveries available for the L90. One set for dual-sim devices, and one set for single sim devices. By recovery set, I mean all available recoveries, CWM, TWRP, and Philz-Touch.
The reason for TWRP not installing SuperSU to root the OS is because there is no OS to root.
wojtek267 said:
Did you try installing stock rom with kdz files using guides to be found on L90 general (I think) section?
Click to expand...
Click to collapse
umm bro how could i do that since it requires my l90 to be in different modes while doing that, but i can only boot uptill twrp and there's no os in there.(btw i have stock kdz downloaded on my pc)
shinobisoft said:
What thread did you get your recovery from, @Quarx CM11? There is an option in TWRP on the page that's displayed right after selecting files to install, "Zip file signature verification". Make sure it's unchecked. Unchecking that option should bypass the MD5 verification and allow the installation. Unfortunately, you may have to continue with editing the updater-script on new installs.
I'll speak with @shoxxy and @Quarx about creating recoveries for the dual sim devices so that we can prevent this error from happening anymore. This will mean that there will eventually be 2 different sets of recoveries available for the L90. One set for dual-sim devices, and one set for single sim devices. By recovery set, I mean all available recoveries, CWM, TWRP, and Philz-Touch.
The reason for TWRP not installing SuperSU to root the OS is because there is no OS to root.
Click to expand...
Click to collapse
i believe i got twrp from google (damn) , by md5 verification you mean that zip file verification should have a cross infront of it or not? well w/e it is i tried in both ways (having cross and not having one) but it checks for md5 both times, maybe because i dont have twrp from quarx thread.
Can i update my twrp to quarx's one? if so how pls tell, would be much helpfull.
EDIT : atm i have downloaded few files that might be needed to unbrick(stock kdz file, cm11 28/10 build, twrp image from quarx) on my pc
UPDATE
OK i got to install cm11 on my device and when i try to fix permissions is says a SELinux is present (good) but phone is still just booting in twrp only.....
HELPPPP
nooooooo some1 pls help im desperate.......
p.s. why doesnt twrp remember my settings, i set screen timeout to 15 sec, after every reboot i have to w8 full 60 sec to get its screen timeout to be able to use the touch screen.
EDIT: OK guys dont bother yourself now i got myself running cm11 on my phone and its unbricked now. Cheers and thanks for your time.
if any1 wants me to tell what happened to my device how it happened and how i fixed w/e i tried etc then pls tell i might write it down for some other people who might be stuck.
sattu_96 said:
OK i got to install cm11 on my device and when i try to fix permissions is says a SELinux is present (good) but phone is still just booting in twrp only.....
HELPPPP
nooooooo some1 pls help im desperate.......
p.s. why doesnt twrp remember my settings, i set screen timeout to 15 sec, after every reboot i have to w8 full 60 sec to get its screen timeout to be able to use the touch screen.
EDIT: OK guys dont bother yourself now i got myself running cm11 on my phone and its unbricked now. Cheers and thanks for your time.
if any1 wants me to tell what happened to my device how it happened and how i fixed w/e i tried etc then pls tell i might write it down for some other people who might be stuck.
Click to expand...
Click to collapse
you said that u updated ur device to 10d..
Thats d problem.....
If u updated ur phone without stock recovery..
It will struck at twrp..
If u try to flash roms..
but still u'll struck at twrp (It happens to me tooo)
After rebooting the phone is directly enter into recovery mode to flash new update ..
I don't know where the update file and script stored but until its updated its still struck at the same twrp..
if u remove cache/delvik cache/data/system..
But still its trying to update phone by entering into recovery mode.......
So,
Only one solution to this.
Flash kdz file using offline method.
Here's link to thread
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
but after flashing kdz 10C.
It'll automatically update to 10d (Don't panic at this)..
kprsnt said:
Only one solution to this.
Flash kdz file using offline method.
Here's link to thread
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
but after flashing kdz 10C.
It'll automatically update to 10d (Don't panic at this)..
Click to expand...
Click to collapse
the problem here is that my phone was not in usb debugging mode before brick and i spent 6-7 hrs figuring out how to get my device detected, but it never got detected in my pc.
BTW my prob for now is solved since my phone is running cm11 very well, its true that i lost some good functionality like knock on, qslide apps, quick window software, etc. but at least it has an os to boot into now.
help
sattu_96 said:
OK i got to install cm11 on my device and when i try to fix permissions is says a SELinux is present (good) but phone is still just booting in twrp only.....
HELPPPP
nooooooo some1 pls help im desperate.......
p.s. why doesnt twrp remember my settings, i set screen timeout to 15 sec, after every reboot i have to w8 full 60 sec to get its screen timeout to be able to use the touch screen.
EDIT: OK guys dont bother yourself now i got myself running cm11 on my phone and its unbricked now. Cheers and thanks for your time.
if any1 wants me to tell what happened to my device how it happened and how i fixed w/e i tried etc then pls tell i might write it down for some other people who might be stuck.
Click to expand...
Click to collapse
hey brother same problem here. after flashinf L-touch rom on my galaxy S duos (gt-s7562) i got stuck in boot screen, nothing is going after it.
then i tried installing flashable twrp recovery from cwm recovery, and then followed the procedure to install L-touch rom. but when i reboot my device it says " no os installed" and asks me to install superuser. ( i think my os and my root access are gone now).
please hepl me out brother.
thanks and regards,
dhaval
You need to download the firmware (around 900mb) not cm ROM (300mb)
Sent from my GT-I9192 using XDA Free mobile app
i have found out how to fix this what you need to do is first flash a rom zip file get your stock recovery image for your device and flash it via twrp select install than install image find your stock recovery image then flash it then it will boot to the previous rom you tried to install then you can reflash twrp and all good
i have rooted samsung galaxy tab s2 T815y , but now using stock recovery i m getting (dm verity verification failed) and update from external storage is disabled error and my tab is not working working normally on existing rom(officail mm rom)
dude.rlc said:
i have rooted samsung galaxy tab s2 T815y , but now using stock recovery i m getting (dm verity verification failed) and update from external storage is disabled error and my tab is not working working normally on existing rom(officail mm rom)
Click to expand...
Click to collapse
I think you need a custom recovery installed such as TWRP to disable dm-verity, but don't quote me on it.
wirelesskebab said:
I think you need a custom recovery installed such as TWRP to disable dm-verity, but don't quote me on it.
Click to expand...
Click to collapse
ya i know but i want to install official stock rom, but using twrp it is not possible and using stock recovery(dm verification failed)
dude.rlc said:
ya i know but i want to install official stock rom, but using twrp it is not possible and using stock recovery(dm verification failed)
Click to expand...
Click to collapse
I think your problem is that you're not on the stock rom and you're trying to use the stock recovery... dm_verity goes hand in hand with the official rom, you can see this if you go into download mode, you would see binary would say something like "samsung official" system status would say something like "original" or "official". You can find this in smart switch > more > emergency software recovery and initialization > device initialization.
Why is using TWRP not possible? Please elaborate, what rom are you running? I think 3rd party recovery is necessary to bypass this issue in all cases when using unofficial rom.
I would suggest initializing your device via smart switch, make sure to back up everything if you can as it will be lost, however, I think that it should resolve the issue entirely. Initialization if you can't boot into stock rom, you will need to enter download mode and in smart switch type the model number and then the serial number, it should initiate then.
You could try waiting for someone who knows their stuff, but initialization via smart switch (not just the image pulled from sammobile which leaves some files out) is probably the way to go, IMO. I'm just a novice, but I'm the only one that's replied, so hopefully some others can chime in and say if I'm giving you bad advice.
dude.rlc said:
ya i know but i want to install official stock rom, but using twrp it is not possible and using stock recovery(dm verification failed)
Click to expand...
Click to collapse
You will always fail dm-verity in stock recovery on a modified device.
It's pointless trying to OTA on a modified device. It will fail.
To update you need to flash the stock firmware with odin in DOWNLOAD mode not RECOVERY.
wirelesskebab said:
I think your problem is that you're not on the stock rom and you're trying to use the stock recovery... dm_verity goes hand in hand with the official rom, you can see this if you go into download mode, you would see binary would say something like "samsung official" system status would say something like "original" or "official". You can find this in smart switch > more > emergency software recovery and initialization > device initialization.
Why is using TWRP not possible? Please elaborate, what rom are you running? I think 3rd party recovery is necessary to bypass this issue in all cases when using unofficial rom.
I would suggest initializing your device via smart switch, make sure to back up everything if you can as it will be lost, however, I think that it should resolve the issue entirely. Initialization if you can't boot into stock rom, you will need to enter download mode and in smart switch type the model number and then the serial number, it should initiate then.
You could try waiting for someone who knows their stuff, but initialization via smart switch (not just the image pulled from sammobile which leaves some files out) is probably the way to go, IMO. I'm just a novice, but I'm the only one that's replied, so hopefully some others can chime in and say if I'm giving you bad advice.
Click to expand...
Click to collapse
thanks for ur reply but my main problem is my device is no longer sync with pc using usb(because i think its usb dock pcb is damaged) so i cant use odin thts why i m searching for a solution to install official rom without pc.
i have install official images of marshmallow using twrp but my device is automatically turning off , when i m not using it
dude.rlc said:
thanks for ur reply but my main problem is my device is no longer sync with pc using usb(because i think its usb dock pcb is damaged) so i cant use odin thts why i m searching for a solution to install official rom without pc.
i have install official images of marshmallow using twrp but my device is automatically turning off , when i m not using it
Click to expand...
Click to collapse
Then use flashfire to install the stock rom. It will install everything except the bootloader.
ashyx said:
Then use flashfire to install the stock rom. It will install everything except the bootloader.
Click to expand...
Click to collapse
but my tab is not rooted ,is there any way to root it without pc it is running on marshmallow(t815y)
dude.rlc said:
but my tab is not rooted ,is there any way to root it without pc it is running on marshmallow(t815y)
Click to expand...
Click to collapse
You don't need a PC. Just install supersu with twrp.
ashyx said:
You don't need a PC. Just install supersu with twrp.
Click to expand...
Click to collapse
i dont have twrp installed in my tab.
and i cant connect my tab to pc to install twrp
dude.rlc said:
i dont have twrp installed in my tab.
and i cant connect my tab to pc to install twrp
Click to expand...
Click to collapse
You said you had it installed below?
dude.rlc said:
i have install official images of marshmallow using twrp but my device is automatically turning off , when i m not using it
Click to expand...
Click to collapse
ashyx said:
You said you had it installed below?
Click to expand...
Click to collapse
yes but i was trying to install official firmware using stock recovery thats why i have changed it because my tab is not working properky
dude.rlc said:
yes but i was trying to install official firmware using stock recovery thats why i have changed it because my tab is not working properky
Click to expand...
Click to collapse
Then there's nothing you can do. You either need root, twrp or odin.
I have a similar problem, dm+verity verification failed in stock recovery but I have not rooted or installed any other firmware.
So my questions are
1. Has someone else installed it without my knowledge?
2. Has someone installed something through adb sideload without my knowledge?
3. Have i deleted something I shouldnt have?
4. When i go into stock recovery and before i choose what to such as "recovery logs" if i hold down the home/finger print button for about 2 secs the highlighted colour changes from blue to green, is this normal?
Thanks in advance
I just received a Galaxy S2 SM-T810 running Nougat. It appears to be in perfect condition. I have Odin 3.1.2. and TWRP twrp_3.1.0-1_sm-t810_13317.tar. I have been unable to get TWRP installed. I have made multiple attempts, and it keeps the stock recovery.
Can anyone tell me why this is failing? Odin says it was successful. Any help would be appreciated. :crying:
Thanks in advance.
Try it again without Odin. ADB..
C0BRA01 said:
I just received a Galaxy S2 SM-T810 running Nougat. It appears to be in perfect condition. I have Odin 3.1.2. and TWRP twrp_3.1.0-1_sm-t810_13317.tar. I have been unable to get TWRP installed. I have made multiple attempts, and it keeps the stock recovery.
Can anyone tell me why this is failing? Odin says it was successful. Any help would be appreciated. :crying:
Thanks in advance.
Click to expand...
Click to collapse
Do you have oem unlock switched on as well?
C0BRA01 said:
I just received a Galaxy S2 SM-T810 running Nougat. It appears to be in perfect condition. I have Odin 3.1.2. and TWRP twrp_3.1.0-1_sm-t810_13317.tar. I have been unable to get TWRP installed. I have made multiple attempts, and it keeps the stock recovery.
Can anyone tell me why this is failing? Odin says it was successful. Any help would be appreciated. :crying:
Thanks in advance.
Click to expand...
Click to collapse
A proper read of the instructions would solve it.
SonderTech said:
Do you have oem unlock switched on as well?
Click to expand...
Click to collapse
There was no option to do that. I looked thinking that might have been it,
Deleted.
C0BRA01 said:
Thank you. that's was quite useless.
I have flashed TWRP on quite a few devices.
I kept getting a weird screen instead of TWRP and I used ODIN 3.12.3 and TWRP 3.1.0-1 and then tried 3.1.1.1 that failed too. I finally ended up using ODIN 3.12.5 and TWRP 3.1.0-1 I also had flashed the tablet back to 6.01, and then back to 7.0. When I tried to use ODIN to reflash directly to 7.0 again it basically didn't do anything so I had to flash backward first. I think the partitions for my stock ROM were somehow messed up, and flashing back to 6.01 and then back up to 7.0 fixed it. Even with that, I had to use the older TWRP 3.1.0-1 I think that was the worst time I ever had getting a device rooted.
Click to expand...
Click to collapse
Google's new API might have something to do with that. I'm not sure. Did you end up getting a systemless root on the device with 6.0 and above
SonderTech said:
Google's new API might have something to do with that. I'm not sure. Did you end up getting a systemless root on the device with 6.0 and above
Click to expand...
Click to collapse
yes I installed Majisk.
C0BRA01 said:
yes I installed Majisk.
Click to expand...
Click to collapse
Oh ok
Hi,
I had a Note 9 SM-N960F (region XSG) that was ROOTED with Magisk and running Android 8 (Oreo).
I downloaded updated Android 10 firmware for my phone and region (via Samfirm). I placed BL, AP, CP, and HomeCSC files in correct positions. Ran ODIN. PASSED!
But it's bootlooped now.
I can get into "Downloading" and "Stock Recovery." What do I do???
Please help. I'm stuck.
pappaellio said:
Hi,
I had a Note 9 SM-N960F (region XSG) that was ROOTED with Magisk and running Android 8 (Oreo).
I downloaded updated Android 10 firmware for my phone and region (via Samfirm). I placed BL, AP, CP, and HomeCSC files in correct positions. Ran ODIN. PASSED!
But it's bootlooped now.
I can get into "Downloading" and "Stock Recovery." What do I do???
Please help. I'm stuck.
Click to expand...
Click to collapse
after flashing Do data factory reset and wipe cache from recovery and reboot
After reboot Wait 5 to 10 minutes .
Trex888 said:
after flashing Do data factory reset and wipe cache from recovery and reboot
After reboot Wait 5 to 10 minutes .
Click to expand...
Click to collapse
Thank you for your response!!!
Will all my information be deleted? I backed up my pictures/videos. But i forgot to backup my text messages.
pappaellio said:
Thank you for your response!!!
Will all my information be deleted? I backed up my pictures/videos. But i forgot to backup my text messages.
Click to expand...
Click to collapse
Yes all info will be deleted and you cannot backup anything on this boot loop stage.
But you have to do factory reset anyway otherwise your device won't boot.
Trex888 said:
Yes all info will be deleted and you cannot backup anything on this boot loop stage.
But you have to do factory reset anyway otherwise your device won't boot.
Click to expand...
Click to collapse
Is there any way of flashing another BL file to get the phone booted?
pappaellio said:
Is there any way of flashing another BL file to get the phone booted?
Click to expand...
Click to collapse
No unfortunately you will lose your data in order to make your device boot
pappaellio said:
Is there any way of flashing another BL file to get the phone booted?
Click to expand...
Click to collapse
Bootloader won't help
Have to flash full firmware then Must do factory reset as I said earlier
Trex888 said:
Bootloader won't help
Have to flash full firmware then Must do factory reset as I said earlier
Click to expand...
Click to collapse
After many, many, many bootloops with STOCK FIRMWARE (correct regional and model for my phone), I FINALLY figured it out.
1. First, I used ODIN to flash TWRP.
2. I went into TWRP and I did a full wipe. This deleted my phone completely. No operating system.
3. Next, I went to DrKetans website and downloaded the Android 10.1 firmware he created for the Note 9 (SMN960F). I put that file on a MicroSD card and placed it in my phone.
4. I entered TWRP on my phone and flashed the file on my MicroSD.
5. My phone FINALLY loaded. But I had no reception.
6. So I downloaded the modem file from his site and flashed it via ODIN. I did NOT flash the BL file because i didn't want to mess up the bootloader again.
7. Rebooted my phone with reception.
Hope this helps someone out there.
hi guys, a friend of mine gave e this samsung galaxy tab S2 SM-T715 32GB that is stuck on bootloop, he said nothing about what he has done to it (sadly) all i know is that it's stuck in bootloop and it's impossible to access the recovery... what i've tried so far is this:
- find a TWRP and flash it with odin v3.14, which works but when the tablet reboots it's stuck on bootloop and i can't access the recovery
- find and flash an older version of the TWRP that's for the android 5.1 stock rom, flashed in and worked, though i can't access it after the reboot
- find and flash the latest OFFICIAL rom which works because when i get into the download mode i see "samsung official" on "binary" and not "custom" as it was after the previous tries
if anyone has an idea about what i should do please help me ^^ the tab is still in good condition and would be a waste to throw in the garbage tbh
y0ur5h4d0w said:
hi guys, a friend of mine gave e this samsung galaxy tab S2 SM-T715 32GB that is stuck on bootloop, he said nothing about what he has done to it (sadly) all i know is that it's stuck in bootloop and it's impossible to access the recovery... what i've tried so far is this:
- find a TWRP and flash it with odin v3.14, which works but when the tablet reboots it's stuck on bootloop and i can't access the recovery
- find and flash an older version of the TWRP that's for the android 5.1 stock rom, flashed in and worked, though i can't access it after the reboot
- find and flash the latest OFFICIAL rom which works because when i get into the download mode i see "samsung official" on "binary" and not "custom" as it was after the previous tries
if anyone has an idea about what i should do please help me ^^ the tab is still in good condition and would be a waste to throw in the garbage tbh
Click to expand...
Click to collapse
Flashed multiple part stock ?
Fully working with stock or still bootlooping?
bmwdroid said:
Flashed multiple part stock ?
Fully working with stock or still bootlooping?
Click to expand...
Click to collapse
i flashed a single file stock rom in "AP" on odin, how can i get multiple files rom? the one i've flashed right now was downloaded from sammobile with the latest updated, android 7.0 included (see a screenshot of the file name attached)
y0ur5h4d0w said:
i flashed a single file stock rom in "AP" on odin, how can i get multiple files rom? the one i've flashed right now was downloaded from sammobile with the latest updated, android 7.0 included (see a screenshot of the file name attached)
Click to expand...
Click to collapse
with the application samfirm ,you check "Binary Nature" and you have multiple files rom .Do'nt forget to specify the Region .
aboulafia1901 said:
with the application samfirm ,you check "Binary Nature" and you have multiple files rom .Do'nt forget to specify the Region .
Click to expand...
Click to collapse
i've flashed the 4 files i downloaded with samfirm, though it still bootloops i guess it's RIP
y0ur5h4d0w said:
i've flashed the 4 files i downloaded with samfirm, though it still bootloops i guess it's RIP
Click to expand...
Click to collapse
Might be worth a try to flash several times one after another.
Sometimes I read it helps.
bmwdroid said:
Might be worth a try to flash several times one after another.
Sometimes I read it helps.
Click to expand...
Click to collapse
flashed back to back 4 times, nothing changed sadly
Try perhaps with Frija in place of samfirm and perhaps with heimdall (under Linux but also windows I think) in place of Odin.
y0ur5h4d0w said:
hi guys, a friend of mine gave e this samsung galaxy tab S2 SM-T715 32GB that is stuck on bootloop, he said nothing about what he has done to it (sadly) all i know is that it's stuck in bootloop and it's impossible to access the recovery... what i've tried so far is this:
- find a TWRP and flash it with odin v3.14, which works but when the tablet reboots it's stuck on bootloop and i can't access the recovery
- find and flash an older version of the TWRP that's for the android 5.1 stock rom, flashed in and worked, though i can't access it after the reboot
- find and flash the latest OFFICIAL rom which works because when i get into the download mode i see "samsung official" on "binary" and not "custom" as it was after the previous tries
if anyone has an idea about what i should do please help me ^^ the tab is still in good condition and would be a waste to throw in the garbage tbh
Click to expand...
Click to collapse
did you fix yours?
I have the same model and finally fixed(its been > 3hrs so far) mine by formatting ALL partitions in TWRP, then installing 5.0.2.
Ri9000 said:
did you fix yours?
I have the same model and finally fixed(its been > 3hrs so far) mine by formatting ALL partitions in TWRP, then installing 5.0.2.
Click to expand...
Click to collapse
i still haven't but i might try when i have some free time! thanks for the advice would be awsome to actually fix it honestly
y0ur5h4d0w said:
i still haven't but i might try when i have some free time! thanks for the advice would be awsome to actually fix it honestly
Click to expand...
Click to collapse
mine is still up >30 hrs so looking promising. I've been working on it for 8 months or more. Thinking back, looking at the flash in "edl mode" guide . . .
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
This is a generic guide that could be suitable for many Qualcomm based devices, once the phone can be triggered to EDL mode. To make sure this guide will work as expect, following requirements are needed: - Know how to trigger the phone to EDL...
forum.xda-developers.com
. . maybe this is how I should have done it, but mine was stable in download mode.
In the end this is what I did ymmv.
flash back to 5.0.2stock with heimdall,
flashing twrp3.1.0-1, format internal partitions,
reflash 5.0.2stock, & twrp3.1.0-1.
edit: after 1 day it is rebooting again. groan.