Related
I'm having the the problem after try to flash (N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.ta r). Odin3 v3.12 stuck at initialization step as image attached. Also try with Odin3 v3.07 and Odin3 v3.10.6 with the same problem. Maybe because FRP lock in ON status or anything else? Need help ASAP
Screen info on Download Mode
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920L
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enable
KNOX WARRANTY VOID: 0 (0х0000)
RP SWREV: B:2 K:0 S:0
Try again after enabling 'OEM Unlock' in the Developer Options. By doing so FRP lock will be off.
And what exactly are you trying to do...?
Shiv Parmar said:
Try again after enabling 'OEM Unlock' in the Developer Options. By doing so FRP lock will be off.
And what exactly are you trying to do...?
Click to expand...
Click to collapse
Actually, this is phone come from stock official rom, which is received OTA update from samsung then try to download the updates but it's stuck during updating. Now this phone, can boot into download mode only.
I can't boot into system anymore and turn the on the OEM unlock function in developer mode.
Is there solution to resolve this. TIA
Im just guessing; since the OP doesn't flash a custom stuff like twrp recovery, OEM unlocking is not necessary. And the knox is hasn't tripped yet as i see. I would try another usb port, different version of odin(run as administrator) and be sure usb drivers are correctly installed on the PC. If all is OK; just try flashing the fw version which came installed on the device. If it success, enable oem unlock then try flashing latest fw and keep the OEM unlock enabled for future plans like rooting etc.
Mi MIX
7.5.4 Épic
Konsstantine34 said:
Im just guessing; since the OP doesn't flash a custom stuff like twrp recovery, OEM unlocking is not necessary. And the knox is hasn't tripped yet as i see. I would try another usb port, different version of odin(run as administrator) and be sure usb drivers are correctly installed on the PC. If all is OK; just try flashing the fw version which came installed on the device. If it success, enable oem unlock then try flashing latest fw and keep the OEM unlock enabled for future plans like rooting etc.
Mi MIX
7.5.4 Épic
Click to expand...
Click to collapse
FYI, I already try to flash with different Odin like v3.12, v3.07 and v3.10.6 but still same stuck at initialization step but I'm not flash the fw which is came at first because I dont know what the previous fw. The fw that I try to flash is original samsung fw from sammobile which is the latest ones (Nougat 7.0), actually this device is not mine, its my friend device that need my help to resolve it.
Maybe this device is from 5.0 and received OTA update for 6.0, maybe I should try to flash with 5.0 version first the try 6.0 later. Anyway thanks for advice @Konsstantine34
Do refer attachment, which version should I flash it?
antuketot76 said:
FYI, I already try to flash with different Odin like v3.12, v3.07 and v3.10.6 but still same stuck at initialization step but I'm not flash the fw which is came at first because I dont know what the previous fw. The fw that I try to flash is original samsung fw from sammobile which is the latest ones (Nougat 7.0), actually this device is not mine, its my friend device that need my help to resolve it.
Maybe this device is from 5.0 and received OTA update for 6.0, maybe I should try to flash with 5.0 version first the try 6.0 later. Anyway thanks for advice @Konsstantine34
Do refer attachment, which version should I flash it?
Click to expand...
Click to collapse
Upgrading from X to latest fw; shouldn't be a problem, downgrade could. In my opinion it's about the usb port/cable. Try different ones of them. Side note: If odin fails/freezes once; you have to reboot into download mode again to start a new session.
Also can you please post the screenshot of Options tab in Odin? Perhaps partition stuff or others are checked which supposed to be not.
Konsstantine34 said:
Upgrading from X to latest fw; shouldn't be a problem, downgrade could. In my opinion it's about the usb port/cable. Try different ones of them. Side note: If odin fails/freezes once; you have to reboot into download mode again to start a new session.
Also can you please post the screenshot of Options tab in Odin? Perhaps partition stuff or others are checked which supposed to be not.
Click to expand...
Click to collapse
See the screenshot attached for option tab, its stuck at initialization inside log
antuketot76 said:
See the screenshot attached for option tab, its stuck at initialization inside log
Click to expand...
Click to collapse
Well, i have no idea more than that. Perhaps another pc or Kies way(never used). What's the P7500 though?
Konsstantine34 said:
Well, i have no idea more than that. Perhaps another pc or Kies way(never used). What's the P7500 though?
Click to expand...
Click to collapse
opps, wrong photo. P7500 is for my galaxy tab 10.1... actually now Im flash a galaxy tab.
Its should be N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.tar.md5
Guys, really need your help on this problem, do you have any ideas on this.
Sorry for disturbing you guys, so sorry.
@CodeNameRedNeck
@LiL_Assassin
@Art Vanderlay
antuketot76 said:
Guys, really need your help on this problem, do you have any ideas on this.
Sorry for disturbing you guys, so sorry.
@CodeNameRedNeck
@LiL_Assassin
@Art Vanderlay
Click to expand...
Click to collapse
If Odin is seeing the phone in download mode my guess would be that your drivers are fine (I could be wrong) so I can't help but wonder why it sticks on initialization. I flash firmware on my device with FRP on all the time. I can only suggest using smart switch. When you connect your phone with smart switch running it will tell you that your device is not supported. It will still work. You will need the serial number and you must use capital letters and the dash in the model number.
CodeNameRedNeck said:
If Odin is seeing the phone in download mode my guess would be that your drivers are fine (I could be wrong) so I can't help but wonder why it sticks on initialization. I flash firmware on my device with FRP on all the time. I can only suggest using smart switch. When you connect your phone with smart switch running it will tell you that your device is not supported. It will still work. You will need the serial number and you must use capital letters and the dash in the model number.
Click to expand...
Click to collapse
Im try with Samsung Kies but not try yet with Smart Switch.
Maybe I can try it with Smart Switch, look if this successful.
Anyway thanks
Try to download latest stock firmware update N920CXXU3CQE1 from samupdate or Samsung mobile and install it via odin that should work .....
mala96 said:
Try to download latest stock firmware update N920CXXU3CQE1 from samupdate or Samsung mobile and install it via odin that should work .....
Click to expand...
Click to collapse
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
antuketot76 said:
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
Click to expand...
Click to collapse
But did you tried to download the latest version N920LKLU2DQE1 and install it .....
antuketot76 said:
As u mention above is fw for model N920C not same as model inside this thread.
Refer photo attached, my model is N920L korean version LG U+
Click to expand...
Click to collapse
If you have adb installed on your pc you don't even need odin.. Just go into recovery mode and select flash from adb then open a command prompt and (first make sure your firmware is in the SAME exact folder as adb is) then type adb sideload firmwarename.md5
Try that.
mala96 said:
But did you tried to download the latest version N920LKLU2DQE1 and install it .....
Click to expand...
Click to collapse
Yes, I already try flash both latest fw as below but failed.
7.0 version - N920LKLU2DQC7_N920LLUC2DQC7_N920LKLU2DQC4_HOME.tar.md5
GALAXY Note 5 SM-N920L 15.01.2017 6.0.1 Korea (LG Uplus) (LUC) N920LKLU2CPL5
--------------------------------------------------------------------------------------------------------------------
6.0.1 version - N920LKLU2CPL5_N920LLUC2CPL5_N920LKLU2CPL5_HOME.tar.md5
GALAXY Note 5 SM-N920L 15.01.2017 6.0.1 Korea (LG Uplus) (LUC) N920LKLU2CPL5
As I mention below that this device only can boot into Download Mode only, can't boot into system or recovery screen at all even use the combination button.
MrMike2182 said:
If you have adb installed on your pc you don't even need odin.. Just go into recovery mode and select flash from adb then open a command prompt and (first make sure your firmware is in the SAME exact folder as adb is) then type adb sideload firmwarename.md5
Try that.
Click to expand...
Click to collapse
Fyi, this device can boot into download mode ONLY even I try several times with button combination.
My pc already have ADB install on it. Is it using adb method gonna work in download mode or just in recovery mode only? I also dont know what fw is it in this device due to I can view download mode only.
antuketot76 said:
Fyi, this device can boot into download mode ONLY even I try several times with button combination.
My pc already have ADB install on it. Is it using adb method gonna work in download mode or just in recovery mode only?
Click to expand...
Click to collapse
Sorry adb sideload only works in recovery.. Try using my version of odin.. Sometimes odin will freeze and say Not Responding when it's first checking the MD5 file but if you leave it alone for 5 minutes I'll respond again.. Don't connect the phone until after odin finishes checking the md5 file..
My odin version is here you just need to unzip it..
odin-here
MrMike2182 said:
Sorry adb sideload only works in recovery.. Try using my version of odin.. Sometimes odin will freeze and say Not Responding when it's first checking the MD5 file but if you leave it alone for 5 minutes I'll respond again.. Don't connect the phone until after odin finishes checking the md5 file..
My odin version is here you just need to unzip it..
odin-here
Click to expand...
Click to collapse
Thanks for your advice, will try it now and will let u know after this...
IMPORTANT - READ THIS FIRST:
The Note FE comes with dm-verity check and forced encryption enabled. You will need to remove this extra layer of security for root access. To disable dm-verity and forced encryption you must install TWRP recovery first on your Note FE. Note that disabling forced encryption and dm-verity requires a factory reset from TWRP recovery, so you should backup your data (internal storage) before you begin.
The next stage then will be to root the device by flashing the SuperSU zip via TWRP recovery. SU will also ensure that dm-verity and forced encryption remains disabled. Bear in mind, however, that a factory reset will restore them again.
WHAT YOU WILL NEED:
Download Odin and drivers here: https://build.nethunter.com/samsung-tools/
Download TWRP for Note 7 Exynos: there are two versions: Korean and International:
Korean version: https://dl.twrp.me/graceltekor/
International: https://dl.twrp.me/gracelte/
Download the latest version of SuperSu here: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
You should also download the stock firmware appropriate to your version of Note FE, just in case. Variants S & L can be found on Sammobile, and variant K is available here: https://www.androidfilehost.com/?fid=817550096634784008
ROOTING YOUR NOTE FE:
Read these instructions through carefully before you begin.
(1) Install TWRP Recovery on your Note FE via Odin.
(2) Boot your Note FE into TWRP recovery as follows:
(a) First switch off your device.
(b) Now Press and hold “Home + Power + Volume Up” buttons for a few seconds and as soon as you see your device’s logo on-screen, release the three buttons altogether. Your device will boot into TWRP recovery.
(3) Upon booting into TWRP recovery for the first time, you’ll get a prompt to allow system modifications. You should swipe right to allow this.
(4) On the TWRP main menu, select WIPE then select “Format Data”. You will need to type yes in order to proceed. This will clean wipe the entire internal storage on your Note FE (make sure you have backed-up your important files safe to restore later).
(5) Still in TWRP recovery, you should now connect your Note FE to the PC. (TWRP supports MTP connection so you’ll be able transfer files to the device.) Wait until your Note FE appears on your PC desktop (may take a while first time). You can now transfer the SuperSU zip to your Note FE.
(6) Go back to the TWRP main menu and select “Install” this time. Now you can flash the SuperSU zip.
(7) Reboot your Note FE.
You should now be rooted. Test using an appropriate app.
It would be helpful to others if you reported your experience and the outcome here.
Good luck.
Thanks again for using your device to test this bro!
sent from my Note FE, S8 plus, S7 edge or S6
Thanks alot
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
malaccio said:
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
Click to expand...
Click to collapse
Yeap just did it.
having a problem booting into twrp after the flash, it stuck on the Samsung logo, Home + Power + Volume Up don't get me anywhere.
any idea will it be the TWRP version, my phone is K version, BTW i can flash stock version back with no problem
iraqgsm said:
having a problem booting into twrp after the flash, it stuck on the Samsung logo, Home + Power + Volume Up don't get me anywhere.
any idea will it be the TWRP version, my phone is K version, BTW i can flash stock version back with no problem
Click to expand...
Click to collapse
Are you letting it boot into system then trying to boot into twrp or trying to boot direct to twrp after it flashes?
sent from my Note FE, S8 plus, S7 edge or S6
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
wow N7FE cant use old N7 twrp??
malaccio said:
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
Click to expand...
Click to collapse
Yes. Good thing too.
iraqgsm said:
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
Click to expand...
Click to collapse
Still in bootloop?
iraqgsm said:
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
Click to expand...
Click to collapse
Two possibilities why it's not working for you:
Try flashing TWRP with USB debugging off.
Are you placing the TWRP file in the right slot (AP) in Odin?
The last one is obvious, but it's strange that TWRP doesn't open for you.
kenpaci said:
wow N7FE cant use old N7 twrp??
Click to expand...
Click to collapse
Well, it works. But there may be minor problems. If we get enough reports we should be able to isolate these and see what can be done to correct them.
These are early days with FE so there will be little personal data on them yet. So this is a good time for some experimentation, especially as flashing stock is known to be successful.
zamzenos said:
Two possibilities why it's not working for you:
Try flashing TWRP with USB debugging off.
Are you placing the TWRP file in the right slot (AP) in Odin?
The last one is obvious, but it's strange that TWRP doesn't open for you.
Click to expand...
Click to collapse
I will try with USB debugging and I did place it in the AP slot
---------- Post added at 07:05 PM ---------- Previous post was at 06:13 PM ----------
still no go with usb bugging off,
a question that is the only twrp version that is working for you now right
iraqgsm said:
I will try with USB debugging and I did place it in the AP slot
---------- Post added at 07:05 PM ---------- Previous post was at 06:13 PM ----------
still no go with usb bugging off,
a question that is the only twrp version that is working for you now right
Click to expand...
Click to collapse
I used "twrp-3.1.1-0-gracelte.img.tar".
Are you formatting data? If you are, try flashing without allowing modifications and without formatting data. You won't be able to make use of TWRP in that mode, but try it and see what happens.
One last try: If the above fails, try entering stock recovery after you flash the stock firmware.
Finally, I have the K variant. It might be that the problem occurs because you have a different variant.
You could get the TWRP app (check the TWRP site). There is a specific version for korean telecoms (graceltekor). I've dloaded it and will give it a try tomorrow. But you should test the above suggestions first.
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
this version of twrp is newer than the one you have on the first post, it worked perfectly thank you
Click to expand...
Click to collapse
iraqgsm said:
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
this version of twrp is newer than the one you have on the first post, it worked perfectly thank you
Click to expand...
Click to collapse
Which version did you use? I've just flashed the korean version myself. No problems. I'm amending the OP to give people a choice.
Glad it worked for you. Hope this will encourage others to take the plunge.
Click to expand...
Click to collapse
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
Are you formatting data? If you are, try flashing without allowing modifications and without formatting data. You won't be able to make use of TWRP in that mode, but try it and see what happens.
One last try: If the above fails, try entering stock recovery after you flash the stock firmware.
Finally, I have the K variant. It might be that the problem occurs because you have a different variant.
You could get the TWRP app (check the TWRP site). There is a specific version for korean telecoms (graceltekor). I've dloaded it and will give it a try tomorrow. But you should test the above suggestions first.
Click to expand...
Click to collapse
zamzenos said:
iraqgsm said:
Which version did you use? I've just flashed the korean version myself. No problems. I'm amending the OP to give people a choice.
Glad it worked for you. Hope this will encourage others to take the plunge.
Click to expand...
Click to collapse
the twrp-3.1.1-0-gracelte.img.tar worked.
twrp-3.0.2-1-graceltexx.tar.md5 didnt work
honestly, it was easy thank you
Click to expand...
Click to collapse
iraqgsm said:
zamzenos said:
the twrp-3.1.1-0-gracelte.img.tar worked.
twrp-3.0.2-1-graceltexx.tar.md5 didnt work
honestly, it was easy thank you
Click to expand...
Click to collapse
There's a 3.1.1-0 version of the korean version (graceltekor) too. Use the new link I added to the OP. I've tried both today, now that I have a better idea of what is involved. Both work fine, seems to be no difference between them - I mean, for our purposes.
But it's really good to have full root. Honestly never expected it to be this good.
Click to expand...
Click to collapse
BerndausLB said:
Link is dead.
I have SM-N935K and need the stock firmware please.
Any help (working link) is highly appreciated.
Thank you.
Click to expand...
Click to collapse
Only link I had: http://fixedfirmware.blogspot.ie/2017/07/samsung-galaxy-note-7-fe-sm-n935skl.html.
Try this link (haven't tried this myself): https://www.androidfilehost.com/?fid=817550096634784008
Google for it otherwise. But you may be able to use one of the other variants. There was a discussion here. Not sure of the outcome, though.
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.
Similar to the previous threads for OnePlus 5, OnePlus 5T or OnePlus 6, here are the necessary packages to unbrick/revive a hard bricked OnePlus 7 Pro.
The following hardware revisions are supported:
GM1910: China
GM1911: India
GM1913: Europe
GM1917: Global/US Unlocked
Download: https://www.androidfilehost.com/?w=files&flid=294744
guacamole_21_H.04_190416_unlocked.zip
After using it, the phone will be restored to HydrogenOS aka Chinese firmware.
Click to expand...
Click to collapse
guacamole_21_E.08_190515_unlocked.rar
After using it, the phone will be restored to OxygenOS 9.5.4.GM21BA aka European firmware.
Click to expand...
Click to collapse
guacamole_21_O.07_190512_unlocked.zip
After using it, the phone will be restored to OxygenOS 9.5.3.GM21AA aka global firmware.
Click to expand...
Click to collapse
In every case, it is possible to upgrade to latest OxygenOS by using full signed zip from this thread via Local Upgrade.
With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.
Use the most updated signed driver (2.1.2.2 at this moment) to avoid potential issues..
For detailed procedures, please consult the linked threads above. There is no reason to repeat the same thing again.
Make sure the path of the extracted files doesn't contain any non-English character. The tool isn't unicode aware.
Source:
HydrogenOS package: 人艱不拆 (OnePlus China forum thread), @trollavin & @Some_Random_Username for the help in mirroring
OxygenOS (EU) package: @MrVoshel
OxygenOS (global) package: @Lucifer6
Reserved for future.
Thank you for this!!
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
LLStarks said:
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
Click to expand...
Click to collapse
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
jkyoho said:
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
Click to expand...
Click to collapse
Well, that's the perfect explanation.
:highfive:
Can you turn TMobile to int'l with this ?
HtcOnekid said:
Can you turn TMobile to int'l with this ?
Click to expand...
Click to collapse
What he said
When i start MsmdownloadtoolV4.0.exe it says :
Packet image not exist!
Take out the Chinese characters in the file name and then try
joemossjr said:
Take out the Chinese characters in the file name and then try
Click to expand...
Click to collapse
Yep that's i though, but i finaly looking for EU version. Because i think with OTA upgrade to GMBA EU modem will not contain the good modem right ?
---------- Post added at 12:59 AM ---------- Previous post was at 12:27 AM ----------
failed to install on EU model : param preprocessing and stop at 5 ou 7 sec before flashing. I tryed using anothere patched tool and not working :s
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
what is your device OOS 9.5.3/4/5/6 ?
flash the co-responding stock boot.img from twrp with magisk zip together, and see if you can boot
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
thebigtross said:
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
Click to expand...
Click to collapse
Thanks for your replies! I was on OOS 9.5.5 and I tried flashing the twrp/magisk zips but that didn't work either. I also tried applying the stock boot.img to the active slot, but still got the recovery bootloop.
So as my last hope, I wiped all data in recovery mode, rebooted to fastboot and sideloaded the complete stock image from here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I reconfigured my phone from scratch, rooted with the patched boot image like before and everythings works now. Guess I will not bother with TWRP any time soon.
Added global and EU packages.
Titokhan said:
Added global and EU packages.
Click to expand...
Click to collapse
Will global work for 1911 (India)
Mr.Crucial said:
Will global work for 1911 (India)
Click to expand...
Click to collapse
Yes, the packages are interchangable.
[/COLOR]
Titokhan said:
Yes, the packages are interchangable.
Click to expand...
Click to collapse
But I think that these packages will not work on T-mobile 1915!
When I reboot into edl mode, it recognizes the "Qualcomm HS-USB QDLoader 9008", but then 10 seconds later, the phone automatically boots the the battery display, which disables edl. The same this happens whether I use the vol up+down and plug in, or `adb reboot edl`.
Edit: "How I learned to stop worrying and risk a brick"
Selecting the right COM and hitting start in MSMtool in that 10 second window kept it in edl mode for the duration of the flash.
I'm trying to root my Samsung Galaxy S6 Edge (build version G925AUCS7ERC1) running 7.0 nougat.
On this firmware, pingpong root does not work. So, today I tried to revert my phone back to android 5.0 by flashing an old rom (build version G925AUCU1AOCE).
It didn't work. I got an error message "REV. CHECK FAILED," which is specifically built in to prevent you from downgrading (**** you Samsung)
Does anyone know how to root this model/firmware?
Thanks
dude use magisk
anon_lastname said:
I'm trying to root my Samsung Galaxy S6 Edge (build version G925AUCS7ERC1) running 7.0 nougat.
On this firmware, pingpong root does not work. So, today I tried to revert my phone back to android 5.0 by flashing an old rom (build version G925AUCU1AOCE).
It didn't work. I got an error message "REV. CHECK FAILED," which is specifically built in to prevent you from downgrading (**** you Samsung)
Does anyone know how to root this model/firmware?
Thanks
Click to expand...
Click to collapse
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Zac C4rter said:
dude use magisk
Click to expand...
Click to collapse
That sounds promising. However, it seems TWRP is required to install Magisk. And it seems there is no TWRP image for G925a ( https://twrp.me/samsung/samsunggalaxys6edge.html)
Another problem is that I can't get fastboot to recognize the phone. "adb reboot bootloader" reboots the phone but it doesn't enter fastboot mode.
Do you have any advice on how to get magisk installed on this specific model?
anon_lastname said:
That sounds promising. However, it seems TWRP is required to install Magisk. And it seems there is no TWRP image for G925a ( https://twrp.me/samsung/samsunggalaxys6edge.html)
Another problem is that I can't get fastboot to recognize the phone. "adb reboot bootloader" reboots the phone but it doesn't enter fastboot mode.
Do you have any advice on how to get magisk installed on this specific model?
Click to expand...
Click to collapse
try this https://dl.twrp.me/zeroflte/twrp-3.3.1-0-zeroflte.img.tar.html
Zac C4rter said:
try this https://dl.twrp.me/zeroflte/twrp-3.3.1-0-zeroflte.img.tar.html
Click to expand...
Click to collapse
So, I tried to flash that recovery.img file to the recovery partition of my phone using Heimdall. It didn't work. (The reason I used heimdall is because my operating system is Linux. I'm pretty sure the behavior would be the same on Odin.)
The error message I got on the phone was "SECURE CHECK FAIL : (RECOVERY)"
After doing some research, it seems that on these "newer" Samsung models you're simply not allowed to write these partitions. It seems that Samsung supports installing a custom OS like Lineage, but they don't want you to mess around with the proprietary OS.
anon_lastname said:
So, I tried to flash that recovery.img file to the recovery partition of my phone using Heimdall. It didn't work. (The reason I used heimdall is because my operating system is Linux. I'm pretty sure the behavior would be the same on Odin.)
The error message I got on the phone was "SECURE CHECK FAIL : (RECOVERY)"
After doing some research, it seems that on these "newer" Samsung models you're simply not allowed to write these partitions. It seems that Samsung supports installing a custom OS like Lineage, but they don't want you to mess around with the proprietary OS.
Click to expand...
Click to collapse
This looks like the exact problem I am having:
No OEM Unlock in Developer Options SM-G925A
hi, I have a SM-G925A with Nougat 7.0 and August 2017 security patch, but I can't find OEM Unlock option in developer options, most posts online say that means it should be already unlocked, but when trying to flash twrp with odin in download...
forum.xda-developers.com
Ran into the same problem. PIT file is correct but heimdall and JOdin3 both have issues trying to put TWRP into recovery. I did manage to get JOdin3 to work by adding/replacing the /etc/udev/rules.d/51-android.rules (see attached), but it did not take. Go figure.