So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.
Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!
First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs
Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]
Related
Hey guys,
I'm new to the Xperia Arc development and need some help with installing a custom rom. I've done quite a bit of reading but still can't figure out what is wrong and why it's simply not working.
So from what I gathered the steps to ensure a successful flash are:
Firstly flash a stock rom via flashtool ie LT18i_4.1.B.0.587.ftf
flash LT18i_4.1.A.0.562_Kernel > root the device > flash back to LT15a_4.1.B.0.587_Kernel
Then now that the device is rooted, I need to install a recovery such as CWM via RecoverX
So, so far so good as I can access CWM, stock rom works fine as well
So then next step is to unlock the bootloader
pretty sure this worked, as when i tried to unlock it again, it said it failed as it was already unlocked
Now flash a custom kernel, in this case i flashed the 146 FXP CM kernel
This also seemed successful as I was presented with a custom splash screen
So then after custom kernel is installed I enter recovery, wipe the cache and reset factory settings, format the data system and cache as well as wiping the dalvik and battery stats.
After, I installed the custom rom zip file, in this case it was aokp_anzu-ota-eng.kxp_build5 and then google apps and then reboot.
So my problems begin here.
My phone seems to be stuck in the boot process (sometimes), on the "initiating swagger" splash screen and it goes crazy. I've tried flashing this rom with other kernels (fusion 3.9) and sometimes it actually loads up into the rom. But the rom is extremely laggy, applications freeze and close and the wifi never works
So my question is, is there any steps or procedures that I am missing, not doing right or in the correct order?
I don't think it's any hardware issues as wifi works in the stock rom, and it's fairly smooth and fluid.
Also, is there a better way to flash roms so that I don't need to do this entire process of flashing a stock rom, rooting, unlocking bootloader, installing recovery every time I want to flash a new rom? And when I flash a custom kernel first, then flash a custom rom that has a kernel inbuilt (cm10) does the custom rom's kernel replace the one i just flashed, reason for asking is that the instructions say to flash the custom kernels and then the roms, but yeh just hasn't been working for me so not really sure how to do what.
I'd really appreciated any help or insight!
Thanks
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
XperienceD said:
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
Click to expand...
Click to collapse
Thanks! I've read your guide (what I based my flashing on) and it seems consistent with what I have done, on the surface of it anyway. If you think I missed or overlooked something, would it be possible to point it out?
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
XperienceD said:
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
Click to expand...
Click to collapse
As ExpirienceD says,just one more thing flash kernel modules if you need to.
So:
1.Flash kernel
2.Full wipe data/cach...etc...
3.Flash ROM
4.Flash kernel modules
Sent from my LT15i using xda premium
Hello guys, I've searched a little and didn't find any posts that could help me specifically for the Galaxy Nexus.
I've flashed my phone a long time ago and have been using Paranoid Android for probably over a year.
The problem is, my cellphone was really really slow. So I decided to try a new ROM and re-flash it. And So I did.
I've tried flashing this Full_Auto R11 kernel then the CyanogenMod 12 and finally GAPPS.
I was getting error status 6 on Clockwork mod on gapps, but eventually got around it. But it didn't install play store, I've tried manually adding but it didn't work.
So I went for another 5.0 ROM (I'm really interested in getting android 5.0). Wiped all the data, all the cache, installed everything and rebooted.
Bam! Infinite booting screen.
No, I didn't create a nandroid backup because I'm really dumb.
So, I need your help. What I want to do is to get my phone working again with a 5.0 ROM (if possible).
I can boot into ClockWork Recovery just fine, if that helps.
Thank you for the attention.
I would recommend to install latest full factory package from Google.
Then you will start with everything stock, so flash latest TWRP recovery via fastboot (CWM is no longer supported, so error 6 when installing new Lollipop Google Apps appears).
Then in TWRP, do a factory reset, wipe /cache and /system partitions.
Then you can install your Lollipop ROM (over ADB or by pushing ROM package to emulated sdcard).
After this, install latest Full_Auto kernel.
At the end, install Pico Google Apps.
You must install the Pico version, because our /system parition is too small to handle Lollipop with all Google Apps included.
This should work for you, and you will have fully working Lollipop on your Galaxy Nexus
P.S: If you intall the AOSP Lollipop ROM by @freshgiammi and you miss root access, install latest SuperSU flashable zip.
Thank you!
Thank you man!
I've ran into some troubles but managed to do everythings correctly =)
This post can be locked up now.
Thanks again for the reply, LamarrCZ!!
Hi, after trying to use philz recovery to flash a ROM on to my device I got what I think was called a soft brick where I had to download and flash the stock ROM.
My device (GT-N7100) is now not rooted again and back to square one. Any problems I come across occur from using old tutorials with dead links so if someone could recommend a tutorial to install a custom rom like 5.1 I would be very grateful. Thanks
EDIT. I found this guide on youtube http://mytechtube.in/samsung-galaxy-note2-rooting.html + http://mytechtube.in/samsung-galaxy-note2-6-0-1.html . Does it look like it will work?
Flash twrp using Odin, then flash a custom rom via twrp.
Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk
Root is not required to flash TWRP. TWRP can be flashed directly to the phone using Odin.
1life2love4 said:
Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
audit13 said:
Flash twrp using Odin, then flash a custom rom via twrp.
Click to expand...
Click to collapse
Should I just use the latest version of TWRP direct from their website https://twrp.me/devices/samsunggalaxynote2n7100.html ?
I think my phone code name is t03g how can i confirm?
Thanks
EDIT. Just installed TWRP :good: now on to picking a good ROM. will have a look at the ressurection one too.
To install apps that require root should O root it now or do some ROMS root it for me?
Sorry for the amount of questions
The easiest way to install twrp would be to flash the tar version using Odin.
audit13 said:
The easiest way to install twrp would be to flash the tar version using Odin.
Click to expand...
Click to collapse
Just did as you suggested thanks. To install apps that require root should I root it now or do some ROMS root it for me?
Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.
audit13 said:
Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.
Click to expand...
Click to collapse
Thanks for the info. I've watched some videos of cm13 and I so far thats what im going with. Will look for a youtube video to help with installing it.
To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.
audit13 said:
To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.
Click to expand...
Click to collapse
I didnt realise that before. Could I for example install any of the GAPPS from this link https://devs-lab.com/android-gapps-download.html " full google apps" or pico google apps ?
From whatI gather GAPPS are installed straight after rom install before root though is this the same in cm13?
Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/
audit13 said:
Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/
Click to expand...
Click to collapse
Perfect Im going to try that in the next hour. I like the look of aroma. For platform would I select ARM and android 6.0?
EDIT. Found the answer it was ARM.
Arm as I believe your phone has a Qualcomm processor.
audit13 said:
Arm as I believe your phone has a Qualcomm processor.
Click to expand...
Click to collapse
Yeah was ARM as I just installed CM13. Thank you seriously headig your way.
Hopefully, everything works.
Now that you have twrp on your phone, you can use it to create a backup of everything in your phone, including time efs folder. Save the efs folder in a safe place in case you need to restore it to the phone at a later date.
After making a backup, you can flash other Roms and you can return to cm13 by restoring your backup.
Just getting familiar with it. Thanks for the help.
Do you know if there's settings to turn screen on during during calls because it works with the front sensor and that sensor is broke on my phone?
Sent from my GT-N7100 using Tapatalk
You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.
Got it sorted using an app from the play store.
Sent from my GT-N7100 using Tapatalk
audit13 said:
You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.
Click to expand...
Click to collapse
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the rom and reinstalling the custom rom like I did the first time.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop.
Any suggestions on how i could get it running again? Thanks!
I have been working on the sister models also. I saw no one was building these anymore so here it is I hope it can be enjoyed by all. Spread the word. provide feedback so other fans of this ROM may obtain it and work out any bugs if there are any. I will update once or twice a week depending on time and demand. I'm compiling for three different variants. Hit the thanks button and Enjoy. Dirty flash the updates not the initial flash of this rom but the updates to it. Initial install = Factory reset, wipe data and cache, install rom zip, install gapps zip, install su zip, reboot system. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
4-10-18
https://www.androidfilehost.com/?fid=890129502657597436
4-13-18
https://www.androidfilehost.com/?fid=818070582850507491
4-17-18
https://www.androidfilehost.com/?fid=818070582850508419
4-24-18
https://www.androidfilehost.com/?fid=673956719939836620 If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app
5-4-18
https://www.androidfilehost.com/?fid=818222786056028546
Root is not baked in. Flash and root your preferable way.
5-20-18
https://www.androidfilehost.com/?fid=674106145207488021
5-31-18
https://www.androidfilehost.com/?fid=674106145207490572
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060741
9-3-18
https://www.androidfilehost.com/?fid=1322778262903996744
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022369
12-7-18
https://www.androidfilehost.com/?fid=11410963190603868411
12-16-18
https://www.androidfilehost.com/?fid=11410963190603876081
2-25-19
https://www.androidfilehost.com/?fid=1395089523397901582
3-24-19
https://www.androidfilehost.com/?fid=1395089523397924752
5-6-19
http://download1589.mediafire.com/7...q5/lineage-14.1-20190507-UNOFFICIAL-d2tmo.zip
10-13-19
https://www.androidfilehost.com/?fid=1899786940962607809
i recommend clean flash as i built with different computer
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.
thanks bro... but is it rooted rom or use any method to root it ?
hasan.sy said:
thanks bro... but is it rooted rom or use any method to root it ?
Click to expand...
Click to collapse
I use SuperSU zip
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
I appreciate the feedback and no worries mate I'm still trying to get the no sim bug worked out in the att variant no luck so far sprint variant is doing good also
Update posted 4-17-18
It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.
Sammay_Boiii said:
It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.
Click to expand...
Click to collapse
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding
Joker1716 said:
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding
Click to expand...
Click to collapse
Thank you for your rapid response! I will try that as soon as I get to my house and I'll let you know what happens
After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?
Sammay_Boiii said:
After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?
Click to expand...
Click to collapse
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
This should help
https://forum.xda-developers.com/showthread.php?t=1949687
Joker1716 said:
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
Click to expand...
Click to collapse
I will do that. Your rom needs to be flashed over stock rom?
Sammay_Boiii said:
I will do that. Your rom needs to be flashed over stock rom?
Click to expand...
Click to collapse
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?
Joker1716 said:
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?
Click to expand...
Click to collapse
What you said makes a lot of sense actually. Im used to just flashing back ups of other roms that I forgot how to flash fresh ones. I'm not used to this haha but I got it now. Stock rom 4.3 has been flashed via odin and the root method is currently on my screen.
hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3
Sammay_Boiii said:
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3
Click to expand...
Click to collapse
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher
hasan.sy said:
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher
Click to expand...
Click to collapse
Thank you. Ive been flashing this rom repeatedly and always received a "Process system not responding" then it falls into a boot loop
Update posted
Joker1716 said:
Update posted
Click to expand...
Click to collapse
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)
hasan.sy said:
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)
Click to expand...
Click to collapse
If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app
Hi all XDA community.
So I have run into a snag and I'm not getting any joy with what I have tried so far.
Procedure followed to this point:
1 wipe phone stock Samsung TW 5.0.1
2 CF Auto root install using Odin 3.12.x
3 reboot device
4 install TWRP 3.1.1.0 with Odin
5 reboot to recovery. Reboot device, all good.
6 reboot to recovery mount MTP, copy ROM to SD card.
7 install RR-N 5.8.5 20171215 Final.zip and NvmX RR-N v10.6. ROM and kernel.
8 wipe phone and reboot.
This is now where the problem comes in, the phone is stuck in a boot loop, sometimes getting further than other times, but never completing first start.
What I've tried a few times is to recopy the ROM to the SD card, re-install. Nope still the same. I tried another ROM. Same. Haven't tried another kernel though.
My next thought is to flash back to stock and try again, just that it's a big download and takes quite long.
Any other thoughts on where I've gone wrong and how I can fix it from you guys would be most appreciated.
TIA
345/5000
very weird you should start with the kernel that brings the rom to flash the nevermorex then I use RR N and is totally stable with gt i9500 the only thing is that when I connect to the pc I do not recognize the device at all if someone in this community helps me to solve that would be very helpful
have the test with the kernel that brings the rom to see
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
NEW UPDATE IS HERE
As some of you might've noticed, the new update for RR s4 has rolled out few days ago but because the links in the first post at XDA thread haven't been updated yet, most of you forgot about it or even haven't realized!
And according to kongacute, it includes Bluetooth fix
Here is the link:
https://androidfilehost.com/?fid=746163614322263530
missioner said:
Hi all XDA community.
So I have run into a snag and I'm not getting any joy with what I have tried so far.
Procedure followed to this point:
...............
7 install RR-N 5.8.5 20171215 Final.zip and NvmX RR-N v10.6. ROM and kernel.
Click to expand...
Click to collapse
install cust rom + gapps, wipe cache dalvik, reboot.
if all good try install cust kernel.
if bootloop, extract boot.img in cust rom then flash via twrp.
try another cust kernel or version.
hope this help
Sent from my Lenovo A3500-HV using XDA-Developers Legacy app
Thanks I will try this tonight
Ertocell said:
install cust rom + gapps, wipe cache dalvik, reboot.
if all good try install cust kernel.
if bootloop, extract boot.img in cust rom then flash via twrp.
try another cust kernel or version.
hope this help
Sent from my Lenovo A3500-HV using XDA-Developers Legacy app
Click to expand...
Click to collapse
So sadly the recommended method has not yielded success.
The phone is still bootlooped.
So back to OEM ROM and try again.
Thanks again for all the help.
Flashed OEM ROM courtesy of sammobile.
Re-Rooted
Installed TWRP
Flashed RR clean install.
Success!!!!
Test for 24 hours
Flash Gapps pico.
Battery consumption issue now after Gapps install,
Any ideas?
missioner said:
Thanks again for all the help.
Flashed OEM ROM courtesy of sammobile.
Re-Rooted
Installed TWRP
Flashed RR clean install.
Success!!!!
Test for 24 hours
Flash Gapps pico.
Battery consumption issue now after Gapps install,
Any ideas?
Click to expand...
Click to collapse
Wait for a few days or a week. You can't judge it by only a day usage. The phone needs to optimize with the newly installed system.
After some more testing I think the charging socket is not very happy, I think it isnt helping the battery issue.
I will look into it when I have time this weekend. It may be time for a new connector though.