No GPS-lock after Radio-flash - Nexus 5 Q&A, Help & Troubleshooting

Hello,
I was running the LMY48B-radio, then was flashing the KTU84Q-Radio because I've read that the GPS performs better, the .zip file had no .img file to flash, so I went ahead & just flashed the KTU84Q radio via recovery, now I'm experiencing very weak GPS signal and no lock.
I've tried to re-flash the LMY48B radio, didn't fix it.. I think I've maybe done something wrong, so I'm gonna write down the steps of how I flashed it:
1) Bootloader mode
2) flash radio.img via fastboot
3) reboot bootloader
4) boot into recovery
5) flash radio.zip
6) reboot
Is there anything I've forgot? Or didn't do properly?
I'm running Cataclysm ROM/LP 5.1.1 (Stable release, 20th June 2015) and ElementalX kernel.

Related

[Q] Flashed boot.img in Fastboot, works - flashed in TWRP, does not work

Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks
You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.

Ota flash not working

I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
I've come across this today (my OPO was rooted and I had TWRP installed), I was able to install the OTA via returning the OPO back to an unrooted stock build. You can easily do this via getting the 'Fastboot' zipped version of your current .....1NO build.
Once you have this, you only need to fastboot flash the following: - boot.img, recovery.img and system.img
After flashing just these three images, yes you'll loose root but you'll be able to OTA update to the ......2QL build via the normal phone method - hten if you want, you could then reflash a TWRP recovery and re-install a supersu.zip
One thing I forgot to add, which maybe helpful to others as it took me a moment to realise, both boot.img and recovery.img flash without issue, but due to it's size to flash the large system.img you'll probably need to brake it down into flashable chunks, notice the change in fastboot commands: -
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot -S 512M flash system system.img​
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
OTAs can only be flashed through stock recovery..applicable to all devices
Hello,
on the same subject, I am looking for explanations on how to create twrp flashable files for ota updates. Do you know where I could find any resources?
Thx
I had the same issue while installing the incremental update (I got root and TWRP); I solved it simply installing the signed zip of ...2QL version which was pulled out yesterday afternoon. My only concern was about root that could be wipe away with the new installation, so I directly installed SuperSU via zip. Everything works fine till now
Sent from my A0001

[SOLVED] TWRP 3.0.2 bootloop

Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...

flash back to the factory/Stock rom..unable to flash TWRP or boot into TWRP anymore :

flash back to the factory/Stock rom..unable to flash TWRP or boot into TWRP anymore :
- I ran the flash-all.bat and basically wipe the entire phone..
- after that, I used Nexus Root Toolkit v2.1.9 and tried to root + flash custom recovery..
the first time it didn't go thru.
the second time, it was able to boot into TWRP,, then after rebooting the phone, (the toolkit automated steps..)
i couldn't find the SuperSU under Settings :/
also, TWRP recovery mode doesn't work too.
when I boot into the recovery mode, it basically just a broken green android laying there :/
(My main goal is to uninstall the bloatware it came with the Stock rom..)
any ideas on how can I get this fixed ?
here is the link to the stock rom:
https://developers.google.com/android/images
I was able to follow the instruction and used flash-all.bat to flash my Nexus 5 back to the latested Stock Image.. 6.0.1 (M4B30Z, Dec 2016)
hi..
same like me..but you can try to click on top options>custom recovery>tick utilize an alternate custom recovery image and browser your recovery.img...and my nexus 5 was successful install twrp and root via nexus root tool v2.19..
The broken green Android on his back means that stock recovery could be on the phone.
Did yo try manually flashing TWRP using fast boot commands ?

Nokia 6.2 TA-1198 Stock Boot.Img

Please, I followed this post [https://forum.xda-developers.com/nokia-6-2/development/unofficial-twrp-3-3-1-0-team-win-t3999433] and flashed the TWRP.Img file from fastboot instead of booting it. Now, my WIFI is no longer working and I have been told that flashing the Stock boot.img will fix it. I do not know where to get it from. Please, Can someone share it or point me to a link where I can download it.
On which securitylevel are you?
I would also need this / a complete stock rom
I'm at Patch level December 5 and my A slot works fine / is stock, but I cannot get my B slot to work.
Now updates are broken and I do not have root.
If your phone boots fine, everything seems to be ok.
The inactive slot contains the previous Patchlevel boot.img. It can not boot, as I know, the current Patchlevel system.
Dd your working stock boot.img and patch it with Magisk Manager. Then try to boot with it.
HTML:
fastboot boot patched_boot_a.img
If it boots and you got root everything is fine and you can flash it.
Ota check's the state of your partitions like system.
If you ever mounted it rw (like Adaway does) it fails the hash test and blocks ota.

Categories

Resources