Database Info

Boot stops at 'Google', can't mout sdcard in cwm

Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!

PedroBustamonte said:
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
Click to expand...
Click to collapse
flasgh stock via fastboot and wipe everything DONE!

i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,

Cascabreu said:
flasgh stock via fastboot and wipe everything DONE!
Click to expand...
Click to collapse
So there's no way to get the content of the sdcard before I wipe everything?
ej8989 said:
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Click to expand...
Click to collapse
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)

PedroBustamonte said:
So there's no way to get the content of the sdcard before I wipe everything?
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
Click to expand...
Click to collapse
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.

mdean1981 said:
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
Click to expand...
Click to collapse
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...

It will also wipe everything if I remember well
Envoyé depuis mon Nexus S avec Tapatalk

PedroBustamonte said:
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
Click to expand...
Click to collapse
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue

Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
Yes you're right. But I really can't think of any thing I could try.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a

Blissfull said:
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Click to expand...
Click to collapse
Factory Images for Nexus Devices
https://developers.google.com/android/nexus/images

Hi ^^
I had the same problem with my Nexus S a long time ago and never found out how to solve it. It seems that the internal memory is corrupted and nothing but replacing the motherboard can solve it. Since I bought mine in the USA but I live in Belgium I never got mine repaired. Sometimes I come back here to see if there is still no solution but each time I'm disappointed...
Sorry.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
I can confirm this. I had the same thing happen to my Nexus S 4G recently. I was never able to salvage any data off the sdcard no matter what I tried (various mounting attempts in recovery, any adb command I thought might be helpful, etc.). As a last resort I tried to lock/unlock the bootloader - once I locked it, I was unable to unlock it again, it just froze up after asking me if I was sure I wanted to unlock. I guess that's what happens when the internal sdcard goes to hell. I ended up taking it to my local Sprint store and they replaced the phone with a refurbished one from Samsung (for approximately $35).

[Q] NEXUS 5 BRICKED TRYING TO ROOT WITH CF AutoRoot. HELP!?

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.

failed to mount /efs

is there a fix for this after going to the 4.3 update. i flashed the stock image from odin and now it am having this issue. My phone also has a black transparent popup with yellow lettering. I believe it is in factory mode. There is no data in the efs file. I think that is the overall issue right now. Does anyone have any help/ suggestions?
Here is what I have done to try and fix this issue
Reflash with odin
reflash with keis
factory reset through operating system
factory reset through recovery
reflash with odin using pit file as well

Dullawolf said:
is there a fix for this after going to the 4.3 update. i flashed the stock image from odin and now it am having this issue. My phone also has a black transparent popup with yellow lettering. I believe it is in factory mode. There is no data in the efs file. I think that is the overall issue right now. Does anyone have any help/ suggestions?
Click to expand...
Click to collapse
So you're on stock 4.3 and then you Odin flash 4.3 again?

buhohitr said:
So you're on stock 4.3 and then you Odin flash 4.3 again?
Click to expand...
Click to collapse
yes, basically.

Dullawolf said:
yes, basically.
Click to expand...
Click to collapse
How about do a factory reset and reflash again? Check make sure your download file is good too just in case.

buhohitr said:
How about do a factory reset and reflash again? Check make sure your download file is good too just in case.
Click to expand...
Click to collapse
did all that like three times.
did factory reset through phone os and through recovery
flashed 4.3 through odin and through kies

OK the last resort probably flash full stock with a PIT file.
Sent from my Galaxy Nexus using xda premium

buhohitr said:
OK the last resort probably flash full stock with a PIT file.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PIT file?? link?

buhohitr said:
OK the last resort probably flash full stock with a PIT file.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
n/m found it here http://forum.xda-developers.com/showthread.php?t=2586319

Dullawolf said:
n/m found it here http://forum.xda-developers.com/showthread.php?t=2586319
Click to expand...
Click to collapse
pit file didnt work either! dammit!

Anyone else have any suggestions?

Dullawolf said:
Anyone else have any suggestions?
Click to expand...
Click to collapse
So currently can you boot up your phone?

buhohitr said:
So currently can you boot up your phone?
Click to expand...
Click to collapse
well, earlier today i was able to. not so much any more. can't even get into download mode. the only thing that happens now is when i plug it into my computer it says it failed to install hs-usb qdloader drivers.
only time i can get any lights to turn on is when i pull the battery and sim card. and just the led comes on red.
looks like i have myself a paperweight :/

Dullawolf said:
well, earlier today i was able to. not so much any more. can't even get into download mode. the only thing that happens now is when i plug it into my computer it says it failed to install hs-usb qdloader drivers.
only time i can get any lights to turn on is when i pull the battery and sim card. and just the led comes on red.
looks like i have myself a paperweight :/
Click to expand...
Click to collapse
Have to try the hardbrick method (boot off the sdcard) http://forum.xda-developers.com/showthread.php?t=2581166
If you can boot up, we may have a chance to fix the efs issue.

buhohitr said:
Have to try the hardbrick method (boot off the sdcard) http://forum.xda-developers.com/showthread.php?t=2581166
If you can boot up, we may have a chance to fix the efs issue.
Click to expand...
Click to collapse
i would like to try this, but i dont want to mess up my 16gb class 10 micro sd. i tried it with a 4gb class 4 and it wont let me reformat it back, even with the utility he directed us to.

Its safe. I don't think you can mess up the card.
Sent from my Galaxy Nexus using Tapatalk

buhohitr said:
Its safe. I don't think you can mess up the card.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
will this work even if the phone isn't booting? i mean nothing at all. it wont acknowledge anything unless i pull the battery and sim card and plug it into a computer.

Dullawolf said:
will this work even if the phone isn't booting? i mean nothing at all. it wont acknowledge anything unless i pull the battery and sim card and plug it into a computer.
Click to expand...
Click to collapse
If you read the description "how to recover from a hard brick", the phone don't boot at all (appear to be dead). That because there's nothing there to boot, the SDcard mount a new boot image to assist the phone to boot. Currently you don't have much choice; 1) try the hardbrick method 2) send out for JTAG repair 3) buy a new phone or if still under warranty then send out for replacement.

buhohitr said:
If you read the description "how to recover from a hard brick", the phone don't boot at all (appear to be dead). That because there's nothing there to boot, the SDcard mount a new boot image to assist the phone to boot. Currently you don't have much choice; 1) try the hardbrick method 2) send out for JTAG repair 3) buy a new phone or if still under warranty then send out for replacement.
Click to expand...
Click to collapse
fair enough. i also bought a jig, to see if that will help. i will try the sd card thing as well.
thanks for your help. it is much appreciated.

buhohitr said:
Have to try the hardbrick method (boot off the sdcard) http://forum.xda-developers.com/showthread.php?t=2581166
If you can boot up, we may have a chance to fix the efs issue.
Click to expand...
Click to collapse
welp, this didn't work. i will be getting the jig on monday. i will try that then.

Dullawolf said:
welp, this didn't work. i will be getting the jig on monday. i will try that then.
Click to expand...
Click to collapse
You need to try couple times (4-5 times), rewrite the image to sd try again and repeat this process a few times.(each time to retry, you need to rewrite the image then try).

[Q] Nexus 5 Flash Write Failure

Hey guys,
I have a rooted Nexus 5 and on Saturday it suddenly froze and when I restarted the phone it was stuck on a boot loop. I tried to go into my TWRP recovery and it asked for a password and it says that the internal storage is 0 MB. I have tried to flash stock rom using fastboot manually and it keeps saying (remote: flash write failure). Will someone please help me on this? I can't figure out what to do.
Thank You

sounds like your internel memory went bad. youll need to replace it.

amalthomas994 said:
Hey guys,
I have a rooted Nexus 5 and on Saturday it suddenly froze and when I restarted the phone it was stuck on a boot loop. I tried to go into my TWRP recovery and it asked for a password and it says that the internal storage is 0 MB. I have tried to flash stock rom using fastboot manually and it keeps saying (remote: flash write failure). Will someone please help me on this? I can't figure out what to do.
Thank You
Click to expand...
Click to collapse
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.

Nexus 5
varuntis1993 said:
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.
Click to expand...
Click to collapse
Hey, when i do that it says (remote: failed to erase partition)
I am dying here i have been trying to fix this since Saturday.
Is there anything else I can try?
Thank You.

Nexus 5
simms22 said:
sounds like your internel memory went bad. youll need to replace it.
Click to expand...
Click to collapse
Hey, where would I be able to buy that?
Thank You

this??
http://forum.xda-developers.com/showthread.php?t=2577447
going to search .. if i'll find something will post here

amalthomas994 said:
Hey, when i do that it says (remote: failed to erase partition)
I am dying here i have been trying to fix this since Saturday.
Is there anything else I can try?
Thank You.
Click to expand...
Click to collapse
Sorry to say it seems like ur internal memory partition has gone corrupt.
U will need to send ur device back to google or to lg service center.

Nexus 5
varuntis1993 said:
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.
Click to expand...
Click to collapse
By the way, what is the actual command to flash only cache.img, just making sure I did it correctly.

amalthomas994 said:
By the way, what is the actual command to flash only cache.img, just making sure I did it correctly.
Click to expand...
Click to collapse
Fastboot erase cache
Fastboot flash cache cache.img

Nexus 5
enricocid said:
this??
http://forum.xda-developers.com/showthread.php?t=2577447
going to search .. if i'll find something will post here
Click to expand...
Click to collapse
Hey, thank you, I tried that but this is what i get when i get to the adb part
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name
/userdata

amalthomas994 said:
Hey, where would I be able to buy that?
Thank You
Click to expand...
Click to collapse
no no no.. get your whole phone replaced. you wont have any issue doing it, its a known issue.

simms22 said:
no no no.. get your whole phone replaced. you wont have any issue doing it, its a known issue.
Click to expand...
Click to collapse
But since it is rooted and i can't relock the bootloader, will they replace it?

amalthomas994 said:
But since it is rooted and i can't relock the bootloader, will they replace it?
Click to expand...
Click to collapse
yes. if you bought it through google, they will generally replace rooted phones especially if its a hardware issue(has nothing to do with root). and if its not google, they wont boot it up anyways(i dont think).

amalthomas994 said:
But since it is rooted and i can't relock the bootloader, will they replace it?
Click to expand...
Click to collapse
did you try flashing userdata and cache via fastboot?

Nexus 5
simms22 said:
yes. if you bought it through google, they will generally replace rooted phones especially if its a hardware issue(has nothing to do with root). and if its not google, they wont boot it up anyways(i dont think).
Click to expand...
Click to collapse
Ok, thanks a lot, that atleast gives me some kind of hope lol

Nexus 5
samersh72 said:
did you try flashing userdata and cache via fastboot?
Click to expand...
Click to collapse
Yep, no luck, keep getting write errors
thanks anyways

Nexus 5
Hey everyone,
I am able to get to adb and fastboot, so is there any way I can fix the corrupted files or anything?

amalthomas994 said:
Hey everyone,
I am able to get to adb and fastboot, so is there any way I can fix the corrupted files or anything?
Click to expand...
Click to collapse
no, your storage is physically broken.

Nexus 5
simms22 said:
no, your storage is physically broken.
Click to expand...
Click to collapse
Ok thanks for the reply.
But WOW.. how can something like that even happen..
I know it was not a mistake I did

amalthomas994 said:
Ok thanks for the reply.
But WOW.. how can something like that even happen..
I know it was not a mistake I did
Click to expand...
Click to collapse
its actually a sorta common issue with the nexus 5. at least ive seen more than enough nexus 5 here with that issue. its a hardware issue, nothing you did.

Adb update! Plz help stuck in recovery! [Q&A],[SOFTBRICK/BOOTLOOP], QTAQZ3

Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk

SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49

samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse

samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk

ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse

Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .

ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk

samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse

ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!

samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?

samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk