So basically I have my nexus 5 and it’s completely stocked. I don’t want to root or do anything that could prevent me from receiving OTA updates?
What are the steps to update my phone rom stock 4.4 to 4.4.1.
Thanks
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
richport29 said:
I found this video very helpful.
http://www.youtube.com/watch?v=rfZ4f5Bdgfc&list=FLJJ5N1JCwlum5OdXVTemjHw&index=2
Click to expand...
Click to collapse
I have a nexus 5.
rayoubi said:
I have a nexus 5.
Click to expand...
Click to collapse
Exact same process.
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
Obviously use the Nexus 5 4.1.1 ota
Be patient and receive the update directly from Google as an OTA within a week, or so. There might need to be a revision to this update, due to issues with the new radio seeming to not get good signal strength and so forth, which is why Goofle sends it out incrementally.
Sent from my Nexus 5 using Tapatalk
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
jd1639 said:
F n a I've never seen so many dopes in a row
http://forum.xda-developers.com/showthread.php?p=47369234
Click to expand...
Click to collapse
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
hotleadsingerguy said:
People need to search first, but that guide doesn't work for everyone.
My phone wouldn't reboot into actual recovery...it came up saying "No error" or some nonsense and wouldn't get into recovery. It makes the guide useless.
Click to expand...
Click to collapse
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
jd1639 said:
The guide is not useless. If you can't boot into recovery you're doing something wrong or your recovery is borked. If its borked you can fix it.
Click to expand...
Click to collapse
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
rootSU said:
Then your recovery is broken. Look at the how to flash factory images sticky in General and fastboot flash a fixed recovery.
Nothing to do with the fact that this is another OTA thread when there is an OTA sticky. The guide is not useless, your phone is.
Click to expand...
Click to collapse
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
hotleadsingerguy said:
And, as I mentioned, I haven't modified a thing on the phone. If my recovery is broken, it was broken from the factory.
Click to expand...
Click to collapse
I never said it was anything to do with what you had done or when it had broken.
hotleadsingerguy said:
And, again, the guide had nothing to do with that. If anyone else has the issue (which people are having, according to a few other topics I've seen), the guide makes no account for it -- for anyone with the issue, the guide is of no help.
Click to expand...
Click to collapse
And why would it? It also doesn't help people with a smashed screen or broken volume buttons. The guide is a guide to do what needs to be done on a fully working phone. It does NOT need to cover every fault that someone might have that prevents them doing the things in the guide. The fact your phone is broken bears no relevance to the usefulness of the guide. Besides, I already advised you what you could try to fix it.
Anyway, this thread is a duplicate and I have requested it be closed.
hotleadsingerguy said:
Oh, I didn't realize the guide explained how to fix it if something happened to your recovery. If so, I redact my statement.
(Obviously that's sarcasm and I don't redact my statement, since it doesn't do that)
My phone is completely bone-stock. I haven't rooted or unlocked. It doesn't boot into recovery using the method listed in the guide, and booting into the system menu and selecting Recovery just boots the phone normally for me.
Click to expand...
Click to collapse
hi
i am a noob. my phone is also compleely stock. not rooted and locked. i just activated with my carrier and downloaded speedtest. thats it. i have android sdk and platform tools and universal naked driver with adb support installed on my pc.
Code:
adb boot recovery
takes me to recovery. and i side loaded from there. :good:
Related
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Edit: Forgot to also ask, am I just an idiot?
badfontkeming said:
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Click to expand...
Click to collapse
I have the same issue, no fix yet.
untermensch said:
I have the same issue, no fix yet.
Click to expand...
Click to collapse
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
I have the exact same problem so I right there with ya
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
badfontkeming said:
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
Click to expand...
Click to collapse
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well.
The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.
EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
Yeah... the issue is, the reason I'm trying to flash CWM is so I can get root.
krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
sparky28000 said:
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
Click to expand...
Click to collapse
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
krhainos said:
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
Click to expand...
Click to collapse
Now there is atleast 3 people since I bricked mine also
krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
just curious how are you able to get in APX mode it seems I cant even do that
Drgravy said:
just curious how are you able to get in APX mode it seems I cant even do that
Click to expand...
Click to collapse
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
krhainos said:
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
Click to expand...
Click to collapse
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Drgravy said:
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Click to expand...
Click to collapse
I used the reset hole in place of the power button when fiddling with button combinations. Hold down VOL+, and poke the reset hole with a paperclip and that'll get you in APX mode -- not like it does any of us any good.
I thought I had bricked mine...
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
jdeatsch said:
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
Click to expand...
Click to collapse
Not working for me at all...
untermensch said:
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
Click to expand...
Click to collapse
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Weird. When I try to edit this post, I only get 3/4 of the quote and none of my actual post to edit. Anyway...
Just wanted to clarify: not asking for directions. If the file is what I think it is, I know what I'm doing. I just want to know that the file is what I think it is.
It is the Jelly Bean recovery kernel and the ClockWorkMod ramdisk repacked with mkbootimg, then blobpack,
then I added the "-SIGNED-BY-SIGNBLOB-" header with a hex editor. it seems like ADB does not work but I
was able to root with an update.zip
I installed this with fastboot and erased and re-flashed 4 time's before posting to make sure
it would not cause instant brick.
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Would opening the command prompt window with administrative rights make a difference? Worth a shot.
Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.
It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
TwistedPoet said:
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
Click to expand...
Click to collapse
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
buhohitr said:
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
Click to expand...
Click to collapse
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
TwistedPoet said:
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
Click to expand...
Click to collapse
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
buhohitr said:
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
TwistedPoet said:
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
Click to expand...
Click to collapse
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
At last I got to know lot of things from this thread as I'm new to this trade.
TwistedPoet said:
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
Click to expand...
Click to collapse
Update - With some very helpful guides and a little but of explanation, I was able to return to stock ROM, which returned my ability to boot into recovery mode. I also successfully flashed Safe strap Recovery onto my device. After looking at the guide about which custom ROM's can be flashed onto the phone, I'm considering using one but I am a tad hesitant. I know very very little about framework, kernels and modules. So, I guess we'll see. Thanks for the simply excellent links and your time!!!!!
All,
I got myself into a bit of pickle and could use some advice.
First, device information:
Nexus 5 Hammerhead D821(E)
Hw version rev_11
Bootloader version HHZ11k
Secure boot enabled
lock state unlocked
I think it's 4.4.2 or 4.4.3. I haven't installed KitKat.
Also running some xposed modules and Teamwin recovery but haven't flashed a rom or kernel
The issue
About an hour ago I got into the com.android.systemui. The screen keeps flashing and I'm lucky if I can power off the device. No chance of starting an app or getting into settings. When the device is powered up I can not access file folders through Explorer, in bootloader the device is not even recognized.
I figure I need to do a factory reset but seeing that I can't reach settings I don't know how to do this exactly (I assume it's OK to do with a rooted device that's still running the custom ROM?) Should I do it through TWRP? And if so, how do I proceed? I've read a few threads that deal with similar issues but I haven't found a manual that I feel fits completely which make some uncomfortable to try.
Thanks very much in advance,
T
Also, I just found this one: http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Would that be the right way to go?
First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.
Lethargy said:
First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.
Click to expand...
Click to collapse
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!
Taeglian said:
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
Click to expand...
Click to collapse
That would be a "bootloop" or non-boot, not a "soft-brick".
Taeglian said:
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!
Click to expand...
Click to collapse
Cool. But I do still suggest you have a look at various threads in the first link of my signature to learn a little more.
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
junkshot9112 said:
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
Click to expand...
Click to collapse
Well if you have an unlocked bootloader you can simple flash the stock images.
NBreunig3 said:
Well if you have an unlocked bootloader you can simple flash the stock images.
Click to expand...
Click to collapse
Thank you so much for the reply. I think I could even do a factory reset from recovery, but I'm not sure. I'm pretty new at this. I was really hoping there may be a way I could backup my data first, or even fix the issue, as I'm pretty sure I know what happened. I think my permissions are set wrong, but I could be entirely wrong. I found this guide that sounds like my issue, but it is for a different device. I've tried adapting it to the best of my ability, but I can't get the phone in ADB mode from recovery. http://www.gizbeat.com/2103/how-to-change-file-permissions-through-adb/
Wouldn't hurt to try knowing you can also just flash stock images.
NBreunig3 said:
Wouldn't hurt to try knowing you can also just flash stock images.
Click to expand...
Click to collapse
Can you point me in the direction of someone who may be able to help me do just that? I've tried just about all I can think to do. I really am new at this and feel I am in over my head. I really appreciate any and all help and would gladly donate to this site or any individual user who is able to help me solve my problems (I hope it isn't against your rules to say things like that).
Thanks again.
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
NBreunig3 said:
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
Click to expand...
Click to collapse
Sorry, I was unclear, that was my fault. I believe I know how to flash stock images. That is something I have done since the OG Droid. I was asking if you may know anyone who may be able to help me attempt to backup my data, reset my permissions, or even get the phone into ADB mode before I resort to losing everything. Again, apologies for being unclear.
No worries. I would just look online and possibly post another thread here or just wait for replies.
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
cntryby429 said:
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
Click to expand...
Click to collapse
Is this what is referred to as a "dirty flash"?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
robocuff said:
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
Click to expand...
Click to collapse
I was successful. Thank you so much. What can I do for you to show thanks?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
Yes. But in reality it is not much different than taking an OTA. That never wipes data. I only clean flash if I am having issues after a dirty flash and I can't remember the last time that happened.
Sent from my Pixel XL using XDA Labs
junkshot9112 said:
I was successful. Thank you so much. What can I do for you to show thanks?
Click to expand...
Click to collapse
Your thanks is more than enough.?