Related
Hey!
So I recently bought a Redmi note 3 (SD) Kenzo, and successfully installed the latest official cm13 snapshot, though I am having problems with the rear camera, flash and FP sensor not been recognized/functioning.
(I should note I’ve never rooted, flashed, unlocked boot loader or install custom recovery or anything like this before)
My process was:
Request official permission to unlock, which I received in like 5 mins, then proceeded to successfully unlock with Mi unlock tool.
I then flashed official TWRP 3.0.2-2, but then couldn’t access internal storage due to some encryption thing TWRP was complaining about. I later worked out it was because I was running the latest China Dev MIUI ROM which is marshmallow, and then flashed “cofface_TWRP3_kenzo_p.img”, which worked fine.
I booted up into TWRP just fine, and then proceeded to wipe Dalvik cache, system, data and cache. I then flashed the firmware then latest snapshot build of which is linked here "http://forum.xda-developers.com/redmi-note-3/development/rom-cyanogenmod-13-t3431866". And then flashed open Gapps.
I then booted up which took around 10 minutes or so just fine.
According to Aida64 I have FPC sensor, and looking through root/system/etc/firmware, with no “goodix” to be seen. I don’t know where to look to find info on my rear cam and flash though.
So should I flash “radon kernel” (I don’t entirely know what this will do), did I make a mistake in the process, or something else entirely? Also is my bootloader now locked due to flashing cm13, and can I unlock it again with the Mi unlock tool?
It would be so great if you could help!
(also if more info is needed just let me know)
BukuThatDude said:
I recently bought a Redmi note 3 (SD) Kenzo, and successfully installed the latest official cm13 snapshot, though I am having problems with the rear camera, flash and FP sensor not been recognized/functioning.
Click to expand...
Click to collapse
Bro, you did everything in correct order.
And, to get fp working for you, flash Radon v2.9 and select fpc (or goodix if still doesn't work). Kernel is the sw part which directly interacts with your hw. So, you'll need Kernel Aduitor or any another such app to tweak the kernel settings. AIDA64 should show your cam sensors, afair.
And, if Radon doesn't help then you can flash CM13_RADIOS.zip which you'll find in the "All ROM, Recoveries, add-on zips......." thread.
And, official CM13 doesn't lock your bootloader, the unofficial CM13 from SantoshM does that.
You can unlock your bootloader any no. of times using MiUnlock, and if needed you can check it using the following command in adb and fastboot tool
Code:
fastboot oem device-info
Look for "Bootloader Unlocked - true/false"
As above, flash the latest Radon Kernel. Also do not use the old snapshots of CM13 (they are now months old), nightlies are more stable and much more updated.
sasukay said:
Bro, you did everything in correct order.
And, to get fp working for you, flash Radon v2.9 and select fpc (or goodix if still doesn't work). Kernel is the sw part which directly interacts with your hw. So, you'll need Kernel Aduitor or any another such app to tweak the kernel settings. AIDA64 should show your cam sensors, afair.
And, if Radon doesn't help then you can flash CM13_RADIOS.zip which you'll find in the "All ROM, Recoveries, add-on zips......." thread.
And, official CM13 doesn't lock your bootloader, the unofficial CM13 from SantoshM does that.
You can unlock your bootloader any no. of times using MiUnlock, and if needed you can check it using the following command in adb and fastboot tool
Code:
fastboot oem device-info
Look for "Bootloader Unlocked - true/false"
Click to expand...
Click to collapse
Can the kernel be flashed after the firmware/rom? Will it factory reset the device? If i run into any any issues what part do i wipe and replace in twrp to revert to the previous kernel?
Are you sure you have the Kenzo version?
Maybe you have the Kate version like me
BukuThatDude said:
Can the kernel be flashed after the firmware/rom? Will it factory reset the device? If i run into any any issues what part do i wipe and replace in twrp to revert to the previous kernel?
Click to expand...
Click to collapse
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
sasukay said:
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
Click to expand...
Click to collapse
Thank you, I'll update on how it goes.
sasukay said:
Flashing a kernel is like flashing any add-on zip like bootanimation or some new font and stuff. You don't need to flash the whole ROM or the reqd. firmware.
So, first make a backup of system and boot partition in twrp.
Then, wipe cache and dalvik and then flash the kernel zip. Reboot and done.. First boot may take some time.
And, should you need to revert back to stock, you can restore the backup you made earlier.
Click to expand...
Click to collapse
Yes holy sh*t thank you, both cameras and flash work now, fingerprint doesn't, so i'll try re-flashing it for "goodix" to see if that works.
(also is normal to hear a physical clicking sound next to the flashlight when turned on/off?)
BukuThatDude said:
Yes holy sh*t thank you, both cameras and flash work now, fingerprint doesn't, so i'll try re-flashing it for "goodix" to see if that works.
(also is normal to hear a physical clicking sound next to the flashlight when turned on/off?)
Click to expand...
Click to collapse
Flashing either FPC or goodix radon fingerprint still doesn't work?
BukuThatDude said:
Flashing either FPC or goodix radon fingerprint still doesn't work?
Click to expand...
Click to collapse
Try flashing this
Maybe you have goodix variant. If everything else fails, try goodix patch: https://drive.google.com/file/d/0B3Ji2Mma4WGpaFAweDZNWmVVVms/view
Camera and sensors all work well on MIUI 10 beta 8.11.15 Pie, as well as Lineage OS 16.
But when downgrade to MIUI 9 or 10 Oero via official MiFlashTool(fastboot) , or Lineage OS 15.1 via TWRP, it says "CANNOT connect to camera". What's more, all sensors do not work in CIT mode (of course they do not work in normal situation).
I think flash MIUI Oreo via official MiFlashTool(fastboot) should over-write all files about Pie, Isn't it?
Any ideas to this strange bug?
My poco has the same symptoms.
I installed the B-S-G camera and it did not work well, so I uninstalled it.
Then, I woke up original camera application, "CANNOT connect to camera" happened.
This phenomenon is similar to Pixel 3, but this one is more serious, coz it will not get better after reboot.
I have another twice try to flash MIUI stable 9.6.18 and beta 8.9.13 (both of them are Oero) via FASTBOOT from beta 8.11.15 (Pie), but camera app still says it " cannot connect to camera ", so can't google camera apps.
Did I forget something important? How to Downgrade from Pie to Oreo? Have any one succeeded in downgrading?
I think it's not hardware broken. Please help me. Thanks
succeeded in downgrading. need flash back a persist.img backup from 8.1 (not persist.img from official .tga fastboot package)
kumoilain said:
succeeded in downgrading. need flash back a persist.img backup from 8.1 (not persist.img from official .tga fastboot package)
Click to expand...
Click to collapse
How did you create your persist.img backup?
MikelFuchs said:
How did you create your persist.img backup?
Click to expand...
Click to collapse
ask your friends for a backup, or you can try mine. make a backup before flash my persist.img.
persist and a twrp(cn default and have English)which can flash persist easily:drive.google
kumoilain said:
"CANNOT connect to camera".
Click to expand...
Click to collapse
have you solved it somehow?
because I have the same problem
onairda said:
have you solved it somehow?
because I have the same problem
Click to expand...
Click to collapse
Try flashing persist partition. See my posts on 2018.11.25 and 2018.11.27
kumoilain said:
Try flashing persist partition. See my posts on 2018.11.25 and 2018.11.27
Click to expand...
Click to collapse
I just flashed version 9.6.18.0 from fastboot, then after installing the recovery "recovery-TWRP-3.2.3-1010-POCO_F1-CN-wzsx150.img" I flashed the file pocopersist8.img in the "persist" partition, despite this the cameras do not work and neither do the gyroscope and accelerometer sensors.
However after trying several persist files a few days ago I found one that runs 3 cameras (except the IR) even though it takes about 15 seconds to boot up, and in any case the sensors still don't work, anyway thanks for trying, I had already tried but I said to myself I try one last time.
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
deleted
What version of RR Pie did you test? The May Release?
JDBS30 said:
What version of RR Pie did you test? The May Release?
Click to expand...
Click to collapse
all of them.
this link i used and choose one of them from your choice arm a only of course: https://get.resurrectionremix.com/?dir=gsi
I can't install Resurrection Remix
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
elfennani said:
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
Click to expand...
Click to collapse
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
rudi021 said:
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
Click to expand...
Click to collapse
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
elfennani said:
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
Click to expand...
Click to collapse
like i wrote your device must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
rudi021 said:
like i wrote you must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
Click to expand...
Click to collapse
How did you downgrade your firmware?
elfennani said:
How did you downgrade your firmware?
Click to expand...
Click to collapse
i found oreo firmware. if you want you can download from my google drive. here is link: https://drive.google.com/file/d/1KnqHZ8_EVTstJP5AMsMy_8Uc1QV-vMHe/view?usp=sharing
Please help
rudi021 said:
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
Click to expand...
Click to collapse
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Maxmiliano Coelho said:
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Click to expand...
Click to collapse
my dear friend just ask i will help you. this patched boot.img is made by ashyx. i will be bad member if i share his works without permissions.so i share with you his link. here is link for oreo patched boot.img https://androidfilehost.com/?fid=1395089523397921797
please follow instructions carefully. read twice and try to understand.enjoy.if you have any doubt please ask. thank you.
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
why not.i am not star just ask and if i can help i will please to do that.you can always send me personal message(PM) on xda
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
rudi021 said:
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
Click to expand...
Click to collapse
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Maxmiliano Coelho said:
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Click to expand...
Click to collapse
once you perform flashing gsi,no need repeat every time this steps,just (at least i do like that) format data,reboot to recovery,flash gsi(as system.image) and flash magisk then mount system and reboot.about audio volume install viper fx audio apk(Magisk module),and then fix volume as your own.
kapmino269 said:
If anyone faced problems with booting some roms on
ROM LOGO NOT SAMSUNG .
use this :
https://www.androidfilehost.com/?fid=6006931924117925309
Tested on j415f
RR
AOSP
DESCENDANT ZERO .
Click to expand...
Click to collapse
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
rudi021 said:
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
Click to expand...
Click to collapse
me i have not a network on aex extended but on dot os i have
Envoyé de mon Phh-Treble vanilla en utilisant Tapatalk
kapmino269 said:
Guys , sorry I found error in my script and I fixed it I tested it on AEX official , I will test it in others then post it .
@rudi021
---------- Post added at 09:15 AM ---------- Previous post was at 08:29 AM ----------
v2 : https://www.androidfilehost.com/?fid=6006931924117930007
tested : work with rom logo bootloop 100%
Click to expand...
Click to collapse
thank you bro. i definetly try this on pie upgrade and inform you.thank you for your hard work. i am on vacation and when i come home i will try this.thank you and greetings from Croatia.:good:
also i stop build gsi roms for j4+ because my pc is old so i need little upgrade of same( RAM(have only 4 gb,need for pie at least 8 gb ,my motherboard can have 32 gb,), my processor is i3 but i will upgrade on i5 and after that i will continue work on it. but now i am on vacation with my wife and children and when i come hom ei will continue to work it.thank you once more.
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?
Loaded twrp with odin, then loaded aicp custom rom.
A year later loaded pixel pie custom rom
On power off the fone wouldn't restart in pixel, or twrp
I tried taking the Battery out and waiting 5 mis, 1hr, 3 hrs the fone still wont start.
BUT if the fone is left with the battery out for 3days it starts in both pixel and twrp no problem !!!
I also tried cleaning all partitions on twrp except sd card and loading my image of aicp which used to work, .. no change.
Anyone have an idea what this might be?
The phone is a samsung note 4 snapdragon originally on marshmallow android.
Im thinking of asking samsung to put marshmallow on again then reloading twrp and aicp
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
ze7zez said:
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
Click to expand...
Click to collapse
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
If you are installing a new/different custom rom, it's best to do a full wipe with internal memory included.
For many phone models, twrp 3.6.x performs worse than 3.5.2.x.
Since the twrp kernel is good for shutting down the phone, change the ROM to one that also shuts down the phone well.
Read the first post of the thread very carefully and understandingly:
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS...
forum.xda-developers.com
and install LineageOS 18.1 by @ripee.
gwm121 said:
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
Click to expand...
Click to collapse
Thankyou ze for succinct helpful info.
I am reading very carefully as you suggest
In this section im unsure about ..........."type fastboot reboot" ...
Recovery is to get to twrp right? vol up pwr home with note 4, that would bring up menus on twrp, .there is a menu box for reboot.. Have I undersood this please?
I can follow ypour suggestion tomload an earlier version of twrp
is it possible a later twrp has anything to do with the loading kernal of the rom
"""Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."""