Related
Hey all,
So I posted what I did to **** everything up the other day: https://forum.xda-developers.com/ta...ie-tried-to-root-device-t3655848?goto=newpost
I read about 70 different forums posts and concluded (somehow) that i needed to try and flash "twrp_3.1.0" for my T810. Well, for some reason it worked. I now have twrp on my boot-looped device.
Now, I'm trying to install a different recommendation which is the "SuperSU-v2.76" ROM through dragging it onto my tablet via My Computer (Since Odin refuses to load it)
Guess what? Ran into another problem when doing this. My T810 will no longer connect with my PC. It is stating "Device driver software was not successfully installed"... throwing out an error message MTP USB Device Failed.
I came up with the wise idea to simply put the SuperSU file on my brand new 128gb micro SD card. I found a USB adaptor for the card, plugged it into my PC and now My Computer is stating that the Micro SD card only has 1.67mb of space available. Did a bunch of research and found out that the USB adaptor actually has a limitor pre programmed into it so that you cannot adapt large SD cards..
I'm striking out guys. I need help. I'm able to navigate the twrp menu.. is there an option on this screen that will help me? I cannot think of what needs to be done next to get this Tab working....
also
.... yes I have the Samsung USB driver installed for my particular device....
So I ended up running to the store and I bought a 16gb micro SD. It worked, I was able to run the SuperSU-v2.76 flash on my device. Geuss what happened next?
Bootloop again.
Currently trying another suggestion which calls for restoring the tablet to an original OEM flash. Going to try installing the "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" flash and ill post what happens........
NOPE! No good. twrp does not recognize booting MD5 files.... I'm stuck again.
dyrewolv said:
Click to expand...
Click to collapse
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
ashyx said:
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
Click to expand...
Click to collapse
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
dyrewolv said:
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
Click to expand...
Click to collapse
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
ashyx said:
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
Click to expand...
Click to collapse
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
dyrewolv said:
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
Click to expand...
Click to collapse
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
ashyx said:
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
Click to expand...
Click to collapse
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
dyrewolv said:
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
Click to expand...
Click to collapse
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
ashyx said:
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
Click to expand...
Click to collapse
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
dyrewolv said:
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
Click to expand...
Click to collapse
It probably fails because you can't downgrade.
It's up to you to whether to flash MM or NN.
You will need to update first and then flash twrp and then supersu.
Hello ... Any ideas on recovering IMEI after successful root of Note9 ?
IMEI currently unknown (both), TWRP shows empty EFS folder (should i see these files?), Software Baseband is UNKNOWN too.
Software factory wipe done with no effect, OEM unlock is unlocked (and not greyed out).
Thanks
Just wondering if anyone has recovered from this ?
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
bober10113 said:
did you read all of dr ketans thread on root?
Click to expand...
Click to collapse
do let us know the tread link
bober10113 said:
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
Click to expand...
Click to collapse
nrah said:
do let us know the tread link
Click to expand...
Click to collapse
added link
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
nrah said:
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
Click to expand...
Click to collapse
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
bober10113 said:
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
Click to expand...
Click to collapse
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
nrah said:
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
Click to expand...
Click to collapse
are you on pie or oreo?
bober10113 said:
are you on pie or oreo?
Click to expand...
Click to collapse
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
nrah said:
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
Click to expand...
Click to collapse
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
bober10113 said:
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
Click to expand...
Click to collapse
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
nrah said:
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
Click to expand...
Click to collapse
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
if i dont do the manual software update check thing after a binaries issue, i would get stuck.
also unrelated:
when you flash stock, you flash all 5 files right?( in odin csc slot you put csc.md5 and not the home csc.md5 and all the other slots only have 1 appropriate file so you cant go wrong there)
endurance:
https://forum.xda-developers.com/galaxy-note-9/development/kernel-endurance-kernel-v1-1-7-t3883862/
v2.xxxx is pie
v1.xxxx is oreo
after flashing kernel.zip you MUST flash magisk or you wont have anyways to manage root and give permissions.
so also flash right after kernel:
https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip will eventualy be not the latest( check last link below dor mire up to date)
then if and when phone boots up you can install the magisk manager app:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.2/MagiskManager-v7.1.2.apk
both can be found here are up to date :
https://github.com/topjohnwu/Magisk/releases
bober10113 said:
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
Click to expand...
Click to collapse
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
nrah said:
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
Click to expand...
Click to collapse
well thats one of your problems. if oem unlock has not appeared you either need to wait for 7 days or try the method i described by visiting system/software update/manual update and wait for a pop up message that says device registered. then go back to dev options to see of OEM unlock has appeard and says that it is unlocked
Waititng 7 days sure....
That doesn't work imho. Just download an older 8.1 stock rom and flash . u will find OEM to be unlocked there.
The fix in the end was to use the Root_for_OEM_issue_devices_v5 script. I had been using the v3 script. I had followed Max's vid from high on Android, where he's got the earlier script version on his site.
Issue also, once rooted, was that Magisk was out of sync - Magisk was ahead of the manager, so i down graded the manager (once I worked out the release pairs), and magisk was stable again. I did note that the Magisk did not always maintain root for some reason, when the version were out of sync. Possible connection, not sure.
Must admit you learn a lot about these phones when you have a root problem - a lot more compared to someone just following someone else's good work and wanting the %100 it will work path !
Thanks bober10113 for chipping in along the way.
My phone is stuck at Samsung Logo I have tried (Stock firmware, wipe data, factory reset nothing works) and the recovery gives the error mentioned in the title.
failed to mount /efs (invalid argument) . I have tried various methods but nothing worked. Anyone have idea how to solve this issue ?
Try smart switch also.
Punitverma2010 said:
Try smart switch also.
Click to expand...
Click to collapse
I have tried smart switch but i am not getting device initialization option in updated version. How ever i have downloaded an older version and found device initialization option it asked me for device model and serial number. I have entered correct information still it is giving me error invalid model number or serial Number.
fahad4210 said:
I have tried smart switch but i am not getting device initialization option in updated version. How ever i have downloaded an older version and found device initialization option it asked me for device model and serial number. I have entered correct information still it is giving me error invalid model number or serial Number.
Click to expand...
Click to collapse
I think going to Samsung service centre might help.
Do you have twrp installed?
Rooted.ndroid said:
Do you have twrp installed?
Click to expand...
Click to collapse
When i am installing TWRP it says Only official binaries are allowed to be flashed.
fahad4210 said:
When i am installing TWRP it says Only official binaries are allowed to be flashed.
Click to expand...
Click to collapse
tried downgrading to 8.1.0?
did your developer option have oem unlocking option? Its that even if unlock bootloader but if your developer option doesn't show oem is already unlocked then it says that to me as well.
But hey I don't know everything you have done, you might have done everything correctly still it screwed you. Best of luck bud.
if you dont mind what happens when you flash the firmware?
Rooted.ndroid said:
tried downgrading to 8.1.0?
did your developer option have oem unlocking option? Its that even if unlock bootloader but if your developer option doesn't show oem is already unlocked then it says that to me as well.
But hey I don't know everything you have done, you might have done everything correctly still it screwed you. Best of luck bud.
if you dont mind what happens when you flash the firmware?
Click to expand...
Click to collapse
My device is stuck at samsung logo and it is not booting. I have tried to downgrade it to 8.1.0 with odin and it was successfully done.
But issue remains the same. Hence it is not booting so i am not able to unlock OEM. I am getting error in recovery that is E: failed to mount /efs (invalid argument) . Somehow i found a threat with a solution and for that i need to install TWRP in my device.
fahad4210 said:
My device is stuck at samsung logo and it is not booting. I have tried to downgrade it to 8.1.0 with odin and it was successfully done.
But issue remains the same. Hence it is not booting so i am not able to unlock OEM. I am getting error in recovery that is E: failed to mount /efs (invalid argument) . Somehow i found a threat with a solution and for that i need to install TWRP in my device.
Click to expand...
Click to collapse
I needed to tweak date to make OEM unlocking: Bootloader is already unlocked on developer options after flashing stock rom of other region but for my exact region it appears each time and I dont need to boot to rom to flash twrp, I can flash the ROM and twrp simultaneously only in my device's original firmware(8.1.0) but not in rom of any other region and on pie.
I hope I'm not annoying you, could you try flashing 8.1.0 by unticking auto reboot ----- force reboot ---- odin --- twrp.
Edit: this thing doesn't make sense.
Rooted.ndroid said:
I needed to tweak date to make OEM unlocking: Bootloader is already unlocked on developer options after flashing stock rom of other region but for my exact region it appears each time and I dont need to boot to rom to flash twrp, I can flash the ROM and twrp simultaneously only in my device's original firmware(8.1.0) but not in rom of any other region and on pie.
I hope I'm not annoying you, could you try flashing 8.1.0 by unticking auto reboot ----- force reboot ---- odin --- twrp.
Click to expand...
Click to collapse
Thanks for guidance and for helping me. I will update you once it done. Hope this will resolve my problem
Rooted.ndroid said:
I needed to tweak date to make OEM unlocking: Bootloader is already unlocked on developer options after flashing stock rom of other region but for my exact region it appears each time and I dont need to boot to rom to flash twrp, I can flash the ROM and twrp simultaneously only in my device's original firmware(8.1.0) but not in rom of any other region and on pie.
I hope I'm not annoying you, could you try flashing 8.1.0 by unticking auto reboot ----- force reboot ---- odin --- twrp.
Click to expand...
Click to collapse
I have tried as you guided my but still i am not able to install TWRP in my device
Flash with odin the correct firmware be aware of U1 or U2 firmware i don't know what u have installed on ur phone.
if it doesn't work flash combination file u will get (factory binary) the u flash the original stock rom for ur smartphone.
Worked for me .:good:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
22350 said:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
Click to expand...
Click to collapse
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
lewmur said:
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
Click to expand...
Click to collapse
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
this is what the screen says when i try to flash
no content in your post
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
lewmur said:
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
Click to expand...
Click to collapse
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
22350 said:
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
Click to expand...
Click to collapse
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
lewmur said:
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
Click to expand...
Click to collapse
Yea, well that's the issue. i am in odin downloading, with the correct rom from samobile, but the flash fails each time
i ended up using these two
Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal...
forum.xda-developers.com
[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917 TWRP 3.2.1-0 Released Dec 9, 2017 TWRP 3.2.1-0 is out now for most currently supported devices. What's new in 3.2.1-0: * minui fixes (cryptomilk) *...
forum.xda-developers.com
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D
dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!
Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?
I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.