May have messed up .....
Stock N5 unrooted and locked.
Was on 5.01 and did a simple factory reset. This ended up with "erasing" hanging for several hours.
Managed to get to fastboot. Any attempt to reboot ended up hanging on "erasing".
Managed to unlock the phone through adb.
Think I managed to install TWRP - it worked once and booted the phone up perfectly (note i still hadnt rooted at this point).
Today, random reboot and it spends ages on the Google wording before going into a boot look with the swirling colours playing.
Got home, put it back into fastboot and (think) managed to root using a one-click tool. TWRP no longer appears and I seem to have stock recovery that I can access but get loads of "cant mount"/"cant open" type messages. ive tried flashing twrp and CWM via ADB and it says successful (takes under a second ?) but neither seem to be present on a reboot ?
How bad have i messed up ??
anyone help ?
Try flashing factory image again and wipe every damn thing before doing that and dont lock the bootloader
again!
bhavstech said:
Try flashing factory image again and wipe every damn thing before doing that and dont lock the bootloader
again!
Click to expand...
Click to collapse
will the factory image include a recovery ? or do i need to do that separately ?
wilbur-force said:
will the factory image include a recovery ? Or do i need to do that separately ?
Click to expand...
Click to collapse
factory image includes everything you dont need to do that seperately!
And don't use a toolkit!
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
bhavstech said:
factory image includes everything you dont need to do that seperately!
Click to expand...
Click to collapse
OK. so i flashed the image and everything worked OK except the recovery which failed ??
wilbur-force said:
OK. so i flashed the image and everything worked OK except the recovery which failed ??
Click to expand...
Click to collapse
the radio flash failed too
"remote flash wipe failure"
It sounds like the first time in bootloader you must have used "fastboot boot recovery..." instead of "fastboot flash recovery..."
Are u using a Windows or Linux pc? If Linux, open a terminal and cd to the directory u downloaded the stock image to, connect ur phone the pc and type "adb reboot bootloader" when the phone reboots type "./flash-all.sh" that should wipe the phone and fix ur issue, it'll flash everything, recovery, rom, radio, and user data
wilbur-force said:
the radio flash failed too
"remote flash wipe failure"
Click to expand...
Click to collapse
did you use flash all.bat or u flash each and everything manually?
Ben36 said:
And don't use a toolkit!
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
Is there a reason you advise against a toolkit? Just curious, since I rely on one heavily and am wondering if it's going to cause problems down the road.
jason.larkin said:
Is there a reason you advise against a toolkit? Just curious, since I rely on one heavily and am wondering if it's going to cause problems down the road.
Click to expand...
Click to collapse
Because if you had read the thread on fastboot you wouldn't be making this post right now. My advice is go read it thoroughly. Don't worry. It's far far easier than it first looks. I remember first reading a post about it years ago thinking omg my brain is going to explode! But just follow the instructions and once you've used it once you'll think wow that was easy and never use a toolkit again
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
Because if you had read the thread on fastboot you wouldn't be making this post right now. My advice is go read it thoroughly. Don't worry. It's far far easier than it first looks. I remember first reading a post about it years ago thinking omg my brain is going to explode! But just follow the instructions and once you've used it once you'll think wow that was easy and never use a toolkit again
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
I did read that thread....a year ago when I used to do all this manually. Since I discovered the toolkit I haven't had a reason to. Was just curious if there was a technical reason for it or just personal preference.
Related
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.
simms22 said:
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.
Click to expand...
Click to collapse
Is there a way to get the factory img onto the phone via TWRP?
Does the bootloader still work?
BirchBarlow said:
Does the bootloader still work?
Click to expand...
Click to collapse
Yes, I'm able to get into TWRP/recovery mode.
woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then, you are fine, friend:victory:, just do what the guy upstairs said. (simms22)
wipe system, caches, Flash another Rom/kernel for N5
Fastboot flash /boot boot.img
Sent from my Nexus 5 using XDA Premium 4 mobile app
woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then what's the problem?
He's safe. He just needs to flash using fastboot.
This is the reason why Nexus devices are awesome.:angel:
woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..
The point in the bootloader is for this very thing. Just plug it into your pc and fastboot it
Unless you have a kernel/ rom zip or backup already in the memory then just use recovery
Sent from my Nexus 5 using Tapatalk
gee2012 said:
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..
Click to expand...
Click to collapse
Thank you, everyone. Disaster aborted.
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
devcager said:
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
Click to expand...
Click to collapse
Attempting to take the OTA will fail.
Download the factory image and extract bootloader-hammerhead-hhz11k.img
Boot your device into bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
vin4yak said:
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
Click to expand...
Click to collapse
Thank you! I get it about ADB, I had to solve one my problem in the past via ADB. Anyway, I just need to find the 4.4.4 bootloader in ZIP (or probalby .img will work too?) and flash it? That's it? Does it wipe my phone or something?
You just need to flash the IMG via fastboot, no wiping required!
EddyOS said:
You just need to flash the IMG via fastboot, no wiping required!
Click to expand...
Click to collapse
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
You don't need to. Just boot into fastboot, connect to PC, fastboot flash bootloader name_of_file.img, reboot, done
it's easy you must become familiar with fastboot and add the second you aren't it will come back to haunt you
Sent from my Nexus 5 using Tapatalk
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
so you learned nothing. awesome.
Zepius said:
so you learned nothing. awesome.
Click to expand...
Click to collapse
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
I'm still waiting for someone to make a thread saying their device is "bricked because flashed fastboot to adb using bootloader while in recovery with x toolkit"
My phone suddenly started showing zero reception, so i tried wiping it to just get a clean start. Im using TWRP (which i havent really used in the past) and did the "Wipe Data" option rather than the normal wipe because i'm a ****ing idiot. now it says there is no OS installed, so yeah.
I can still boot into recovery but not much else obvously. I'm hoping there's a way for me to mount the phone to my mac and load on a rom and fix it. I understand how stupid i sound but i really need someone to walk me though this. I used to mess around with my GS3 and all my old phones all the time and never had a problem but i haven't with my nexus really since i first got it. I swear i'm not actually retarded.
What are my options here?
FixedTheFernBack said:
My phone suddenly started showing zero reception, so i tried wiping it to just get a clean start. Im using TWRP (which i havent really used in the past) and did the "Wipe Data" option rather than the normal wipe because i'm a ****ing idiot. now it says there is no OS installed, so yeah.
I can still boot into recovery but not much else obvously. I'm hoping there's a way for me to mount the phone to my mac and load on a rom and fix it. I understand how stupid i sound but i really need someone to walk me though this. I used to mess around with my GS3 and all my old phones all the time and never had a problem but i haven't with my nexus really since i first got it. I swear i'm not actually retarded.
What are my options here?
Click to expand...
Click to collapse
You could probably just flash the stock Nexus 5 image from here developers.google.com android section. You'll see a bit saying nexus factory images.
If you can't actually manage to transfer the file on to your phone and flash it from recovery, then just use the tutorial on that page using adb and fastboot.
Yep. The options are fastboot flash stock system and boot.img or adb push a flashable zip to your sdcard and flash via recovery
Click link in signature for sticky then read my adb and fastboot thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yep. The options are fastboot flash stock system and boot.img or adb push a flashable zip to your sdcard and flash via recovery
Click link in signature for sticky then read my adb and fastboot thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot. Solved it with adb sideload cm11. i hadn't really ever used adb before so i was in a bit of a panic.
FixedTheFernBack said:
Thanks a lot. Solved it with adb sideload cm11. i hadn't really ever used adb before so i was in a bit of a panic.
Click to expand...
Click to collapse
Excellent
Sent from my Nexus 5 using Tapatalk
I have searched and can't find out anything about this, but for some reason I can flash recovery-clockwork-6.0.4.5-hammerhead.img through fastboot and then get into CM recovery. However, if I leave recovery and try to boot into it again, I get the dead droid picture. I can flash CM again and it'll work, but again, for a single use. I've never had this problem before on any Droid I've owned and I can't seem to find anyone dealing with it in this forum. Any help would be greatly appreciated.
No this phone is not rooted. I have unsuccessfully attempted this with CM (upon exiting recovery mode, you are prompted to root your phone if it hasn't been rooted).
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
You should also search the rules and list in he correct forum. This is not for questions only development
Sent from my Nexus 5 using XDA Free mobile app
also, clockwork mod recovery is long discontinued and provides no support anymore.
EddyOS said:
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
Click to expand...
Click to collapse
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
strakajagr said:
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
Click to expand...
Click to collapse
In any case, I can flash something else since CM is no longer supported. Thanks.
strakajagr said:
In any case, I can flash something else since CM is no longer supported. Thanks.
Click to expand...
Click to collapse
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How do I go about locking the bootloader after it's unlocked?
strakajagr said:
How do I go about locking the bootloader after it's unlocked?
Click to expand...
Click to collapse
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
BirchBarlow said:
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
Click to expand...
Click to collapse
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
strakajagr said:
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
Click to expand...
Click to collapse
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
simms22 said:
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
Click to expand...
Click to collapse
Word. Thanks.
Next order of business is figuring why there is so much lag when I text/gchat in 5.0. This is the whole reason I got into this mess. I couldn't wait 3 more weeks. Sadly, when I type, the keyboard freezes constantly. I figure I'll install a recovery mode correctly and then try to tackle that problem.