I was texting on my phone when it crashed. I was running SlimKat official release with franco kernel 25 for two weeks. Phone had been running great! Now it bootloops on the google logo and doesn't recognize the 32gb of memory. Wont mount any of the partitions in recovery. When in recovery (TWRP) and I opt to reboot to bootloader or reboot is says NO OS. Now as well all I can do with fastboot is relock the phone. I wanted to reflash the recovery to stock as Google will exchange the phone. When I try and flash the stock recovery in the terminal command window everything looks like its flashing good however when I boot into recovery it still boots TWRP.
Help please. :crying:
what do you mean all you can do is relock the phone in fastboot? that doesnt make sense.
what commands are you trying to do when you flash the stock recovery?
Flash the entire factory image. If you get errors your eMMC is probably toast and you should warranty it.
Sent from my Nexus 5
did you use toolkit for rooting?
Simonna said:
did you use toolkit for rooting?
Click to expand...
Click to collapse
You ask because of his troubleshooting expertise or because you think that toolkits and CF.. are killing emmc?
I have seen this problem from people using the manual method and the toolkits as well.
I strongly think that the question to ask is whether they have a 16GB or 32GB phone.
GUGUITOMTG4 said:
You ask because of his troubleshooting expertise or because you think that toolkits and CF.. are killing emmc?
I have seen this problem from people using the manual method and the toolkits as well.
I strongly think that the question to ask is whether they have a 16GB or 32GB phone.
Click to expand...
Click to collapse
I think that toolkits are killing emmc because I saw more users who used toolkits for rooting, and then their phones just dead.But maybe it's just a coincidence..
Toolkits does not kill emmc. This is just coincidence.
emmc died on the phone
Tapatalk-kal küldve az én Nexus 5-el
Simonna said:
I think that toolkits are killing emmc because I saw more users who used toolkits for rooting, and then their phones just dead.But maybe it's just a coincidence..
Click to expand...
Click to collapse
I don't think it's tool kits either. Keep in mind that more people use tool kits than don't. So even though you see more of what appears to be emmc failure with tool kit users there are more of them. I've seen it with people who have not used tool kits a well as those that have.
Sent from my Nexus 5
jd1639 said:
I don't think it's tool kits either. Keep in mind that more people use tool kits than don't. So even though you see more of what appears to be emmc failure with tool kit users there are more of them. I've seen it with people who have not used tool kits a well as those that have.
Sent from my Nexus 5
Click to expand...
Click to collapse
It's not toolkits. It's the luck of the draw. How many N5's sold compared to how many that have had fried nand is what needs to be looked at. That figure is going to be very hard to come by. It could be a normal percentage of failure or it could be high or low. Did Google cheap out on the memory to make the phone more affordable? Or did they put quality memory in and cut some other corners as well as cut their profit margin? All questions that none of us on XDA will, most likely, ever know. The one thing you can be certain of though, toolkits aren't the cause of these failures.
I also had this problem, I couldn't do anyting. I left it sitting there for the night.
The next morning, it booted up like nothing happened
El Daddy said:
Flash the entire factory image. If you get errors your eMMC is probably toast and you should warranty it.
Sent from my Nexus 5
Click to expand...
Click to collapse
Google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when I reboot the phone into bootloader it says unlocked again and the recovery stays TWRP no matter what I flash. Im lost. It doesn't make any sense....
Looks like I may have to send it in as is however I'm concerned they wont warranty it when they get it back unlocked with TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rooteddesire said:
google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when i reboot the phone into bootloader it says unlocked again and the recovery stays twrp no matter what i flash. Im lost. It doesn't make any sense....
Looks like i may have to send it in as is however i'm concerned they wont warranty it when they get it back unlocked with twrp.
Click to expand...
Click to collapse
Zepius said:
what do you mean all you can do is relock the phone in fastboot? that doesnt make sense.
what commands are you trying to do when you flash the stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot oem lock
and so on....
it says its successful, however its obviously not.
RootedDesire said:
fastboot flash recovery recovery.img
fastboot oem lock
and so on....
it says its successful, however its obviously not.
Click to expand...
Click to collapse
Then I reboot and get this
its definitely the stock recovery i extracted and placed in my fastboot folder
RootedDesire said:
Google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when I reboot the phone into bootloader it says unlocked again and the recovery stays TWRP no matter what I flash. Im lost. It doesn't make any sense....
Looks like I may have to send it in as is however I'm concerned they wont warranty it when they get it back unlocked with TWRP.
Click to expand...
Click to collapse
That's because your eMMC is dead. It can't be written to.
Sent from my Nexus 5
yet another brick in the wall
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Is somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
XeeV said:
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Does somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
Click to expand...
Click to collapse
Highly unlikely. AFAIK when your eMMC is dead, it's dead forever.
exb0 said:
Highly unlikely. AFAIK when your eMMC is dead, it's dead forever.
Click to expand...
Click to collapse
But it's not dead. It is readable. I can't write. But, maybe there is a workaround like with JetFlash USB drives. I have 2 JetFlash sticks. They became read-only: I could read, but could't write, even with dd or fdisk (they works OK, but after reinserting everything is as it was before). But there is a software: it erases JetFlash drives and I can write again.
XeeV said:
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Is somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
Click to expand...
Click to collapse
I had the same issue yesterday, I reflashed stock via fastboot and it fixed the issue, I couldnt flash/wipe/connect to adb or anything, when I tried to mount it showed internal storage size 0, so I went back to the bootloader and flashed all the stock stuff via fastboot and it did the trick for me.
Pawelss said:
I had the same issue yesterday, I reflashed stock via fastboot and it fixed the issue, I couldnt flash/wipe/connect to adb or anything, when I tried to mount it showed internal storage size 0, so I went back to the bootloader and flashed all the stock stuff via fastboot and it did the trick for me.
Click to expand...
Click to collapse
I can reflash a stock, but it writes nothing. It only shows, that it's writing. I can flash CWM instead TWRP. But after a reboot there will be my old TWRP. I can do "fastboot oem lock" and it show "locked", but after reboot it show "unlocked". All is read-only but no errors when writing.
---------- Post added at 09:17 PM ---------- Previous post was at 09:00 PM ----------
Nexus 5 has Sandisk SDIN8DE4. In datasheet there is "Enhanced Write Protection":
----------------------------------------------------------------------------------------------------------------------------------------
To allow the host to protect data against erase or write, the iNAND supports two levels of write
protect command 10 :
• The entire iNAND (including the Boot Area Partitions, General Purpose Area Partition, and
User/Enhanced User Data Area Partition) may be write-protected by setting the permanent
or temporary write protect bits in the CSD.
• Specific segments of the iNAND may be permanently, power-on or temporarily write
protected. Segment size can be programmed via the EXT_CSD register.
For additional information please refer JESD84-A441 standard.
----------------------------------------------------------------------------------------------------------------------------------------
and "H/W Reset":
----------------------------------------------------------------------------------------------------------------------------------------
Hardware reset may be used by host to reset the device, moving the card to a Pre-idle state and
disabling the power-on period write protect on blocks that was set as power-on write protect before
the reset was asserted. For more information, refer to JESD84-A441 standard.
----------------------------------------------------------------------------------------------------------------------------------------
Maybe, there is a way to turn off write protection of just do a hardware reset (but no to loose bootloader)?
Is anybody here familiar with eMMC, chips and JESD84-A441 standard?
Related
Anybody have any insight into whether or not the bootloader will be locked? Since there has never been a device directly from NVIDIA before we really don't have anything to go off of, or do we?
blaxer said:
Anybody have any insight into whether or not the bootloader will be locked? Since there has never been a device directly from NVIDIA before we really don't have anything to go off of, or do we?
Click to expand...
Click to collapse
It's required to ship locked as to support certain video features. But it also support 'fastboot oem unlock'. And yes, I've confirmed that it works.
agrabren said:
It's required to ship locked as to support certain video features. But it also support 'fastboot oem unlock'. And yes, I've confirmed that it works.
Click to expand...
Click to collapse
So, I'm assuming this means that it will shipped locked, but the bootloader is unlockable...
jadengore said:
So, I'm assuming this means that it will shipped locked, but the bootloader is unlockable...
Click to expand...
Click to collapse
Yes. Exactly what I'm saying.
Sent from my HTC One using XDA Premium HD app
Sounds as easy as Nexus devices. That would be great.
agrabren said:
Yes. Exactly what I'm saying.
Click to expand...
Click to collapse
And what about sources/binary blobs?
Adanedhil said:
And what about sources/binary blobs?
Click to expand...
Click to collapse
I don't have any details on that.
What key combo do you use to access the bootloader? Yes I know about adb reboot bootloader.
Sent from my Nexus 7 using Tapatalk 4 Beta
lol3caring said:
What key combo do you use to access the bootloader? Yes I know about adb reboot bootloader.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Back and Home while powering on.
Unlocked!
Guys, I just unlocked my bootloader! Here's a link for the ADB/Fastboot drivers, and I've attached below a link of what the bootloader unlock screen looks like!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jadengore said:
Guys, I just unlocked my bootloader! Here's a link for the ADB/Fastboot drivers, and I've attached below a link of what the bootloader unlock screen looks like!
Click to expand...
Click to collapse
I'll be posting details tomorrow on how to backup your most critical partitions (the ones that cannot be rebuilt if lost).
Stay tuned.
So is it bad that I unlocked today?
Sent from my SHIELD using xda app-developers app
agrabren said:
I'll be posting details tomorrow on how to backup your most critical partitions (the ones that cannot be rebuilt if lost).
Stay tuned.
Click to expand...
Click to collapse
I am really looking forward to your update on backing up the partitions.
After we just need a custom recovery to cleanly push SU to /system.
I can't wait for SU.
With active cooling I can't wait to see how far this SOC can be pushed. :fingers-crossed:
For anyone that cares I was able to re-lock the bootloader but unlike a nexus this is still marked as flagged for a voided warranty.
agrabren said:
I'll be posting details tomorrow on how to backup your most critical partitions (the ones that cannot be rebuilt if lost).
Click to expand...
Click to collapse
Be aware that even backing up all critical partitions does not protect you from permanently bricking your device. I'm thinking about the bootloader partition. If you erase or modify it, Shield will just not be able to boot anymore (because it has to be signed) and you will end with a brick. So don't ever do anything that could tamper with the bootloader. There are a few other partitions that are also needed to boot and that you don't want to mess with.
Partitions like boot, system, or userdata are safe though, and that's enough for all customization needs.
Gnurou said:
Be aware that even backing up all critical partitions does not protect you from permanently bricking your device. I'm thinking about the bootloader partition. If you erase or modify it, Shield will just not be able to boot anymore (because it has to be signed) and you will end with a brick. So don't ever do anything that could tamper with the bootloader. There are a few other partitions that are also needed to boot and that you don't want to mess with.
Partitions like boot, system, or userdata are safe though, and that's enough for all customization needs.
Click to expand...
Click to collapse
Agreed, although I'm somehow doubtful that a signed nvflash image won't make it's way into the light, which can repair a destroyed bootloader (as well as other partitions).
agrabren said:
Agreed, although I'm somehow doubtful that a signed nvflash image won't make it's way into the light, which can repair a destroyed bootloader (as well as other partitions).
Click to expand...
Click to collapse
I agree it would be nice, but for now there are none and it's probably safer to make no assumption about its future availability.
Gnurou said:
I agree it would be nice, but for now there are none and it's probably safer to make no assumption about its future availability.
Click to expand...
Click to collapse
Agreed. Tomorrow I'll check if an unlocked devices allows you to write over the bootloader. I don't *think* it does. I'm not even sure if the required "safe" partitions can be written over. But anyway, still going to get the list for everyone to be safe.
agrabren said:
Agreed. Tomorrow I'll check if an unlocked devices allows you to write over the bootloader. I don't *think* it does.
Click to expand...
Click to collapse
AFAIK it does and I'm not sure you even want to risk trying this . There is no purpose, SHIELD will not boot if the bootloader is changed even the slightest bit anyway, and if anything goes wrong before you restored the bootloader your device will become a brick.
If you want to play with fire anyway, make sure you raw-copied the partition from rooted Android first so you can restore it immediatly after.
And no matter what, don't reboot while the bootloader partition is altered!
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.
My English is quite bad, and I'm sorry for that. Anyway, I hope that someone of you can help me with my problem, and will understand what I wanted to say.
So, at first I unlocked bootloader. After that, with InsecureBootandRoot script I wanted to root phone. When I did it, in "cmd" it stuck on "Daemon started successfully".
From then, I can't run my phone. Bootloader is working, fastboot USB aswell. I tried to install few recoverys, but none of them were working. ADB is also not working, it can't see my device(Probably because it's not working in fastboot. And if my phone is not in fastboot, computer don't recognise my device). Also, I can't "throw" any files to phone because computer see my device only in fastboot.
I tried to use HTC ONE S AIO kit . It show me my CID(HTC 0_32) and version(3.16.401.8), but that's all. Other commands are not working at all.
I also installed sdk and all drivers. That didn't help, meh.
Any ideas what should I do to have my phone working again? :c
Pisay said:
Hello.
My English is quite bad, and I'm sorry for that. Anyway, I hope that someone of you can help me with my problem, and will understand what I wanted to say.
So, at first I unlocked bootloader. After that, with InsecureBootandRoot script I wanted to root phone. When I did it, in "cmd" it stuck on "Daemon started successfully".
From then, I can't run my phone. Bootloader is working, fastboot USB aswell. I tried to install few recoverys, but none of them were working. ADB is also not working, it can't see my device(Probably because it's not working in fastboot. And if my phone is not in fastboot, computer don't recognise my device). Also, I can't "throw" any files to phone because computer see my device only in fastboot.
I tried to use HTC ONE S AIO kit . It show me my CID(HTC 0_32) and version(3.16.401.8), but that's all. Other commands are not working at all.
I also installed sdk and all drivers. That didn't help, meh.
Any ideas what should I do to have my phone working again? :c
Click to expand...
Click to collapse
There is no matching RUU, but i will upload you the matching boot+recovery. Will take some minutes. Download both files and flash them via fastboot.
DOWNLOAD
I should add that my phone is S3.
Anyway thanks for the answer, didn't knew someone is going to help me so fast :3.
pisay said:
i should add that my phone is s3.
Anyway thanks for the answer, didn't knew someone is going to help me so fast :3.
Click to expand...
Click to collapse
then dont flash the files. I'll have a look for the matching files.
Are you sure you have a ville c2 (S3) ??? Because 3.16.401.8 is the official EU S4 Jellybean release...
---------- Post added at 09:26 PM ---------- Previous post was at 09:17 PM ----------
LS.xD said:
then dont flash the files. I'll have a look for the matching files.
Are you sure you have a ville c2 (S3) ??? Because 3.16.401.8 is the official EU S4 Jellybean release...
Click to expand...
Click to collapse
You can see your model ID here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Whats your MID??
oh well, I'm quite shocked.
When I bought this phone, they told me that it's 560e.
But I looked now, and it's Z520e.
Sorry for that, didn't knew that I have S4. Can you upload files for S4 again?
Pisay said:
oh well, I'm quite shocked.
When I bought this phone, they told me that it's 560e.
But I looked now, and it's Z520e.
Sorry for that, didn't knew that I have S4. Can you upload files for S4 again?
Click to expand...
Click to collapse
You're lucky LINK S4 files
If you say so ._.
I flashed them, what should I do now?
Pisay said:
If you say so ._.
I flashed them, what should I do now?
Click to expand...
Click to collapse
Phone should be fine again
Well, I still can't turn it on.
My computer still can't see him.
I can't describe it as "working phone" ;_;
Recovery also still not working.
Pisay said:
Well, I still can't turn it on.
My computer still can't see him.
I can't describe it as "working phone" ;_;
Recovery also still not working.
Click to expand...
Click to collapse
May you post a link to the software you have flashed to your phone?
Have you already tried PhilZ recovery? --> LINK
Dunno if I can paste links here.
Anyway I was trying to root my phone with this tutorial: http://theunlockr.com/2012/04/22/how-to-root-htc-one-x/ .
*Yeah, I'm stupid and I thought my phone is HTC ONE X, not HTC ONE S*
@edit
This recovery is also not working.
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 <- I have this RUU on PC. Will it work on my phone?
You have the wrong CID for the RUU.
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:55 PM ----------
Did you perform "factory reset" in bootloader Mode already?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Yeah, I already tried that. It stuck on logo then, like with recovery.
Pisay said:
Yeah, I already tried that. It stuck on logo then, like with recovery.
Click to expand...
Click to collapse
I have checked the link. The script "only" flashes a kernel (boot.img) + Superuser app. Flashing a new kernel should work for you. What command did you use to flash the boot.img ??
fastboot flash boot boot.img and then fastboot flash boot recovery.img
I'll try uninstalling sdk and all drivers, and then install them using tutorial from this forum. Maybe it will be easier, when adb will work .-.
Pisay said:
fastboot flash boot boot.img and then fastboot flash boot recovery.img
I'll try uninstalling sdk and all drivers, and then install them using tutorial from this forum. Maybe it will be easier, when adb will work .-.
Click to expand...
Click to collapse
Did you restart the bootloader after flashing? Have you cleared caches via fastboot also??
BTE adb will not help you without at least a working recovery...
Which command I should use to restart it?
And yeah, I cleared caches.
And thanks for trying to help me, I really appreciate it. U're wasting your time because some teenager destroyed his phone ._. . Oh god, I'm stupid.
@edit
When I tried to run bootloader, it showed me this:
Thats PhilZ CWM Perfect, you have a working recovery I'm off for 30 minutes. I can assisst you via Teamviewer when i'm back, if you want.
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Not at all, these commands under it mean that anything in recovery won't work.
Also, from now I can't even start bootloader ._. .
Oh well, I'll just give this phone to the service. If they can't turn it on, and also turn on bootloader, can they say to me something like "Hey, you tried to change system of this phone so we won't give you another one"?. :c
Pisay said:
Not at all, these commands under it mean that anything in recovery won't work.
Also, from now I can't even start bootloader ._. .
Oh well, I'll just give this phone to the service. If they can't turn it on, and also turn on bootloader, can they say to me something like "Hey, you tried to change system of this phone so we won't give you another one"?. :c
Click to expand...
Click to collapse
Philz has a option to boot into bootloader. Have you tried it? If you give it to service they'll recognize that you have modified thze phone. As you were able to flash philz, you should also be able to flash boot+recovery image. Then you'll have to perform "factory reset + clear storage" to fix the sd card issue. I'm sure its possible! Once done you can install a rom manually or change the CID to run a stock RUU EU unbranded.
As your warranty is void I'd suggest to fix it o ya own
About 4 weeks ago my phone spontaneously rebooted itself. Once it did I lost all (including the internal SD card) data. So basically a hard factory reset. Additionally TWRP and the recovery was borked. After much struggling I managed to get adb to put TWRP back. But now. Every necessary file system is effectively read only. (I can't mount them in
TWRP at all and when in the phone via ADB. no love) I say effectively, because although it lists it in mount as being rw. I can't even do a simple touch. nothing writes. I'm still rooted, I still have the ability to configure (as in initial setup) however if you restart the phone, all is lost, and you need to reconfigure.
Any suggestions recommendations or sympathy would be appreciated. The one thing I do see is that on the ext4 file systems (which are the ones that are effectively read only) there is an error with the journal that normally is fixed by deleting the journal and trying again. Because of this I can't re-install the OS etc. Thanks again for allowing me to whimper. Sucks that it did this 2 months before the 6.... I had to bite the bullet and replace. LG and Google both say it sucks to be me. :crying:
Backup your files. Fastboot flash userdata.img
Sent from my Nexus 5 using Tapatalk
rootSU said:
Backup your files. Fastboot flash userdata.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah, i tried that and it keeps giving me errors related to not being able to write to the file system because the bootloader is locked. Additional. the bootloader relocked, if I unlock it, it unlocks in word but the restart to bootloader shows it is again locked. Thanks for the help though. any idea appreciated.
linuxrebel said:
yeah, i tried that and it keeps giving me errors related to not being able to write to the file system because the bootloader is locked. Additional. the bootloader relocked, if I unlock it, it unlocks in word but the restart to bootloader shows it is again locked. Thanks for the help though. any idea appreciated.
Click to expand...
Click to collapse
Your NAND is fried. Device needs sending for repair
Sent from my Nexus 5 using Tapatalk
I've not dealt with Moto's before, All my previous phone's have typically been Samsung, Nexus, and currently my LG G3.
My mom has a Verizon XT926 that from what it sounds like started an OTA update and is now stuck at the red circle, white M logo screen, that says "Dual Core"
I would call myself pretty android savvy, and have tried everything I've found so far without any luck.
Here is the current situation:
I can get into recovery, and fastboot
I have tried using RSD Lite to flash multiple versions of the stock ROM without any success
I have tried using HouseOfMoto method, also without any success
I read through SamuriHL's thread here and at droidrzr.com and tried every possible suggestion without any success
Here is a screenshot of RSD Lite
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, after attempting an RSD Lite flash, the error message on the phone is:
failed to read signature for partition aboot
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I thought the above error meant that I was trying to downgrade, but I have even attempted to flash the latest image of VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml and it still fails.
From a few of SamuriHL's posts, i get the feeling this phone has a "corrupt partition table" issue that I don't believe anyone has been able to find a solution for.
Any help would be appreciated, thanks guys!
.10 is not the most current OTA, that's why you're getting the downgrade error. Look in the general section for the thread with the .15 update.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
.10 is not the most current OTA, that's why you're getting the downgrade error. Look in the general section for the thread with the .15 update.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Same deal, phone returns "fail"
This time it doesn't specify that its a downgraded security version, it just flat out fails. Pretty sure the OTA fried this thing. Oh well.....
Namtaru said:
Same deal, phone returns "fail"
This time it doesn't specify that its a downgraded security version, it just flat out fails. Pretty sure the OTA fried this thing. Oh well.....
Click to expand...
Click to collapse
you apparently missed some key points in your research, obvious just by looking at your screenshot.
you need to completely remove the "tz" and "gpt" lines from the xml file, then flash again.
your having a pretty basic issue, thats fairly easily fixed.
.... and yes, if it comes to it, i can easily guide you to fixing the partition table, but that doesnt appear necessary at this point.
bweN diorD said:
you apparently missed some key points in your research, obvious just by looking at your screenshot.
you need to completely remove the "tz" and "gpt" lines from the xml file, then flash again.
your having a pretty basic issue, thats fairly easily fixed.
.... and yes, if it comes to it, i can easily guide you to fixing the partition table, but that doesnt appear necessary at this point.
Click to expand...
Click to collapse
Would you be able to point me to the thread where this is talked about?
I found many references to removing the lines that have getvar in them, which I have also tried, but none referencing your suggestion.
Thanks!
Namtaru said:
Would you be able to point me to the thread where this is talked about?
I found many references to removing the lines that have getvar in them, which I have also tried, but none referencing your suggestion.
Thanks!
Click to expand...
Click to collapse
it has been said by myself and others easily a hundred times, i would rather not dig through threads looking for it.
when we post certain tools and firmwares, we just remove those lines before you get them to avoid this issue. but firmwares posted more for general use will still have those lines, as they are sometimes needed.
if you were to type "gpt error rsd android" into google, im sure there would be many post in threads suggesting the removal of certain lines from the xml as i have suggested.
hope that helps..
edit, added some search terms, just gpt error was too vague.
bweN diorD said:
it has been said by myself and others easily a hundred times, i would rather not dig through threads looking for it.
when we post certain tools and firmwares, we just remove those lines before you get them to avoid this issue. but firmwares posted more for general use will still have those lines, as they are sometimes needed.
if you were to type "gpt error rsd android" into google, im sure there would be many post in threads suggesting the removal of certain lines from the xml as i have suggested.
hope that helps..
edit, added some search terms, just gpt error was too vague.
Click to expand...
Click to collapse
Still doesn't matter, fails again.
The phone doesn't report anything on screen, the last line is still just "usb connected"
edit: when i try to flash .10 instead of .15, it still fails, but the phone returns a single line of: "failed to read signature for partition aboot"
Namtaru said:
Still doesn't matter, fails again.
The phone doesn't report anything on screen, the last line is still just "usb connected"
edit: when i try to flash .10 instead of .15, it still fails, but the phone returns a single line of: "failed to read signature for partition aboot"
Click to expand...
Click to collapse
rsd really blows some times.
run this in fastboot.
-extract the rar
-run the windows batch file and follow the directions
-profit!!
bweN diorD said:
rsd really blows some times.
run this in fastboot.
-extract the rar
-run the windows batch file and follow the directions
-profit!!
Click to expand...
Click to collapse
Already tried that, and DROID_RAZR_HD_Utility_1.4gpt KK, and DROID_RAZR_HD_Utility_1.3.gpt fix.
I'm pretty sure the phone is beyond repair. It just crazy to me because I've been using android since just after the Dream, and of all the horrible things I've done to them, I've never bricked one. Yet a simple OTA from Verizon on a bone stock Rzr HD bricks it, lol.
Namtaru said:
Already tried that, and DROID_RAZR_HD_Utility_1.4gpt KK, and DROID_RAZR_HD_Utility_1.3.gpt fix.
I'm pretty sure the phone is beyond repair. It just crazy to me because I've been using android since just after the Dream, and of all the horrible things I've done to them, I've never bricked one. Yet a simple OTA from Verizon on a bone stock Rzr HD bricks it, lol.
Click to expand...
Click to collapse
unless you grabbed that one from a thread, then you havent tried it. its not the same as either of those you mentioned, its newer.
it may be bricked, you will know after you flash that file. there is nothing else im aware of to try.
if everything says it failed when using the utility, then its toast.
bweN diorD said:
unless you grabbed that one from a thread, then you havent tried it. its not the same as either of those you mentioned, its newer.
it may be bricked, you will know after you flash that file. there is nothing else im aware of to try.
if everything says it failed when using the utility, then its toast.
Click to expand...
Click to collapse
Sorry I wasn't clear. I already tried the one you posted. Literally the exact same link you posted. I ALSO tried the two older versions of the fix you posted.
Namtaru said:
Sorry I wasn't clear. I already tried the one you posted. Literally the exact same link you posted. I ALSO tried the two older versions of the fix you posted.
Click to expand...
Click to collapse
that sux, its done then.
i have seen this a few times before, but its pretty rare.
bweN diorD said:
that sux, its done then.
i have seen this a few times before, but its pretty rare.
Click to expand...
Click to collapse
Thanks for the suggestions. Anyone want a bricked razr hd? Lol
I can help u contact me
zainbintariq12345 said:
I can help u contact me
Click to expand...
Click to collapse
Why not just post it here so everyone can benefit?
Your either f.o.s. or charging money, otherwise there is no reason for a private fix.
Sent from my G3 Rockin Cyanogen
same thing here
I have an xt926 doing the same thing. I dont care if i recover the phone or not, but i was wondering if there was a way to make the computer recognize the memory so i can pull the pictures off it? even better, pull the contacts off it, if thats possible? thanks in advance!
me pasa igual amigo tengo un xt926 y el progrma no me reconoce el cel alguien sabe como hacer
Namtaru said:
Thanks for the suggestions. Anyone want a bricked razr hd? Lol
Click to expand...
Click to collapse
What is it doing can you get to the red motorola logo. If you can then try and plug in charger and while connected to charger, when it gets to the red M logo hold power and volume up and volume down at the same time. when screen goes off release right away and then as quick as you can hold the same three buttons untill you get to fastboot mode and then let go. if it gets to fastboot mode then it might just be a bad battery. If it does not then it is bricked and you would need a fastboot cable to get into fatboot mode and flash stock firmware and bring back the device to life.
xt926 Stuck at Droid Logo
ive tried a hard reset and same thing just stuck at boot when i turn it on it makes noise and starts to fired up and then it just sits at the droid sign until battery dies or i hold volume up or down and it powers off ??? i cant get to the recovery menu and some other menu the on where you select recovery but thats it ??? somone please help thanks
Namtaru said:
I've not dealt with Moto's before, All my previous phone's have typically been Samsung, Nexus, and currently my LG G3.
My mom has a Verizon XT926 that from what it sounds like started an OTA update and is now stuck at the red circle, white M logo screen, that says "Dual Core"
I would call myself pretty android savvy, and have tried everything I've found so far without any luck.
Here is the current situation:
I can get into recovery, and fastboot
I have tried using RSD Lite to flash multiple versions of the stock ROM without any success
I have tried using HouseOfMoto method, also without any success
I read through SamuriHL's thread here and at droidrzr.com and tried every possible suggestion without any success
Here is a screenshot of RSD Lite
Also, after attempting an RSD Lite flash, the error message on the phone is:
failed to read signature for partition aboot
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I thought the above error meant that I was trying to downgrade, but I have even attempted to flash the latest image of VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml and it still fails.
From a few of SamuriHL's posts, i get the feeling this phone has a "corrupt partition table" issue that I don't believe anyone has been able to find a solution for.
Any help would be appreciated, thanks guys!
Click to expand...
Click to collapse
As long as you can to fastboot you can get his device working here are t correct drivers for your device. Install these drivers
http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663
and here is the correct firmware https://www.androidfilehost.com/?fid=24269982087011676
Install the drivers for your device then try flashing the correct firmware i gave you drivers for 64 bit windows system if you have 32 instead let me know and ill give you link to those drivers
---------- Post added at 02:04 AM ---------- Previous post was at 02:00 AM ----------
sdwyz74 said:
ive tried a hard reset and same thing just stuck at boot when i turn it on it makes noise and starts to fired up and then it just sits at the droid sign until battery dies or i hold volume up or down and it powers off ??? i cant get to the recovery menu and some other menu the on where you select recovery but thats it ??? somone please help thanks
Click to expand...
Click to collapse
You might have a bad battery.