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.
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
Hi, ok, so i'm on CM11 currently and was thinking of flashing a stock rom, but keeping my root and recovery intact; whats the best away of doing this, any ideas?
From what i've gathered i have the following options;
DL and flash stock rom direct from google, reroot and re install recovery (i used wugs toolkit first time round; but i'd rather avoid having to reroot and re-install the recovery if i can)
Flash one of the currently rooted roms in Android Development (this is likely going to be the 'root' i go down; why would i need to flash the radio and or bootloader update???)
I'm just making sure i'm not making this more complicated than it needs to be; that is to say, make sure there isn't an easier method.
p.s. The reason behind using stock rooted rom is simple, i was using Xposed Frameworks and came across Gravity Box, the number of options on it are mind boggling, and i feel it gives me greater control over my phone.
Either way will work. Personally I'd flash the factory image and then re-root, but that's just me. If you go that route use this instead of wugs
http://forum.xda-developers.com/showthread.php?p=47025283
Sent from my Nexus 5
easiest?
Flash factory image
start android....enable USB debugging
Fastboot flash custom recovery
xfer and flash SU zip
reboot
chaco81 said:
easiest?
Flash factory image
start android....enable USB debugging
Fastboot flash custom recovery
xfer and flash SU zip
reboot
Click to expand...
Click to collapse
Even easier is that you do not need to enable debugging in order to fastboot flash recovery or push via adb in recovery...
Sent from my Nexus 5
jd1639 said:
Either way will work. Personally I'd flash the factory image and then re-root, but that's just me. If you go that route use this instead of wugs
http://forum.xda-developers.com/showthread.php?p=47025283
Sent from my Nexus 5
Click to expand...
Click to collapse
chaco81 said:
easiest?
Flash factory image
start android....enable USB debugging
Fastboot flash custom recovery
xfer and flash SU zip
reboot
Click to expand...
Click to collapse
Pirateghost said:
Even easier is that you do not need to enable debugging in order to fastboot flash recovery or push via adb in recovery...
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks all, your advice is appreciated; jd, I'll give that link a shot
Pirateghost said:
Even easier is that you do not need to enable debugging in order to fastboot flash recovery or push via adb in recovery...
Sent from my Nexus 5
Click to expand...
Click to collapse
Even more easy is to buy a rooted phone, now top that
I'm in a rush to go somewhere, I very well know 2 ways to go: 1st avenue which takes 20 minutes and 2nd avenue that takes 25 minutes. Both ways are safe to go. Why should I spend 30 minutes analyzing the map to see which is faster and/or looking for a 3rd way if the time will be spent anyways
why not just factory reset and flash a deodexed stock ROM with SuperSU included, there are plenty hanging around development.
mistahseller said:
why not just factory reset and flash a deodexed stock ROM with SuperSU included, there are plenty hanging around development.
Click to expand...
Click to collapse
Is their literally a step by step to flash back to stock ? Mistah seems like your way is fairly simple ? Is there a guide to that anywhere ?
I have a GS3 (SGH i747) on CM11 and just want to be able to use MHL / HDMI.. Which the CM currently does not support.. Dont really want to go back to stock but I need MHL to work and I'm not sure any other way ?
Is there another ROM I can flash that supports it MHL that is decent ? If not, I dont know exactly how to get it back to stock if someone can help ..
Thanks.
robberrobbie said:
Is their literally a step by step to flash back to stock ? I have a GS3 (SGH i747) on CM11 and just want to be able to use MHL / HDMI.. Which the CM currently does not support.. Dont really want to go back to stock but I need MHL to work and I'm not sure any other way ?
I dont know exactly how to get it back to stock.. Thanks.
Click to expand...
Click to collapse
You are in the wrong forums
Sent from my Nexus 5
Pirateghost said:
You are in the wrong forums
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm just asking about method itself as I cannot find in SG3 or any where.. I understand I am in Nexus 5 ? if nobody wants to answer that's fine.
robberrobbie said:
I'm just asking about method itself as I cannot find in SG3 or any where.. I understand I am in Nexus 5 ? if nobody wants to answer that's fine.
Click to expand...
Click to collapse
The methods are different between nexus devices and other
Sent from my Nexus 5
robberrobbie said:
I'm just asking about method itself as I cannot find in SG3 or any where.. I understand I am in Nexus 5 ? if nobody wants to answer that's fine.
Click to expand...
Click to collapse
There are return to stock guides in all the s3 forums here. Essentially you'll be flashing the official .tar via odin.
If you cant find the guides, ask there not here. This phone is completely different. Your method is not the same.
Sent from my Nexus 5 using Tapatalk
rootSU said:
There are return to stock guides in all the s3 forums here. Essentially you'll be flashing the official .tar via odin.
If you cant find the guides, ask there not here. This phone is completely different. Your method is not the same.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok ok thanks.
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.
I have to go to uni in 1 hour and updated my bootloader via flashify, now its stuck in bootloader and wont boot. TWRP is the only accesible option for me. Tried to reflash the bootloader via fast boot but nothings happening.
Bootloader : hhz11k
Rom : N5X 5.0 AOSP Ver. 5.4
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
EddyOS said:
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
Click to expand...
Click to collapse
I'm restoring right now. Doy you know why this happened? Isn't flashify able to flash the bootloader, and if that was the case, shouldn't a flash via fastboot be the solution to my problem?
Anyways thx for your quick answer!
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
EddyOS said:
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
Click to expand...
Click to collapse
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Escoban said:
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Click to expand...
Click to collapse
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Ben36 said:
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
rootSU said:
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
Click to expand...
Click to collapse
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Escoban said:
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Click to expand...
Click to collapse
Were you flashing zips instead do you mean?
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Glad i said "le'ts google it" before going full wipe, i owe you dude.
I downloaded 5.1 radio and bootloader and flashed them using Flashify, then i got the same problem as OP. Reflashing the kernel fixed it.
*deletes Flashify*
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.