Develop Bugs

Root not working on m9 with twrp 2.8.7.0 using chainfire, need help.

I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.

Jerry060599 said:
I have tried everything I think would remotly work, but my phone simply won't go through with the rooting process. I tried flashing chainfire through twrp 2.7.8.0 but everytime the log gets to replacing files, the phone reboots itself into the system, stopping the root. This issues seems to be pretty rare for I can't seem to find any past cases. Could it be something I did that singled me out?
Maybe this list of what I did can help?
1. Bought phone at t-mobile.
2. Got home and immediatly ran a software update with the stock os
3. Updated to 5.1 and proceded to unlock bootloader.
4. Flashed twrp 2.8.7.0
5. Made a nandroid backup of stock os
6. Flashed cyanogenmod 12.1 unofficial build beta 2 for m9 and gapps package.
7. Found ramdom crashes to much to bare, so i restored to factory settings (from the previous nandroid backup)
8. Attepted to root using chainfire beta.
9. Panick ensues as I tried both chainfire cersions with both twrp recovery.
Here is all the logs I can currently get my hands on:
Abnormal bootup notification in the actual OS: http://pastebin.com/BzAvTXxF
Twrp log before flashing root: http://pastebin.com/tDkgSaWd
I am trying to find a way to get the twrp last_log file after twrp crashes so I would have something to go on, but, sense twrp outright crashes, I can't use the copy log button. Adb can't access cache when the phone is booted up either. Is there any other way?
Extra info:
Phone: T-mobile htc m9 hima
OS: 5.1 (latest one availible for my carrier)
Bootloader: unlocked
Safety: S-on
Recovery: Twrp 2.8.7.0 and 2.8.5.0 (I tried both)
Root: Chainfire beta 2.49 and the lastest official stable build (I tried both)
Firmware version: 2.7.531.6
Thankyou in advance for all that took the time to read this. I am completly out of tricks so any help is greatly appreciated.
Click to expand...
Click to collapse
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.

LLegion said:
BRO........YOUR ISSUE IS REALLY EASY TO SOLVE I HAD KIND THE SAME ISSUE, JUST MAKE SURE YOU DO AS FOLLOWS:
1.-FOLLOW EXACTLY AS TOLD BY THE VERY SAME DEVELOPERS OF THE RECOVERY:
https://twrp.me/devices/htconem9.html
2.-INSTALL THE 2.8.7.1-b BETA VERSION NOT THE REGULAR 2.8.7.0
3.-INSTAL SUPERSU 2.49BETA NOT THE 2.46 REGULAR.
IF YOU DO AS I SAY, YOU WILL HAVE A PERFECT M9 WITH TWRP AND ROOTED.
Click to expand...
Click to collapse
tks for the help . will be trying it out.

Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance

LLegion said:
Of u still have issues i can give whatsapp and help you with further assistance
Click to expand...
Click to collapse
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.

Jerry060599 said:
tks for the help . will be trying it out.
Click to expand...
Click to collapse
Of u still have issues i can give whatsapp and help you with further assistance

Jerry060599 said:
Ok. About that 2.8.7.1 twrp image, may I have a link to it? I found some with a google search but none explicitly specifies hima compatibility.
Click to expand...
Click to collapse
Look at post 3 in this thread. Best is you read all information in the first three posts.

Here u havebaccess to my personal folderhttps://drive.google.com/folderview?id=0B--58xBx8PTOfmYyeDdXeFJ1ZnRSdGJTVnVhQTJQZUZiMG5uRWl0blNackNWMVU1NUNoVjg&usp=sharing

Flippy498 said:
Look at post 3 in this thread. Best is you read all information in the first three posts.
Click to expand...
Click to collapse
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.

Jerry060599 said:
Ok. I just tried to flash it. The recovery still crashes/reboots the phone at the line replacing files. :/
Edit: Ill try to do adb sideload instead of flashing it directly from the recovery. Hopfully, I will get some sort of log if I do. Will take another half an hour to update my adb though.
Edit 2: Nope. phone still crashes. This time at "extracting files". Could'nt get logs either. :/ Does anyone know if it is OK to sideload supersu through the stock recovery? This might potentailly eleminate any issues from twrp.
Click to expand...
Click to collapse
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now

dragonesdenano said:
I had the same . Problem was when reverting a nandroid.
So i did restore again same nandroid but ticking only system image. that fixed the problem. then was all normal, zip are flashing good now
Click to expand...
Click to collapse
Sorry for the (extremly) late reply. I had not been home for the past week. I tried restoring to stock system image and flashin su binaries before. It didnt work. At this point, I suspect that the only reason why I can't flash supersu is because of my firmware version. So I'll be wimpering in a corner untill some kind devs at htc decide to release the source for my version.

After flashing CM14.1 Nightly, I can't boot into recovery.

Hello guys,
As stated in the title, I can not boot into recovery since I flashed CM 14.1. I already tried reflashing TWRP, booting TWRP via fastboot, using another, more recent TWRP image.
This is rather urgent, since, although I can boot CM 14.1 without any problem, I forgot to do a Titanium Backup of two apps, so I have to restore a nandroid backup to get those back, which is kind of hard, without access to TWRP. Using TWRP Explorer is out of question, since that, as far as I know, does not work with encrypted backups.
Flashing via Flashify does not work either.
I just tried with the most recent CM Recovery, that does work, but that does not really help, since that won't restore TWRP Backups..
Greetings
jcgruenhage

delete

Just flash twrp again!?

Flash the twrp in the following link https://www.androidfilehost.com/? using flashify from play store .This helped me

daleski75 said:
Just flash twrp again!?
Click to expand...
Click to collapse
That did not work, at least not with the official TWRP. Flashing this TWRP gave me TWRP back, but now restoring the Backup somehow did not work as expected, the old CM 14.1 unofficial build that is in that backup won't boot.
I'll try only restoring the data part onto the official build, is there anything else you can recommend? Another firmware? Something?
Oh and by the way, thank you, for helping here and for you CM 14.1 builds, somehow I couldn't build CM 14.1 and 14, so having your builds was really helpful.

What version of OOS was you on prior to flashing CM14.1?

daleski75 said:
What version of OOS was you on prior to flashing CM14.1?
Click to expand...
Click to collapse
Directly upon receiving my OP3 I flashed CM13, that was in August, so 3.2.4 I guess, and I flashed the firmware of 3.2.6 before flashing Takers and your CM14 and later 14.1 builds.
TWRP behaves funny, the progress of restoring Data is already at 138%, 6800MB of 4899MB, the calculation is not taking compression into account I guess?
LOOOL, I have booted into the official CM14.1 with the old data, no fc or anything, but my pattern does not work anymore. same pattern as before, won't be accepted.

Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.

daleski75 said:
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
Click to expand...
Click to collapse
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.

jcgruenhage said:
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
Click to expand...
Click to collapse
Yup thats the one I am using as well.

daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
Do you know how one would debug something like that? I have nothing but the splash screen in the beginning and then a black screen
I will just flash CM 14.1 and manually extract my OTP tokens from the data backup, so I don't really need to debug that, but it would probably help determine the cause and properly fix it for the future.

Ask for the link
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
May I ask which one? the link is dead ...

I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?

ChrisDiM said:
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
Click to expand...
Click to collapse
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone

Same issue here. Whenever I try to boot into recovery it just goes straight back to the bootloader/fastboot.
**** me, what do I do?

I try "fastboot format userdata" but after i have the same problem with TWRP-3.0.2-1.28

jackalsin said:
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Click to expand...
Click to collapse
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.

ChrisDiM said:
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
Click to expand...
Click to collapse
Hold power button for at least a minute. It's what I did and fixed it.

DevSquad said:
Hold power button for at least a minute. It's what I did and fixed it.
Click to expand...
Click to collapse
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone

ChrisDiM said:
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
Click to expand...
Click to collapse
Can you get into fastboot?
If so, you can sideload a working TWRP via there.

phone trapped in twrp recovery help wanted

so after updates lineage os I cant get out of recovery alt all how to I go about fixing this need step by step instructions to fix and Links with software. thank for help

PerfectQuestion said:
so after updates lineage os I cant get out of recovery alt all how to I go about fixing this need step by step instructions to fix and Links with software. thank for help
Click to expand...
Click to collapse
Can you ?
In TWRP screen -- what number is stated ? (example 3.0.2.1M) what is yours?? ( Make a note before proceeding)
Then select reboot in TWRP
Then select power off.
Count to 15 seconds.
Then press Power and vol+ , at first of two vibes release power - when logo appears, release Vol+
Are you in bootloader now ??
2 perfect questions ?

TWRP 3.0.2.1m and in in bootloader now what.

PerfectQuestion said:
so after updates lineage os I cant get out of recovery alt all how to I go about fixing this need step by step instructions to fix and Links with software. thank for help
Click to expand...
Click to collapse
Which version of twrp you are using ?
---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------
dnishchhal said:
Which version of twrp you are using ?
Click to expand...
Click to collapse
That twrp might have some bugs,
Try this twrp
https://infinitus-rom.com/downloads/uploads/TWRP/TWRP_3.0.3.3_Zenfone2.zip

PerfectQuestion said:
TWRP 3.0.2.1m and in in bootloader now what.
Click to expand...
Click to collapse
Now what ?
You are no longer trapped in TWRP
You can flash cleanstock rom from development section
or flash TWRP 3 0 3 3 and install linOS
:good:

cant flash
ADB just says waiting for device how do I fix it

can u link me to working drivers
need working drivers for it to work

PerfectQuestion said:
ADB just says waiting for device how do I fix it
Click to expand...
Click to collapse
Reboot to bootloader -- if your IFWI version is 0094.0183 for(Z00A 551). Then install this zip (3 0 3 3 ) in TWRP 3 0 2 1M and reboot to recovery and flash whatever you like
Thanks go to say99 :good:
https://infinitus-rom.com/downloads/?dir=uploads/TWRP

wont flash the the zip

any tool I could use to fix it like all in one unbrick tool? and just paste twrp in to files run flash.

that's how I was able to fix last time but cant find tool any more

says install failure

I'm facing the same issue. I've downloaded the new Nightly from Lineage, it rebooted to TWRP and I flashed it.
Now every time I reboot, I come back to TWRP. I've tried installing another rom and it didn't work.
No solution until now.

https://forum.xda-developers.com/showpost.php?p=70172541&postcount=1

timbernot said:
https://forum.xda-developers.com/showpost.php?p=70172541&postcount=1
Click to expand...
Click to collapse
@PerfectQuestion
@tutabeier
How we doing ?
No thanks buttons hit yet in this thread , still having probs ?

[Unofficial][Joan] TWRP 3.2.1 [Oreo firmware]

Introduction
This is a TWRP 3.2.1 build based on an oreo kernel which seems to be required for the oreo firmware of the H930. Currently Im using the kernel from my stock based ROM. In future updates (when i have the time for it, and if its needed) might make it smaller, by removing things like network, wifi and so on drivers. But for now, it works.
The name of the device (which it also checks for if you flash a ROM that has an assert so you wont flash it on the wrong device) is "joan", as thats the official codename of all V30s (inclduing V30S). I decided to that because I want to unite the H930 and US998 development, as the US998 seems to have no problems with H930 roms/kernels.
Bugs/Features
Its basically the same as this TWRP, just newer TWRP version (3.2.1 instead of 3.1.1), newer kernel, and renamed device.
So please for things that dont work go over there. I maybe plan to fix a few things here and there, but its really low priority for now.
Download
Use the one from this post: https://forum.xda-developers.com/showpost.php?p=77828489&postcount=153
FAQ
Why is there now a third TWRP Thread?
The old recoverys dont boot on the new Oreo firmware. This is an updated version that boots on it.
Will this work with the nougat firmware too?
I havent tested it, but it should work, as it uses the same kernel as my korean oreo port.
Whats so special about the Treblelized version?
It can mount/backup/wipe vendor, also flash an image to /vendor. Thats basically it.
Can I flash a treblelized ROM with the normal TWRP?
Yes, you can. You just need the treblelized TWRP if you want to (nativly) mount vendor, or if you want to backup/wipe vendor.
Can't everyone just use the treblelized version?
It's specially intended for people who have repartitioned! You can try, but idk what happens on phones that arent repartitioned, and you use this. Beware of unexpected behaviour!
Sources:
https://github.com/SGCMarkus/android_device_lge_joan-twrp
https://github.com/SGCMarkus/android_kernel_lge_msm8998
XDA:DevDB Information
TWRP - Joan, ROM for the LG V30
Contributors
SGCMarkus
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Alpha
Created 2018-04-18
Last Updated 2018-04-18

I get access denied when i go to to your afh link.

Thank you! Can you check dl link because it req. to login ;/

Jerry08 said:
I get access denied when i go to to your afh link.
Click to expand...
Click to collapse
Dizzyrul3z said:
Thank you! Can you check dl link because it req. to login ;/
Click to expand...
Click to collapse
fixed... wrong link in the clipboard lol

If it's not problem for you, can you made a flashable zip for TWRP?

Dizzyrul3z said:
If it's not problem for you, can you made a flashable zip for TWRP?
Click to expand...
Click to collapse
You can flash an image through TWRP too if you want to update your old one.
In the install menu, switch from "Install zip" to "Install image" (bottom right it was i think)

Damn I did not know that we lern all the time waiting for your rom to flash in twrp and we all be happy

maybe a stupid question, but must I flash before the no-verity-opt-encrypt-6.0.zip ?

kherio said:
maybe a stupid question, but must I flash before the no-verity-opt-encrypt-6.0.zip ?
Click to expand...
Click to collapse
Depends on the rom youre using. the Custom Stock based ones have disabled verity/force encryption already built in what i know. If youre using pure stock, you need to do that once (after you change the boot image).
E.g.
Flash stock rom via kdz -> flash recovery -> format data (if it should be encrypted and twrp cant read it) -> flash no verity-opt encrypt -> flash lrcd (or whatever its called, service that checks if you have root or not) -> flash magisk or so -> setup rom
Thats how i did it, but that doesnt really have todo anything with the recovery itself

Flashed fine from within TWRP. Now waiting for the new Oreo, I'm running the Korea ROM on my unlocked US998.

TWRP
Sorry but I must be doing something wrong or there is a bug as when I install TWRP and I try to access it no matter what I do it always erases everything.
Please let me know if I am doing something wrong.
Thanks

etheodor said:
Sorry but I must be doing something wrong or there is a bug as when I install TWRP and I try to access it no matter what I do it always erases everything.
Please let me know if I am doing something wrong.
Thanks
Click to expand...
Click to collapse
What do you mean by "it erases everything"?
What are the steps you use when you install it?

etheodor said:
Sorry but I must be doing something wrong or there is a bug as when I install TWRP and I try to access it no matter what I do it always erases everything.
Please let me know if I am doing something wrong.
Thanks
Click to expand...
Click to collapse
try after you flash it with "fastboot flash recovery xxxxxxxxxxx.img"
to use this "fastboot boot xxxxxxxxxxx.img"
the way taht i managed to acces it is like this
- flash twrp
- power off phone (DO NOT power it on to enter in its rom)
- press power and volume down
- wait for the first "LG V30 ThinQ" logo to appear
- while i HOLD volume down i let the power button go then press it again
- the black text on white background will appear before the screen which says that you have your bootloader unlocked
- select yes using volume buttons
- press power
- then select yes again
- press power and that's it, just wait and it will enter in recovery

can i flash this in korean model v300s ?

seloka180 said:
can i flash this in korean model v300s [emoji848]
Click to expand...
Click to collapse
No, unless you have a way to unlock the bootloader on the v300s -- and have fastboot flash commands.
Sent via open market LG US998 V30/V30+

TWRP
iRS_ said:
try after you flash it with "fastboot flash recovery xxxxxxxxxxx.img"
to use this "fastboot boot xxxxxxxxxxx.img"
the way taht i managed to acces it is like this
- flash twrp
- power off phone (DO NOT power it on to enter in its rom)
- press power and volume down
- wait for the first "LG V30 ThinQ" logo to appear
- while i HOLD volume down i let the power button go then press it again
- the black text on white background will appear before the screen which says that you have your bootloader unlocked
- select yes using volume buttons
- press power
- then select yes again
- press power and that's it, just wait and it will enter in recovery
Click to expand...
Click to collapse
Thanks very much for the reply. I have tried this exact procedure but after the second yes it erases everything on my phone, and I tried this more than once.
What I have not tied is the "fastboot boot xxxxxxxxxxx.img" I will try this too and see what happens. I will let you know. Thanks again.
---------- Post added at 05:57 AM ---------- Previous post was at 05:36 AM ----------
etheodor said:
Thanks very much for the reply. I have tried this exact procedure but after the second yes it erases everything on my phone, and I tried this more than once.
What I have not tied is the "fastboot boot xxxxxxxxxxx.img" I will try this too and see what happens. I will let you know. Thanks again.
Click to expand...
Click to collapse
I can confirm that "fastboot boot xxxxxxxxxxx.img" is working on my V30 but NOT the key combination

etheodor said:
Thanks very much for the reply. I have tried this exact procedure but after the second yes it erases everything on my phone, and I tried this more than once.
What I have not tied is the "fastboot boot xxxxxxxxxxx.img" I will try this too and see what happens. I will let you know. Thanks again.
---------- Post added at 05:57 AM ---------- Previous post was at 05:36 AM ----------
I can confirm that "fastboot boot xxxxxxxxxxx.img" is working on my V30 but NOT the key combination
Click to expand...
Click to collapse
the key combination can be rather tricky, and you need a pretty good timing for it too, i rarely manage it on the first try ?

TWRP
SGCMarkus said:
the key combination can be rather tricky, and you need a pretty good timing for it too, i rarely manage it on the first try
Click to expand...
Click to collapse
I see, this is not a problem I would rather use the fastboot command which is more safe that the key combo.
Thanks very match for your help

the key combo sometimes tricked me because the twrp was not properly installed and i ended up erasing everything... i always use fastboot command or TWRP official app to reboot in recovery. those are the safest procedures

Not sure how so many people are having issues with the key combination, it is very easy to do. I have updated to Oreo and have unlocked, installed twrp and rooted it successfully first try.
1. Hold both volume down and power until you see the first logo
2. Let go of power while still holding volume down
3. Press and hold down power again, along with volume down
4. You will be on a white screen
5. Choose yes and yes, you have to do this erase procedure twice
6. After the second erase you should now see the twrp splash screen
That is exactly how i did it and it was successful on the first try. I have tried same procedure again 4 times since and have don 2 of my friends phones, all worked perfectly first time

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