It seems I can not flash the Miui beta with the RIL working for the Nexus 5 through twrp recovery. Is there a way to fix this?
Also. I currently have PA's latest build. How do I change the trigger area for PIE? I see in screenshots they are on the side. How can I do this? I hate swiping from the bottom since I'm used to doing that to launch Google.
Thanks in advance.
Sent from my Nexus 5 using XDA-FORUM, powered by appyet.com
ImHereToSaveTheDay said:
It seems I can not flash the Miui beta with the RIL working for the Nexus 5 through twrp recovery. Is there a way to fix this?
Also. I currently have PA's latest build. How do I change the trigger area for PIE? I see in screenshots they are on the side. How can I do this? I hate swiping from the bottom since I'm used to doing that to launch Google.
Thanks in advance.
Sent from my Nexus 5 using XDA-FORUM, powered by appyet.com
Click to expand...
Click to collapse
I got an error the first time I tried to flash the MIUI port in TWRP. Try rebooting the recovery after the error and flashing again. That worked for me.
As for PIE in PA, I don't know as I haven't used it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ImHereToSaveTheDay said:
It seems I can not flash the Miui beta with the RIL working for the Nexus 5 through twrp recovery. Is there a way to fix this?
Click to expand...
Click to collapse
Why about adding the error message? You may need to upgrade your bootloader.
Related
Here are the flashable JB kernels.
18 June: http://www.sendspace.com/file/rakaiw / http://www.multiupload.co.uk/RQU9DR43AM
28 June: http://www.sendspace.com/file/vf5g8l / http://www.multiupload.co.uk/XCFQRUKUOH
Credit to those involved
Thanks
Sent from my Nexus 7 using xda premium
x.Orville.x said:
Thanks
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
No problem!
Sent from my Nexus 7 using xda app-developers app
I flashed the June 28 kernel & it bricked my N7. I'm unable to get back into recovery mode to flash a backup. Any advise?
Mayze23 said:
I flashed the June 28 kernel & it bricked my N7. I'm unable to get back into recovery mode to flash a backup. Any advise?
Click to expand...
Click to collapse
Plug your Nexus 7 into a computer and then press the power and both volume buttons at the same time. Then you can boot into recovery.
Sent from my Nexus 7 using Tapatalk 2
veeman said:
Plug your Nexus 7 into a computer and then press the power and both volume buttons at the same time. Then you can boot into recovery.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I tried that. I can get into fastboot no problem. I'm running pre released windows 8. Could that be the problem as to why I can't get into recovery?
Sent from my SCH-I535 using Tapatalk 2
Mayze23 said:
I tried that. I can get into fastboot no problem. I'm running pre released windows 8. Could that be the problem as to why I can't get into recovery?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's not a problem of the op kernel or win8 but know issue that some Nexus 7 unmount recovery. There's a specific thread for solve this....but in my case don't work
Inviato dal mio Galaxy Nexus con Tapatalk 2
I also had an issue with the 28 June kernal. Wouldn't go past boot screen or load into recovery. Could still access fastboot though.
/remember that nandroids are your friends
I was able to boot into recovery using the N7 toolkit. The problem then was I had to use the toolkit to force it to boot into android. I tried flashing Trinity's and Franco's kernel but it would not flash via TWRP or CWM.
Ended up having to flash the stock image to get my tablet working right. As per another post having a similar issue I would stay away from the June 28 kernel.
The older kernel also put my Nexus in a bootloop
Ah well better reflash
So does any of these kernels work or only put the n7 in boot loop? BTW what's the difference between the two?
Sent from my Nexus 7 using xda app-developers app
ones newer than the other, by the looks of it both bootloop the device :/
really regretting not backing up before doing it
edit: I reflashed the boot.img (extracted it from my ROM) and all is good now. Gonna do a titanium backup just to make sure incase it's unstable
Wow I really wish I had read this thread before flashing. Just bricked my device
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
What steps are you taking when you flash a ROM?
Sent from my Nexus 5 using xda app-developers app
freddienux74 said:
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
Click to expand...
Click to collapse
Are you wiping data when you flash the rom?
If you don't have any important stuff on your phone, I would just flash the factory images and start over with the rom process.
freddienux74 said:
after i flash a rom and when i get to setup menu it says unfortanately phone has stopped!! doesnt matter which rom i flash it says the same thing!! tried with omni rom official beanstalk rom and bs harmony rom!! please help thx in advance
Click to expand...
Click to collapse
Please tell us also what is your phone's status at the moment. Like is your phone rooted with bootloader unlocked and stuff like that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bruce Lee said:
Please tell us also what is your phone's status at the moment. Like is your phone rooted with bootloader unlocked and stuff like that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well since he's flashing a rom, it would be rooted and the bootloader unlocked.
aooga said:
Well since he's flashing a rom, it would be rooted and the bootloader unlocked.
Click to expand...
Click to collapse
It never hurts to ask though. Maybe he did something different and bypassed something. You never know. You got to have the whole story. :sly:
Sent from my Nexus 5 using XDA Premium 4 mobile app
Kreateablaze said:
What steps are you taking when you flash a ROM?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I did full wipe then dalvik cache
Sent from my Nexus 5 using Tapatalk
I'm rooted! When I flashed Mahdi ROM no issues! Mahdi ROM actually is my backup ROM also
Sent from my Nexus 5 using Tapatalk
freddienux74 said:
I'm rooted! When I flashed Mahdi ROM no issues! Mahdi ROM actually is my backup ROM also
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wait it's working now?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bruce Lee said:
Wait it's working now? No its not working! Mahdi ROM is my daily driver and my backup! I'm thinking now it might be kernel issue. Do you think the kernel might be issue?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No its not working now! I meant my daily driver is Mahdi ROM and I use
Sent from my Nexus 5 using Tapatalk
When you flash the ROM it also flashes the kernel that comes with it.
So if you are using Mahdi ROM then everything is ok but if you try a different ROM you get the error constantly?
using the ClockworkMod recovery.
If you receive issues on flashing, double check your download. If nothing, I suggest using the ClockworkMod recovery.
mistahseller said:
When you flash the ROM it also flashes the kernel that comes with it.
So if you are using Mahdi ROM then everything is ok but if you try a different ROM you get the error constantly?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 5 using Tapatalk
storm007 said:
If you receive issues on flashing, double check your download. If nothing, I suggest using the ClockworkMod recovery.
Click to expand...
Click to collapse
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
freddienux74 said:
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Phone has stopped is related to your gapps
freddienux74 said:
I switch to cwm and same issue! Its weird! I mean again today I flash 4 different ROMs and as soon as I get to setup same issue! Unfortunately phone has stopped!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The type of recovery you use will have no bearing on it, hundreds of people on here use twrp and cwm.
All I can suggest and it was suggested before is to wipe your phone completely and start over again. Something went wrong, clearly.
Hi,
I am having trouble updating my Nexus 5 to the latest version. I get the notification to update and it begins to run however, after about 20% it errors and all I can see is the little android error icon. Has anyone else encountered this?
Have you made any changes to the ROM prior to trying to update?
EddyOS said:
Have you made any changes to the ROM prior to trying to update?
Click to expand...
Click to collapse
No It is running the stock version with no dodgy apps installed at all.
Strange. Maybe the update file is corrupted.
Gesendet von meinem Nexus 5 mit Tapatalk
Can you check the build number?
Settings/About phone
Sent from my Nexus 5 using xda app-developers app
bitdomo said:
Can you check the build number?
Settings/About phone
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yeah it is Build number KRT16M
Has anyone got an answer or is there an issue with the device and I need to replace it? it's currently running 4.4 and is trying to install 4.4.2... Could it be an issue with it trying to bypass the 4.4.1 update? I have even done a factory re set and it still errors when trying to install the update.
You could just download the 4.4.2 factory image and manually flash it (leaving out the userdata.img so you don't reset everything) you'll be fine
EddyOS said:
You could just download the 4.4.2 factory image and manually flash it (leaving out the userdata.img so you don't reset everything) you'll be fine
Click to expand...
Click to collapse
Thanks but I have no experience of doing this at all. Complete amateur
Ashton9000 said:
Thanks but I have no experience of doing this at all. Complete amateur
Click to expand...
Click to collapse
Check out the OTA Help Desk.
https://github.com/TeamApexQ/apexq/issues/40
it seems to be an ongoing issue which defenitely prevents me from moving to cynogen mod.
emaayan said:
https://github.com/TeamApexQ/apexq/issues/40
it seems to be an ongoing issue which defenitely prevents me from moving to cynogen mod.
Click to expand...
Click to collapse
This has been resolved in CyanogenMod 11.
So I have to wait til cm 11 becomes available for relay?
Sent from my SGH-T699 using Tapatalk
emaayan said:
So I have to wait til cm 11 becomes available for relay?
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
It is available. Nightlies are being built every day. I believe the fix has also been rolled into the CM 10.2 codebase, and will hit in the next stable release. Though @Nardholio will have to confirm that.
Nightlies aren't stable question has it bee introduced to 10.2 stable release from December
Sent from my SGH-T699 using Tapatalk
See my previous post. It will come in the next stable 10.2 release.
Oh sorry my bad,the original rom is driving me insane
Sent from my SGH-T699 using Tapatalk
emaayan said:
Oh sorry my bad,the original rom is driving me insane
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I believe it!
Also, CM 11 M2 is available for the Relay now. The nightlies are generally quite stable, we're actually well upon our way toward a release.
No
Sent from my SGH-T699 using Tapatalk
Okay then, emaayan. Go with CM-11.0 M2. It's a superiour product to CM 10.2.0 in every way anyway.
well i'm getting an error in cwm install
Magamo said:
Okay then, emaayan. Go with CM-11.0 M2. It's a superiour product to CM 10.2.0 in every way anyway.
Click to expand...
Click to collapse
it's: set_metadata_recursive: some changes failed error in cm-11-20-140104-snapthot-m2-apexqtmo.zip status 7.
emaayan said:
it's: set_metadata_recursive: some changes failed error in cm-11-20-140104-snapthot-m2-apexqtmo.zip status 7.
Click to expand...
Click to collapse
Which recovery are you using? Are you using the one linked to in the installation directions on the Wiki? If not, do so. It should work.
I'm using 6.0.2.8 but could it Because I'm already rooted?
Sent from my SGH-T699 using Tapatalk
emaayan said:
I'm using 6.0.2.8 but could it Because I'm already rooted?
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
That recovery is far too old. Use the one linked in the CyanogenMod wiki for the apexqtmo. It's also the one linked in the CM-11 preview thread here.
http://forum.xda-developers.com/showpost.php?p=47498087&postcount=1
well i tried, that (well i tried the zip recovery) i have no idea how to use heimdail recovery.img, but as others reported, this recovery doesn't get booted into .
but,is this till true?
http://forum.xda-developers.com/showpost.php?p=47665833&postcount=34
i tried updating the recovery...
well i tried, that (well i tried the zip recovery) i have no idea how to use heimdail recovery.img, but as others reported, this recovery doesn't get booted into .
but,is this till true?
http://forum.xda-developers.com/showpost.php?p=47665833&postcount=34
update;
i finally manged to install a cwm (6.0.3.7) that not only can be booted into, but also installs cm 11 , i HIGHLY recommend you modify the OP to include (or at least add) this link:
http://forum.xda-developers.com/showpost.php?p=48217566&postcount=162
emaayan said:
well i tried, that (well i tried the zip recovery) i have no idea how to use heimdail recovery.img, but as others reported, this recovery doesn't get booted into .
but,is this till true?
http://forum.xda-developers.com/showpost.php?p=47665833&postcount=34
update;
i finally manged to install a cwm (6.0.3.7) that not only can be booted into, but also installs cm 11 , i HIGHLY recommend you modify the OP to include (or at least add) this link:
http://forum.xda-developers.com/showpost.php?p=48217566&postcount=162
Click to expand...
Click to collapse
The recovery I posted is the only recovery image that TeamApexQ supports. I also posted a recovery zip later in the thread that I can assure you works as well. Any other recoveries that you can get to work, excellent, but we are not supporting it. The OP will not be changed. As for the question of BTC, as I already stated, we've fixed it in CM-11. We found new firmware that works with it and the Relay.
Hi everyone,
I have a Nexus 5 working under lollipop 5.0.1 ( not rooted )and, just like the 5.0.0, my phone bug a little bit after working a lot on the phone.
The Ram turns to + 70% of consummption and the phone bugs whenever I try to get to the home screen until I restart the phone ( almost everyday )
I use Cleaner to clean my phone.
I thought about going a full reset to the phone and try if this problem will be fixed ( I'll need ur suggestions for the best app backup )
If it doesn't work, I'll try to root my phone ( my last option )
So what you think guys ??!
PS : I can upload a video showing the issue I have if necessary.
Thanks.
Is this a joke? Your talking about the most famous Android 5.0 bug
..
californicated said:
Is this a joke? Your talking about the most famous Android 5.0 bug
Click to expand...
Click to collapse
I thought the 5.0.1 fixed the bug ..
Anyone ?
Try one of the AOSP 5.0.2 ROMs which has the fix. Optipop is pretty good. Cataclysm is good but it doesn't have the fixes in AOSP last I checked.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Try one of the AOSP 5.0.2 ROMs which has the fix. Optipop is pretty good. Cataclysm is good but it doesn't have the fixes in AOSP last I checked.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So Rooting the device is the only option i have ?
What about Treminus Rom (Android 5.0.2 Lollipop) ?
Up
KarimKh said:
Up
Click to expand...
Click to collapse
You don't have to root to have a custom rom. You just need a custom recovery
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have to root to have a custom rom. You just need a custom recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So i can install a custom room without rooting my device .. will it fix the bugs ?
KarimKh said:
So i can install a custom room without rooting my device .. will it fix the bugs ?
Click to expand...
Click to collapse
Is your bootloader unlocked? If it is flash twrp with fastboot. Then flash the rom of your choice and see if it fixes your bug
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? If it is flash twrp with fastboot. Then flash the rom of your choice and see if it fixes your bug
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try that, Thanks.
Alternatively you can also reboot your phone as a temporary fix.