Related
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
I m not sure about it. Do they actually differ ? i317 and n7105 (My thoughts they are same, Actually ALL Canadian versions of note 2 are same)
xtacydima said:
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
Click to expand...
Click to collapse
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
lsdhillon said:
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
Click to expand...
Click to collapse
yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
majicmazo said:
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
Click to expand...
Click to collapse
I m gonna go to twrp 2.8.5. Hopefully it works. Will be back with results soon.
i get this error after installation (Using twrp 2.8.5.0 now)
"unmount of /system failed; no such volume"
Probably this is cause?
How to fix it?
and
I m using twrp for t0lte (i have SGH-i317m) I hope its all right with that.
lsdhillon said:
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
Click to expand...
Click to collapse
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
xtacydima said:
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
Click to expand...
Click to collapse
Could you please guide me to stable risk-free custom kernel for my sgh-i317
yaro666 said:
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
Click to expand...
Click to collapse
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
lsdhillon said:
Could you please guide me to stable risk-free custom kernel for my sgh-i317
Click to expand...
Click to collapse
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
Click to expand...
Click to collapse
really stock kernel with MJ5 modem and old bootloader up until this year january, as I updated to RR 5.1.1 and then updated bl, modem to OC and flashed CM13
xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
Click to expand...
Click to collapse
I flashed AGNI kernel but the results were still same. Now gonna flash http://d-h.st/JUm as xtacydima suggested(Thanks).
Hope it works.
Will be back with results soon.
Do i need to update modem? to install RR (Marshmallow)?
With http://d-h.st/JUm as xtacydima suggested
It doesnt pass note 2 logo
Just goes blank after note 2 logo, So i think it isnt supported.
i m on 4.4.2 stock now.
Another thing i note is that my baseband is "unknown".
Any suggestions?
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help
RADIUM KERNEL FOR THE MOTO G 2014!
This is my first kernel! This is primarily a companion to my Radium Redefined M rom, but I'm also putting it up here for people who don't like to flash roms (Well, they're missing out, aren't they ). It'll start off as close to stock, I'll add features slowly (Keep those requests comin' in!)
NOTE- THIS KERNEL IS ONLY FOR STOCK/STOCK BASED ROMS. DO NOT FLASH IT ON CM/AOSP ROMS. ANYWAYS, I'M NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE
So here we go!-
Features-
OC/UC (1.5GHz/96MHz)
Compiled with UBERTC 4.9
That's it for now
How to flash-
1. Download the latest version
2. Reboot to recovery
3. Flash (You need not wipe anything)
4. Reboot and enjoy!
I know, the features are very less. But it starts off this way. I'm still learning. I'll be adding more governors/hotplugs slowly
Downloads-
LATEST VERSION (R1)
Mirror
ALL BUILDS (FOLDER)
Credits-
1. @zakee94 - For help with OC and ramdisk changes
2. @attack11 - For help with source code
XDA:DevDB Information
Radium Kernel , Kernel for the Moto G 2014
Contributors
Vidhanth
Source Code: https://github.com/Vidhanth/Radium-Kernel
Kernel Special Features: Overclocked and Underclocked to 1.5 GHz and 96 MHz. Optimized with Uber toolchain.
Version Information
Status: Stable
Created 2016-05-15
Last Updated 2016-05-15
RECOMMENDED SETTINGS-
As of now, the kernel is pretty much stock. So it's perfect out of the box.
You can do one thing tho- Change read ahead of Internal Storage to 1024 KB and externel to 4096 KB (If you have a 32 GB card. If other, set a lesser value).
I'll be updating this when we have more features
Reserved
Mine
@Vidhanth
The kernel flashes properly. However, after rebooting, root access breaks. So no root access, after booting. Wiping dalvik and cache doesn't help either. And here are the relevant screenshots.
VirenLuke said:
@Vidhanth
The kernel flashes properly. However, after rebooting, root access breaks. So no root access, after booting. Wiping dalvik and cache doesn't help either. And here are the relevant screenshots.
Click to expand...
Click to collapse
Of course that's normal. SuperSU is systemless, so it patches the boot.img. This kernel replaces your previously patched boot.img so you lose root access. To fix this, you need to flash SuperSU again
Vidhanth said:
Of course that's normal. SuperSU is systemless, so it patches the boot.img. This kernel replaces your previously patched boot.img so you lose root access. To fix this, you need to flash SuperSU again
Click to expand...
Click to collapse
Okay, I reflashed SuperSU, got systemless root working again
Everything works perfectly.
Viren said:
Okay, I reflashed SuperSU, got systemless root working again
Everything works perfectly.
Click to expand...
Click to collapse
Could you please tell me what version of supersu you used and if possible provide the link?
For already I used two versions and does not leave the bootloop
dougluna said:
Could you please tell me what version of supersu you used and if possible provide the link?
For already I used two versions and does not leave the bootloop
Click to expand...
Click to collapse
SuperSU version 2.62 :
https://download.chainfire.eu/748/SuperSU/?
The problem is that beyond 2.62, the method of rooting changed from patching the boot image for a systemless root, to the old fashioned method of /system rooting. While the newer method works on all custom ROMs, it so happens that the stock Motorola ROM requires you to perform a systemless root. So go ahead and install the version in that link. After that, you can boot up, go to the play store, and update from there to version 2.65, which is the current stable build.
For already I used two versions and does not leave the loop boot
Sent from my Moto G 2014 using XDA-Developers mobile app
Viren said:
SuperSU version 2.62 :
https://download.chainfire.eu/748/SuperSU/?
The problem is that beyond 2.62, the method of rooting changed from patching the boot image for a systemless root, to the old fashioned method of /system rooting. While the newer method works on all custom ROMs, it so happens that the stock Motorola ROM requires you to perform a systemless root. So go ahead and install the version in that link. After that, you can boot up, go to the play store, and update from there to version 2.65, which is the current stable build.
Click to expand...
Click to collapse
Thank you very much
stuck on boot screen
ditoparlo said:
stuck on boot screen
Click to expand...
Click to collapse
Please answer two questions:
1. Are you using a stock ROM?
In other words, are you using Radium Redefined?
Or are you using any other ROM out there?
2. Did you flash SuperSU 2.62?
Or did you flash any other version than this?
If the answer to either is yes, please go read the OP and all the posts that follow, thoroughly. That will solve your problems If not, then please provide more information. "Bootloop" isn't enough information to help.
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Click to expand...
Click to collapse
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
I think you can open the Radium Rom zip, the radium kernel zip and copy the system folder and the boot.img from the zip kernel to the rom kernel, replace and i think it will boot fine with radium kernel by default
AcTSkull said:
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
Click to expand...
Click to collapse
Its not yet i think.
sonrics1993 said:
Bootloop, in Radium and flashing SUPERSU 2.62...
Is the order correct?
Install radium
Flash gapps
Reboot
Flash kernel
Flash SUPERSU?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try this -
Flash radium + gapps + kernel
Reboot
Flash supersu
Reboot
And are you sure it's a bootloop? The first boot takes a while. If you think it's taking too long, just force restart from the bootanimation
AcTSkull said:
Correct me if I'm wrong, but I'm pretty sure this kernel is already built-in in the Radium's rom, so you don't need to re-flash it from this thread.
Click to expand...
Click to collapse
No, Radium doesn't have it yet. It will be added in the next update
Sent from my Moto G 2014 using Tapatalk
Its a great kernel, thanks! It could be possible to add usb keyboard function? That would make it even better!
Thanks in advance
kurtxcobain said:
Its a great kernel, thanks! It could be possible to add usb keyboard function? That would make it even better!
Thanks in advance
Click to expand...
Click to collapse
Okay I'll look into it
Sent from my Moto G 2014 using XDA-Developers mobile app
Thanks for your hard work.
Maybe you want to add double tap to sleep and double tap to wake feature for the next version.
Aciong.Aksaya said:
Thanks for your hard work.
Maybe you want to add double tap to wake and double tap to wake for the next version.
Click to expand...
Click to collapse
I won't be adding that because it isn't stable, causes battery drain and doesn't work on all devices.
Sent from my Moto G 2014 using XDA-Developers mobile app
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
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.
[UNOFFICIAL] LineageOS-16.0 For Dragon 4.9 kernel.
The system is built on the basis of the 4.9 kernel and drivers from Nvidia Shield TV.
Of the pluses I noticed, Play 2 / 4k video on YouTube and from files.
To install this firmware you need your own version of TWRP. You can download TWRP here.
Android 9.
Known issues:
- There is no LP0 sleep (standby) mode.
- There is no Camera.
- SELinux - permissive !
Works:
- Wi-Fi and BT
- Sound speakers, headphones, via BT.
system-as-root (SAR)
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. Wipe CACHE and DAVLIK
6. Reboot into system
Download ROM Alpha1
Download TWRP
LOS-16 based on kernel 4.9 nvidia Alpha 3.
Changes
-Added sound through headphones.
Installing images from the archive via fastboot or twrp.
Download ROM Alpha3
- The ROM does contain it's own vendor.img !
Links to the sources
kernel 4.9
platform/dtb
Kernel 4.9 drivers
Kernel 4.9 nvgpu
Vendor
Device nvidia dragon
Thanks @webgeek1234 and CM-Shield team, for the source.
Thanks @michie for testing rom.
If someone wants to help finish the sound support in the kernel and the system, write, I will help you how to start the assembly yourself.
Thank you very much.
This is really an important refresh for the software base.
I think that this new kernel can do wonders on our device.
LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM
if sound is working can you make it work on linux with 4.9?
mi_guel said:
if sound is working can you make it work on linux with 4.9?
Click to expand...
Click to collapse
If you mean the mainline kernel, then the answer is no.
If you are about Linux for Tegra at 4.9 then this is possible.
Vartom said:
LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM
Click to expand...
Click to collapse
Good work
Gesendet von meinem Pixel 2 XL mit Tapatalk
Vartom said:
LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM
Click to expand...
Click to collapse
Glad to see most function works!good job!
The recovery here doesn't seem to work.
almightysiman said:
The recovery here doesn't seem to work.
Click to expand...
Click to collapse
What exactly does not work?
Encryption does not work. I checked the firmware installation.
Vartom said:
What exactly does not work?
Encryption does not work. I checked the firmware installation.
Click to expand...
Click to collapse
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.
almightysiman said:
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.
Click to expand...
Click to collapse
Try downloading the recovery again, sounds like it's corrupt. It should work both ways.
michie said:
Try downloading the recovery again, sounds like it's corrupt. It should work both ways.
Click to expand...
Click to collapse
Tried so many time,still no luck,maybe I should keep trying.
Vartom said:
What exactly does not work?
Encryption does not work. I checked the firmware installation.
Click to expand...
Click to collapse
Finally get alpha2 working,one question,Can I flash magisk to root It?
almightysiman said:
Finally get alpha2 working,one question,Can I flash magisk to root It?
Click to expand...
Click to collapse
You can, but magisk will not work. This is a real SaR.
Vartom said:
You can, but magisk will not work. This is a real SaR.
Click to expand...
Click to collapse
So root is not possible at the moment?
almightysiman said:
So root is not possible at the moment?
Click to expand...
Click to collapse
Yes. To be able to get root, I have to make a special version of the firmware.
Vartom said:
Yes. To be able to get root, I have to make a special version of the firmware.
Click to expand...
Click to collapse
Thanks for making such effort!It's truly a good kernel,I already feel much smooth than other rom.
almightysiman said:
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.
Click to expand...
Click to collapse
i used it with fastboot boot command, not flash, worked fine, and the rom it's quite snappy
LOS-16 based on kernel 4.9 nvidia Alpha 3.
Changes
-Added sound through headphones.
Installing images from the archive via fastboot or twrp.
Download ROM
Hello friends, can you please take notice of the following thread for the future of development of our device?
https://forum.xda-developers.com/pix...xel-c-t4123463
Thank you in advance!