Bootloop flashing miui 12 closed beta - Xiaomi Mi Mix 2 Questions & Answers

hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)

Use fox twrp to flash.

haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I used TWRP. Also tried orangefox

haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I also tried flashing the firmware first

-iwl- said:
hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)
Click to expand...
Click to collapse
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.

paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed

paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
i have no idea what to do now

-iwl- said:
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed
Click to expand...
Click to collapse
when i flashed miui 12 beta it showed on operating software installed before reboot.

paradise220 said:
when i flashed miui 12 beta it showed on operating software installed before reboot.
Click to expand...
Click to collapse
it seems they released a broken rom. i tested again with lineage os and it worked perfectly. so its xiaomi at fault here

Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta

Use chinese twrp

JrAdams said:
Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta
Click to expand...
Click to collapse
Gapps or any google related services doesnt seem to be working with this beta. lots of bugs encountered too, i might just go back to havoc os

Yunus Ceyhan said:
Use chinese twrp
Click to expand...
Click to collapse
Got it working already. just had to flash magisk along with the rom

Related

Bugged Phone - Bootloops with all the roms I've flashed

Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Have you install the Firmware for Redmi 1s by Xiaomi ?
1. install firmware
2. install rom, gapps etc
3. reboot
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
if the above method dont work then try to flash fastboot rom
It was the firmware. I'd never flashed firmware with other phones and neither needed it with other roms. Thanks
Deivid_ said:
Sorry this is the wrong board-- i reposted on Help&Trouble shooting, I don't know how to delete the thread
I tried flashing an old, alpha, version of sailfish on my phone and since then it's been bootlooping. I can access the recovery and install CM11 but after booting it restarts, every 1-2 minutes. Flashing some other roms gives me bootloops (First boot takes >1 minute, the phone resets).
I've already backed up all my data and wiped internal and external storage, but flashing gives me the same problems.
What can I do? I have the latest TWRP installed
Click to expand...
Click to collapse
first of use latest twrp recovery
then wipe everything that you can see(if i say everything then i mean it)
put the latest cm 13.0 zip and gapps to your sd card and
flash both of these and then enjoy
Phuclun510 said:
Have you install the Firmware for Redmi 1s by Xiaomi ?
Click to expand...
Click to collapse
where i can find that firmwire??
savior** said:
where i can find that firmwire??
Click to expand...
Click to collapse
It's in the second or third post of the Cyanogenmod threads in the ORIGINAL DEVELOPMENT subforum.
Already install fastboot rom? these a link http://en.miui.com/thread-14641-1-1.html

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

Phone is always booting in recovery mode

I'm having issues with booting my phone. It suddenly restarted when I was changing my sim card. I cant boot the device normally. I've tried factory reset and format data from twrp. Any solutions will be well appreciated. Thanks in advance.
I'm using MM bootloader
Rifat Rezwan said:
I'm having issues with booting my phone. It suddenly restarted when I was changing my sim card. I cant boot the device normally. I've tried factory reset and format data from twrp. Any solutions will be well appreciated. Thanks in advance.
I'm using MM bootloader
Click to expand...
Click to collapse
apply update via zip. or adb sideload. you will get out of the issue
sukhwant717 said:
apply update via zip. or adb sideload. you will get out of the issue
Click to expand...
Click to collapse
Its not working..I've wiped everything and installed from scratch. still booting in recovery.
Rifat Rezwan said:
Its not working..I've wiped everything and installed from scratch. still booting in recovery.
Click to expand...
Click to collapse
you have twrp ?
Where it says restore mm bl back up, if you don't have one , naughty
you can flash 14.1 cm and gapps instead
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
timbernot said:
you have twrp ?
Where it says restore mm bl back up, if you don't have one , naughty
you can flash 14.1 cm and gapps instead
http://forum.xda-developers.com/zenfone2/help/stuck-recovery-flashing-rom-boot-t3499441
Click to expand...
Click to collapse
I've flashed AICP Nougat and gapps. still no luck. even with adb I cant boot anything other than twrp.
Read the link I posted in my first reply. Jeeese
timbernot said:
Read the link I posted in my first reply. Jeeese
Click to expand...
Click to collapse
Can you help me? Same thing happened to me tonight, I was able to fix it the same way but my phone is not able to detect sim card anymore. I flashed OCT-N latest build and pico gapps.
Rifat Rezwan said:
Can you help me? Same thing happened to me tonight, I was able to fix it the same way but my phone is not able to detect sim card anymore. I flashed OCT-N latest build and pico gapps.
Click to expand...
Click to collapse
Flash Cleanstock rom from android development section and see if prob persists
You have tried the obvious airplane mode??? switching between data and airplane a few times then let it settle a few mins -- a known bug on custom N
timbernot said:
Flash Cleanstock rom from android development section and see if prob persists
You have tried the obvious airplane mode??? switching between data and airplane a few times then let it settle a few mins -- a known bug on custom N
Click to expand...
Click to collapse
Cleanstock solved the problem. Thanks
Rifat Rezwan said:
Cleanstock solved the problem. Thanks
Click to expand...
Click to collapse
Nice
Back Cleanstock up so can revert back to it , flash away until bugs have been ironed out.
Above , switching between airplane mode and data works for me after a reboot and works flawlessly after .
Try AICP ROM
Its marvelous , regular updates
Hi, I have the same problem, actually it happened after updating to latest version of lineage os. I tried everything (various wipes and flashes, restoring stock backups, flashing cleanstock as suggested) but no luck.
I can't even reboot to fastboot through adb, my phone is just a recovery!
I can't imagine how this could impact, but I've just changed my lcd. But I started the update after changing the lcd, and the phone was working before with the previous LOS version, so...
EDIT: ok, I managed to make it work, I flashed TWRP 3.0.3-M3 (I was on 3.0.3-M2, I didn't try to reflash the same version). Too bad I needed just this, I wiped everything, even internal storage lol.

custom roms do not boot up

hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that
logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.
so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D
cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards
Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/
daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?
NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way
daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers

Can Android 10 beta be rooted?

If it can, how? I'm having bootloop issues trying to do that. Thank you.
Bootloop in logo S9
RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up
Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me
S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
it stucks for me on the samsung logo
aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?
Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.

Categories

Resources