Related
Hello everybody,
I rooted my Xperia Z1 about 8 months ago in order to install the 5.1.1 update which didn't roll out for my device probably because it was a global version (5.0.1 was the last OTA). I did a clean install with no problems, flashed DualRecovery, SuperSu, and BusyBox was working just fine. Everything was working perfectly.
About 3 months ago, I tried updating BusyBox, only to tell that the update failed (couldn't install in the path it used to be try changing the path), I read and read, and found that the solution was to delete a certain file from root that prevented me from modifying certain folders and their content(even with root access), and then do a clean install in a different path than the former one. However, I couldn't gain root access to my files, no root explorer worked! It bugged me, but I was busy at that time, so I couldn't resolve it.
Few weeks later I tried rebooting into recovery, but no method worked, no apps, no key combination, no adb, nothing at all worked! After 2 hard days I managed to install TWRP recovery using NUTS recovery project. I rebooted several times, and it was still working. I then installed BusyBox with no problems, and everything was back to perfect. Later I decided to install CM 12.1 because I always used on my Samsung Galaxy Nexus and I always loved it. So using my now working recovery, I backed everything up on a USB and then flashed CM 12.1 WITHOUT its recovery along with a GAPPS package.
CM was installed, which then rebooted into its recovery and tried to install the GAPPS package. The GAPPS installation was a fail. CM recovery asked me to try using TWRP to do such installation ( go figure! ); in fact, CM recovery couldn't flash anything besides another CM 12.1 update. After this point I wasn't able in any possible way to enter TWRP nor install it. Even if I want to flash using fastboot I couln't! adb reads my device just fine, and can use it to reboot into flashmode, which doesn't seem to be functioning properly. The blue light turns on but there isn't a thing on the screen, fastboot can't recognize is it and hence I can't flash anything using fastboot.
Should I reflash partitions if this could be done on Z1? ( I did it before on my Nexus ) Can I use Odin? I even doubt I can enter download mode on my phone
Any help would be much appreciated.
Thanks in advance!
Anyone?
No?
Ok! :sad:
Is your bootloader unlocked? To run cm on our z1 you need an unlocked bootloader because cm needs a custom kernel.
You can try Sony companion app or androxydes flashtool in combination with a pre-rooted ftf to reach stock again.
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
I managed to install TWRP using TWRP Manager app that I downloaded from APKmirror website. I installed GApps and it is working fine right now.
TWRP Manager said that I should have a FOTA recovery or something like that, and if I don't have one then I am installing the recovery on my responsibility.
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Mohdhamm said:
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Click to expand...
Click to collapse
AFAIK, Emma hasn't been updated for a LONG time. It will remain defunct with no updates and no support. Use flashtool from androxyde if you want to continue using Sony's stock ROM.
No bootloader or flash mode detection: That usually means the drivers that interfaces with your phone is missing. Search around XDA for the correct fastboot and adb drivers for your PC's OS.
My approach for fixing your issue: Find the right drivers and put a stable Lollipop ROM on your sdcard. If you have fastboot working (make sure you have unlocked bootloader), flash boot image from the Lollipop zip and flash the recovery image found in some Lollipop threads. If everything goes well, your phone will bootloop, but you'll have working recovery. Press Vol Down when the Sony Logo appears on screen to enter TWRP. Since you saved a backup of your phone elsewhere, erase all the partitions (minus sdcard), format them to ext4, and flash the Lollipop ROM from your sdcard.
Hello all!
Having a difficult issue with my phone. I downloaded and flashed SpaceX-Kernel_MM_RC1_G920F_Test.tar.md5 along with using SuperSu 2.65.apk to root my phone in stock.
Everything went fine, and I installed TWRP Manager to flash the latest TWRP. The flash and verify failed, and it tells me I either already have it installed or something is wrong. Reboot into recovery?
I rebooted my phone, and the screen is stuck with "RECOVERY IS NOT SEANDROID ENFORCING" with the Samsung Logo. Now I can power down and go back into download mode, but I can not flash Twrp via odin, even when it passes the phone is stuck on the recovery screen. I can't restart my phone to boot normally either.
Any suggestions? Thanks in advance.
Edit:
I downloaded the stock firmware from sammobile, and flashed it via Odin 3.10.7. At first it was freezing Odin, after a few tries I closed all my programs and restarted my computer. I reopened Odin with Admin privileges, and flashed again. This time it worked! I guess I will try flashing twrp again.
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.
Hello guys
So I have a N910T3 with baseband N910T3UVS3EPK2. My phone has never been rooted or touched before. I would like to install TWRP so heres what I've done so far.
1.) Enable USB debugging, oem unlock
2.) Downloaded TWRP for note 4 tmobile
3.) Install ADB Drivers
4.) Downloaded ODIN and loaded it with TWRP img.
5.) It downloaded on my phone, and after saying "PASS", I restarted the phone.
6.) If I go to recovery, Stock recovery is still there... Why is that TWRP is not installed?
Thank you.
vvavepacket said:
Hello guys
So I have a N910T3 with baseband N910T3UVS3EPK2. My phone has never been rooted or touched before. I would like to install TWRP so heres what I've done so far.
1.) Enable USB debugging, oem unlock
2.) Downloaded TWRP for note 4 tmobile
3.) Install ADB Drivers
4.) Downloaded ODIN and loaded it with TWRP img.
5.) It downloaded on my phone, and after saying "PASS", I restarted the phone.
6.) If I go to recovery, Stock recovery is still there... Why is that TWRP is not installed?
Thank you.
Click to expand...
Click to collapse
Go to odin options and uncheck auto reboot.
Flash twrp recovery in odin.
Once odin shows pass remove battery and insert again.
Press 3 buttons simontenesly ( volume up+home+power) until Samsung logo shows then let go all buttons.
You will boot into twrp for sure.
Reason why your twrp was not installed because if you dont uncheck auto reboot in odin options the system will rewrite stock recovery if your device reboot after flash twrp.
it worked. nice
Cannot find TWRP .tar or .md5 files for Odin
When I go to download TWRP for my N910T Galaxy Note 4 T-Mobile, running EQB1 firmware, I only see various TWRP versions that are .img files; none that are .tar or .md5 that ODIN wants. Example: twrp-3.0.2-0-tbltetmo.img
So where do I find an ODIN compatible version?
Thanks.
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
jleed88 said:
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
Click to expand...
Click to collapse
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
fast69mopar said:
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
Click to expand...
Click to collapse
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to download the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
fast69mopar said:
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
Click to expand...
Click to collapse
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
jleed88 said:
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
Click to expand...
Click to collapse
Glad it's working for you. Good job. Now you can make your Note 5 your own. I'm an S6 Edge Plus user. We use the exact same ROM as the Note 5. We just use a different kernel. Happy flashing. If you run into any issues don't hesitate to ask me or anyone else here at XDA. This is a great place to read and learn especially with your Note 5. If a problem has occurred before you can bet that someone has posted about it and you will find a solution.
the phone initially booted up normally. and i power off try to enter recovery mode but i got bootloop , is there any way to get into odin mode , recovery mode is broken ( i flashed recovery with odin it took 15 minutes so i click stop and it crashed ) my phone is sm m20