Related
My phone doesnot go past google logo.
Need the stock recovery and system image
I am thinking once i get them i should be able to run using FAstboot commands
without even unlocking(as fast boot oem unlock also not working for me) boot loader..somebody please confirm...
I tried fastboot update update.zip with Official 2.3.3 ROM but i get following error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is not rooted neither the boot loader is unlocked( I have failed to unlock it with Fastboot OEM unlock)
First thing first... connect your phone and type "adb devices". Does your serial nr show up? Turn off your phone and boot into bootloader (hold vol up + power). Type "fastboot devices", does your serial nr show up? If not, adb and/or fastboot isn't recognizing your connection and device. If it does, you SHOULD be able to type "fastboot oem unlock" to unlock your bootloader.
Tip: you can view your bootlooader state on the device display when inside the loader. It says "State: LOCKED" or "State: UNLOCKED" respectively.
[ROM] Samsung stock D720 for Nexus S 4G
All else fails, this should get your phone back to factory.
http://forum.xda-developers.com/showthread.php?t=1072698
http://www.holylivingfuck.com/Crap/SamsungSimpleDL_D720(1.0.002).zip
MIRROR
http://www.fileserve.com/file/JnCgZkm
I have nexus s GSM(tmobile version) , anybody knows similar link like above for it.
jottosson said:
First thing first... connect your phone and type "adb devices". Does your serial nr show up? Turn off your phone and boot into bootloader (hold vol up + power). Type "fastboot devices", does your serial nr show up? If not, adb and/or fastboot isn't recognizing your connection and device. If it does, you SHOULD be able to type "fastboot oem unlock" to unlock your bootloader.
Tip: you can view your bootlooader state on the device display when inside the loader. It says "State: LOCKED" or "State: UNLOCKED" respectively.
Click to expand...
Click to collapse
when i run adb devices it doesnt display any device seems it needs usb debugging enabled which I cant do as mentioned above.
when i run fastboot devices , it does display my phone's serial number but when i run the command fastboot oem unlock my phone displays a confirmation to select "Yes or no" , i chose "yes" and hit the power button but then it doesnt do any thing it just stays there , i tried multiple times waited several mins to hours but no luck yet.
I am running all this on windows 7 64 bit computer .
http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK
justsahid said:
when i run adb devices it doesnt display any device seems it needs usb debugging enabled which I cant do as mentioned above.
when i run fastboot devices , it does display my phone's serial number but when i run the command fastboot oem unlock my phone displays a confirmation to select "Yes or no" , i chose "yes" and hit the power button but then it doesnt do any thing it just stays there , i tried multiple times waited several mins to hours but no luck yet.
I am running all this on windows 7 64 bit computer .
Click to expand...
Click to collapse
cadams14 said:
http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK
Click to expand...
Click to collapse
this doesnt work as it also asks to unlock botloader sing Fastboot oem unlock
i am also stuck in the same situation but i dont have a sprint 4g. is there any other links available?
Another one here. Same situation. Any resolutions yet?
jboxer said:
Another one here. Same situation. Any resolutions yet?
Click to expand...
Click to collapse
Here you go, set your phone to download mode and use ODIN to flash your phone (i9020) back to stock.
http://www.samfirmware.com/WEBPROTECT-i9020.htm
justsahid said:
My phone doesnot go past google logo.
Need the stock recovery and system image
I am thinking once i get them i should be able to run using FAstboot commands
without even unlocking(as fast boot oem unlock also not working for me) boot loader..somebody please confirm...
Click to expand...
Click to collapse
Check out that u hv installed driver properly for fastboot. Bootloader need to b unlocked for getting into Download mode.
Sent from my Nexus S using XDA App
zirra said:
Here you go, set your phone to download mode and use ODIN to flash your phone (i9020) back to stock.
http://www.samfirmware.com/WEBPROTECT-i9020.htm
Click to expand...
Click to collapse
This will work for the t? I was under the impression we didnt have any images for the 9020t version.
Edit: I just signed up for the site and everything, and it says nothing about being for the T version.
Yes that Odin package from Samfirmwares is for the I9020T. However it is not version 2.3.3, but rather 2.3.1 GRH78.
Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!
Nexus Tool Kit
rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.
Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.
Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier
Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter
Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards
the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.
Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot
I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.
Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.
It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu
So i wanted to create a key mapping for android over my android game using my xbox one controller but all the apps that allow it require rooting. So i quickly came here to see if it was rootable and surely my model was listed. LG k20 Plus MP260, So i go and download adb tap my build number, do the usb debugging, allow oem unlocking, downloaded the Lg drivers, moved the recovery.img to the adb file folder directory, moved the super user Zip file and the no-verity-opt-encrypt-5.1.Zip to the internal storage of the phone. Then run Shift+ Right click adb reboot bootloader using Windows powershell command line and i'm in fastboot mode (I can also just power the phone off and hold the volume down button and plug usb into phone to get into it). So i use fastboot devices to make sure the computer recognized my device and it does. Note: (the bootloader is already unlocked) Then i use fastboot flash recovery recovery.img and it flashes. what happens next is well. I use fastboot reboot and well i get "Your device software cannot be checked for corruption lock the bootloader" and below that it say "PRESS THE POWER KEY TO CONTINUE" i press the power key and it boots up normally. In the video's i've watched they say it will boot into the system twrp and my phone is not doing this. I'm willing to let someone team view me and skype me so we can work this out together and i'm even willing to pay 20$ if we can get this done. Please message me asap
I have the exact same problem. Did you ever figure it out?
Bumping an oldish thread, because this still exists. Custom recovery isn't very useful when you can't get to it without reflashing it every time.
dbsc said:
Bumping an oldish thread, because this still exists. Custom recovery isn't very useful when you can't get to it without reflashing it every time.
Click to expand...
Click to collapse
Did you find a solution? I've been fighting my LG K20 plus metroPCS for over 2 weeks. It won't go into download mode or recovery. In recovery it skips over the reset page. I think the phone is possessed lol.
Hi,
I want to install a custom ROM in my Note 4 and upgrade from Android 6.01 to Android 11, and I know that the first step is to unlock the bootloader to avoid issues later on in the process.
I've researched different ways of doing it, and this is what I found:
1. Enable the OEM unlocking option in the phone.
The phone does not have the option to enable OEM unlocking in the developer options of the phone.
2. Go to download mode (starting phone with Power+Home+Vol Down keys).
At this point 3 options should appear. One of them being Press Vol Up to enter Device unlock mode. Well, only 2 options appear and the one missing is Enter
Device unlock mode.
3. Start in Recovery Mode, then select Enter Fastboot.
I started the phone using Power+Volume up+Home to enter Recovery Mode, and a menu presented with several options which should have included the
Enter Fastboot option, but the option is missing in the menu.
4. Use your PC to issue adb+fastboot commands.
I successfully connected the phone to the PC and tried to issue the corresponding commands using adb and fastboot. Adb commands work well. Fastboot
commands do not "see" the phone. (just in case I've tried several different drivers)
At this point I've run out of options, and everything points to the "hard-to-believe" fact that this phone doesn't have the fastboot mode.
Is it possible that the phone does not have a way to unlock the bootloader? or at least checking that the bootloader is unlocked in a way that leaves no doubt about it? (I can't risk bricking the phone based on the assumption that the bootloader is factory unlocked)
I will really appreciate any help in working this sort of mystery out.
Thank you!!
I
rfernandez2007 said:
Hi,
I want to install a custom ROM in my Note 4 and upgrade from Android 6.01 to Android 11, and I know that the first step is to unlock the bootloader to avoid issues later on in the process.
I've researched different ways of doing it, and this is what I found:
1. Enable the OEM unlocking option in the phone.
The phone does not have the option to enable OEM unlocking in the developer options of the phone.
2. Go to download mode (starting phone with Power+Home+Vol Down keys).
At this point 3 options should appear. One of them being Press Vol Up to enter Device unlock mode. Well, only 2 options appear and the one missing is Enter
Device unlock mode.
3. Start in Recovery Mode, then select Enter Fastboot.
I started the phone using Power+Volume up+Home to enter Recovery Mode, and a menu presented with several options which should have included the
Enter Fastboot option, but the option is missing in the menu.
4. Use your PC to issue adb+fastboot commands.
I successfully connected the phone to the PC and tried to issue the corresponding commands using adb and fastboot. Adb commands work well. Fastboot
commands do not "see" the phone. (just in case I've tried several different drivers)
At this point I've run out of options, and everything points to the "hard-to-believe" fact that this phone doesn't have the fastboot mode.
Is it possible that the phone does not have a way to unlock the bootloader? or at least checking that the bootloader is unlocked in a way that leaves no doubt about it? (I can't risk bricking the phone based on the assumption that the bootloader is factory unlocked)
I will really appreciate any help in working this sort of mystery out.
Thank you!!
Click to expand...
Click to collapse
If your phone is exynos, just factory data reset and go to download mode and flash TWRP.
SweptDevUwU said:
I
If your phone is exynos, just factory data reset and go to download mode and flash TWRP.
Click to expand...
Click to collapse
Thank you for your answer!
It is Exynos indeed.
Have you tried this in a similar situation? or in case you haven't, could you please explain how you are certain that this will work well?
Because it is difficult to ignore the large number of warnings about going on with the flashing without being sure that the bootloader is unlocked.
rfernandez2007 said:
Thank you for your answer!
It is Exynos indeed.
Have you tried this in a similar situation? or in case you haven't, could you please explain how you are certain that this will work well?
Because it is difficult to ignore the large number of warnings about going on with the flashing without being sure that the bootloader is unlocked.
Click to expand...
Click to collapse
Hello, I'm using exynos as well, just like he said just install a compatible TWRP then flash a custom rom you want
https://forum.xda-developers.com/t/...xy-note-4-custom-recovery-07-28-2021.4311777/
karlsuu said:
Hello, I'm using exynos as well, just like he said just install a compatible TWRP then flash a custom rom you want
https://forum.xda-developers.com/t/...xy-note-4-custom-recovery-07-28-2021.4311777/
Click to expand...
Click to collapse
Hi!
Thank you for your answer.
Ok. I'll review/follow the procedure in the link you suggested and let you know how it goes.
Hi,
It worked!!
Thank you very much to both of you!