Database Info

stuck on Google logo

After updating around 20 apps (altogether ), I noticed the phone was not functioning normally so I tried to reboot it but now it is stuck on Google logo. I've never unlocked the phone nor used any custom roms. I'm on the latest stock rom 2.3.4
I tried removing the battery and putting it back but didn't work. Vol. up + power and then Recovery didn't work either. It gives me a triangle with ! in it and stops right there.
I also tried the USB Jig that forces the phone into downloading mode but it gave me a screen that asks (Unlock bootloader?) with some warnings but I don't know how to accept that. Niether Vol buttons nor Power button worked there
I didn't want to mess up with the phone until I hear from you guys. Please help

up.......

You might have to actually root it or use the Samsung exe back to factory. That is if you don't want to mess with it because if I ware in your position I'd be going back for a new phone. You did nothing wrong and you have 1 year warranty on it.

FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.

matt2053 said:
FYI, the triangle with ! actually is recovery. The UI is hidden until you hold power and press vol down.
Click to expand...
Click to collapse
Thanks man, I didn't know about that
Is wiping the data (factory reset) going to delete my stuff stored on my SD card? like pic., music, vid. etc?
and do I need to actually wipe the data or will wiping the chache only work?

Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz

frutelaken said:
Factory reset reverts your phone back to the way it was when you got it.
That means all your account settings, device settings, installed applications etc are gone. Everything stored on your SD card will remain there - it's a different storage. The good thing about our Google phones is that you only have to login to Google once and all your stuff is back.
You can try wiping the cache first and see if that works, it won't harm anything. But if that doesn't work, I'm sure a factory reset will.
Good luck.
Greetz
Click to expand...
Click to collapse
Thanks a lot. I already tried wiping the Cache but it didn't work. I guess I'm going with the factory reset now
Thanks again

the factory reset didn't work !
still stuck on Google logo
any advice?

farisallil said:
the factory reset didn't work !
still stuck on Google logo
any advice?
Click to expand...
Click to collapse
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?

Try doing a hard reset.

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help

farisallil said:
I'm not an expert in these things ... is there any post I can follow to do the things you talked about? I'm not sure that I have all the drivers needed on my pc
I do appreciate your help
Click to expand...
Click to collapse
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App

matt2053 said:
One thing you should consider is just returning the phone, especially if you never flashed or rooted or unlocked bootloader.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I would if I was in the States

just unlock it and flash a nice CM7 with Trinity on top
Here's a rooting guide: http://forum.xda-developers.com/showthread.php?t=895545
There's another guide out there for the i9023 (European version).

GchildT said:
Can you connect your device to your computer via USB and start "adb logcat" at the Terminal/Command prompt? Does it give you any kind of readout at all?
Click to expand...
Click to collapse
No. The device doesn't even show up when I type "adp devices"
Is there anything else I should try?

Thanks
I can perform things with Fastboot
I don't want to root or unlock the phone. Is there anything else I can do?
I tried typing Fastboot update update.zip after downloading the stock rom update 2.3.4 and putting it in the SDK tools directory but it gave me the msg "faild to upload update.zip"

Try to reset with Odin.

I think i might have bricked.....

My infinity. I was foolishly in a hurry to make sure I was going to be able to receive the JB update and downloaded the build.prop that was posted last week in the ota thread. I'm so retarded that I forgot that build.prop was for .26 and not 30. So I copied it into system/ and rebooted.
Now all it does is sit at the 1st asus screen and nothing else.
I'm rooted and not unlocked. Iv'e tried factory resetting, hard reset, and nothing works. So it looks like I got an expensive paper weight now.
Any recommendations? If so it would be really awesome.

e?
adb push the correct file? might have to root again first.
i know its tempting but wiping data when you can't boot is never a good idea.

I DID THE SAME THING!!! in fact I think he linked me to it :/ lol
any help PLEASE!!

lafester said:
adb push the correct file? might have to root again first.
i know its tempting but wiping data when you can't boot is never a good idea.
Click to expand...
Click to collapse
I'm in the process of downloading the .30 update from asus's website then i'm going to go from there.
darkreaper476 said:
I DID THE SAME THING!!! in fact I think he linked me to it :/ lol
any help PLEASE!!
Click to expand...
Click to collapse
Sucks don't it! I hope we can recover it.

Im new to the asus' is there any way we can adb into these things via stock recovery mode? any way to get that build.prob fixed? I can take it back but I DONT WANNA.. lol
and what would be the correct build.prop to use? I still have my modified one on the system renamed but.......

Ok, Iv'e tried the "adb devices" from the command prompt and i can't get get my computer to recognize the infinity. Iv'e downloaded android sdk and got it up and running but no dice. I don't know what else to do
If anybody has any advice or any suggestions that me and darkreaper476 can do, i will love you forever. :nohomo:

Nevermind...

I can get to where it says:
reboot system now
wipe data/factory reset
wipe cache partition
But i can't get my computer to recognize the tablet.

This might be a stupid question but I'll ask it anyway. Have you installed the proper drivers for ADB to recognize the TF700?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Biohazard0289 said:
This might be a stupid question but I'll ask it anyway. Have you installed the proper drivers for ADB to recognize the TF700?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
would ADB have recognized it recovery mode? Even it it does the ab doesnt give you enough time to work... 10 seconds before it attempts to reboot. what good is adb if the device isnt in an adb friendly mode? IDK... I'm sick of trying to fix these stupid little issues.. I just returned it, sure I lost some photos and files (I HATE INTERNAL STORAGE) but F it... That why I bought the warranty...
thanks anyway

Something similar to me happened when I was restoring what I thought was my original backup of the build.prop file. Now I get stuck on the Asus screen. Reseting cache, delvik, user data, etc doesn't help.
Does anyone have instructions on how to setup ADB, TF700 drivers, and how to take any firmware and flash it that method, in a simple set of instructions that doesn't require a nuclear physics degree?
I would rather not have to RMA this thing and wait a month or more to get a new one ...

1stx2 said:
I can get to where it says:
reboot system now
wipe data/factory reset
wipe cache partition
But i can't get my computer to recognize the tablet.
Click to expand...
Click to collapse
You don't need adb to recover your device, just follow my How-To guide from the General forum and you should be good but you need an external MicroSd card to do it.

Pretoriano80 said:
You don't need adb to recover your device, just follow my How-To guide from the General forum and you should be good but you need an external MicroSd card to do it.
Click to expand...
Click to collapse
This assumes that I'm able to get to the recovery. I was able to at one point, but now it won't. In other words, if I hold Pwr+VDown, wait till the text, and then release Pwr+Vdown, and then press VUp, it says booting recovery image, signature blah blah, shows an android guy with his chest open and a red exclamation mark. That screen shows for a few minutes, after which I get a reboot and its back to the Asus logo. Is recovery hosed now? If so, now what the hell do I do? Is it bricked for good?

spinaldex said:
This assumes that I'm able to get to the recovery. I was able to at one point, but now it won't. In other words, if I hold Pwr+VDown, wait till the text, and then release Pwr+Vdown, and then press VUp, it says booting recovery image, signature blah blah, shows an android guy with his chest open and a red exclamation mark. That screen shows for a few minutes, after which I get a reboot and its back to the Asus logo. Is recovery hosed now? If so, now what the hell do I do? Is it bricked for good?
Click to expand...
Click to collapse
That's the stock recovery, what happens if you press Power button once while you are at the "dead android" screen?
Edit: in your case Restore with Stock recovery should do the trick.

[Q] Bricked TF300TG

Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!

jak4kaj said:
Hello all,
I seem to have really soft bricked my TF300TG. I've now run out of ideas and maybe someone in here can help.
The following happend: I wanted to update my rooted TF300TG from running JB (CleanRom 3.0.4) with Bootloader ww_epad_10.4.3.9 to the current stock Rom from ASUS ( V10.6.2.6 ). I did unzip the zip from ASUS once and used the resulting zip for the flash.
I attemted this via Method 3: TWRP v. 2.5.0.0, following this guide (http://forum.xda-developers.com/showthread.php?t=2187982), guess I should have read the whole thread, not just the first 20 pages.
What happend was, that during the flash in TWRP I got an error with no error message. I tried to flash again for three times with the "same" error. Thats when I panicked and rebooted the device.
Since then its sitting here, just showing the ASUS logo and doing nothing. I think I understand why its doing nothing since I have still the old bootloader v 10.4.3.9 but a new 4.2 Stock ROM (albeit maybe damaged).
Sadly I have also had no success communicating with the device via ADB or Fastboot.
I still can access the bootloader menue which shows 4 icons: RCK, Android, USB and Wipe. But: the volume up key is not working (did work in Android though) and the volume down key traverses the item entries. So I have no way to select USB which should put me into fastboot mode.
Does anyone have any idea? Otherwise I'm declaring this my last Android tablet (loved it but it didn't quite live up to expectations, Tegra 3 just sucks) and move on.
Thanks for reading!
Click to expand...
Click to collapse
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster

Buster99 said:
Try resetting the device (the little hole beneath the volume rocker and try to get to fastboot. there is no real reason other than broken PITs or trashfiles in /misc that should prevent you form getting fastboot.
also read my post here (or better the threat)
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
buster
Click to expand...
Click to collapse
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4

jak4kaj said:
Hi buster,
thanks for the reply. Sadly I can't seem to enter fastboot since "fastboot erase system" stays at "waiting for device" when I reset the device with a paper clip and press the volume down button.
I'm trying this on linux but that should be a plus versus using windows.
Thanks again
jak4
Click to expand...
Click to collapse
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster

Buster99 said:
yeah - linux sometimes is less of a nightmare when it comes to fastboot commands - but remember to install adb and fastboot
gl
Buster
Click to expand...
Click to collapse
Yes I have fastboot and adb installed. They come with the Android SDK which I need for work.
jak4

I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!

coppervines said:
I have the same problem. Difference is that I did a reset after a failed install of CM11. Stuck at ASUS splash. Cannot access recovery or any other option that was previously available. Nothing is detecting the device as it sits...Tried Ubuntu, Win 7, Win 8.1. I have tried installing all drivers I could find, even tried installing as legacy device, but all drivers give an error that device cannot start. Did A LOT of searching around, and it seems to come down to the tablet not being detected by PC in the state it's in. Seems like there is a lot of help out there for folks that can get their computers to at least see the device.
Would die for some help!
Click to expand...
Click to collapse
what recovery did you use for installing cm11?

Buster99 said:
what recovery did you use for installing cm11?
Click to expand...
Click to collapse
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.

coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster

Buster99 said:
yeah well with an old recovery kitkat gets you a brick - try to get it somehow to fastboot and you should be able to get it working again
gl
buster
Click to expand...
Click to collapse
I would hate to think that my USB cable could be bad...it's been a LONG time since its done anything other than charge. Just need the pc to see the damn thing. ANY insight would be helpful.

APX
I was able to get to APX mode with the universal drivers (Vol +reset)...looking around to see if anyone else has had success. I never installed Nvflash...

in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
in the other threat a guy just needed a working cable to get it to work. it's a pain with asus and the cable
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What thread? Not sure I understand what you mean...

http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app

Buster99 said:
http://forum.xda-developers.com/showthread.php?t=2179759
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first

coppervines said:
Since i have apx access, i'm assuming the data side of the cable is working...plus, without being able to get into adb/fastboot on the tablet a new cable would be useless. Thinking about getting a mobo on ebay...one for 50 and one for 75$ i think. will have to get wife's approval first
Click to expand...
Click to collapse
So I'm assuming there is no solution to this problem without sending it to ASUS or getting a new Motherboard?
I'm in the exact same position...

coppervines said:
CWM from probably close to a year ago. I attempted to use Rom Manager to flash a newer recovery that would work with CM11, and got stuck in a bootloop. Then I stupidly did a factory reset from boot menu . Wish there was a way around this...and I think I could work some magic if I could get a computer to detect the brick.
Click to expand...
Click to collapse
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.

ebildude123 said:
Wipe data from the bootloader erases everything, if you don't have nvflash blobs I think you're done for.
Click to expand...
Click to collapse
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

Buster99 said:
"bootloader wipe data" soft brinks your tab.
always use custom recovery or fastboot to wipe the tf300t.
otherwise you need to erase all partitions and reflash recovery and start from scratch. assuming that fastboot still works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Boot loader wipe is a hard(ish) brick unless you have nvflash blobs since all you have access to is apx mode, no boot loader, no recovery, etc.
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4

not necessarily, I did it for cm10.1 (drunken flashing not advised ) and i don't have an NV backup.
and i had fastboot to work with.
but things may have changed since then.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

[Q] ADB Sideload

I'm attempting to get my Memo Pad 8 fixed. I've got it into a bootloop by modifying build.prop and the only way to fix it is to change it back. I used a DPI changer app, and I felt that I was close to success yesterday, but may have been farther than I'd hoped. I went into recovery and when I used adb devices I got a set of numbers and then the word "sideload". A few commands worked. At the beginning, I attempted "adb pull /system/build.prop C:\Users\user\Desktop", replacing user with my computer name, and got "error: closed". Eventually, I did some things and then got that long list of suggested commands. I don't know what I'm doing wrong. My tablet is able to power on but I can't get into adb because I attempted at a factory reset before all of this. Can someone help me, is there anyway to change build.prop, or am I done for?

Any help?

@Klamman What recovery?

AJM-hackers said:
@Klammanmann What recovery?
Click to expand...
Click to collapse
I'm using the stock Memo Pad 8 recovery. I'm a newbie when it comes to these things. I'm using Android system recovery <3e>, recovery system version 4.2.31 apparently.

Klamman said:
I'm using the stock Memo Pad 8 recovery. I'm a newbie when it comes to these things. I'm using Android system recovery <3e>, recovery system version 4.2.31 apparently.
Click to expand...
Click to collapse
Maybe root is too much freedom for me to handle xD
(I am still in need of help )

Error: Closed
Nevermind... I'm still getting error: closed... please don't tell me that my situation is that hopeless... :'(

Klamman said:
Nevermind... I'm still getting error: closed... please don't tell me that my situation is that hopeless... :'(
Click to expand...
Click to collapse
Don't stress, it can be fixed! When booting hold the power button and Vol down key (it might be up I'm not sure). This will show you three icons (or maybe four). Go to the one saying factory reset/wipe data using volume down, and select it using vol. up. It''ll wipe everything and return everything to stock

AJM-hackers said:
Don't stress, it can be fixed! Your problem is that you need to install TWRP.
Click to expand...
Click to collapse
I'm asking some others for a copy of their build.prop (memo pad 8)
If I have this, would I need to use TWRP? I'd rather not change my recovery, as I've still got warranty for the place I got it from.

Okay, I've got the file.
Now, uhm, what do I do next?

Also, a factory reset is not deep enough, the system files have been edited, namely build.prop

Klamman said:
Also, a factory reset is not deep enough, the system files have been edited, namely build.prop
Click to expand...
Click to collapse
Did you at least attempt a full wipe/ factory reset? build.prop is in /system which it wipes. To use that file remove the .txt extension, go to recovery, mount system(which I'm pretty sure stock recovery can'' do) and adb push the new file.

AJM-hackers said:
Did you at least attempt a full wipe/ factory reset? build.prop is in /system which it wipes. To use that file remove the .txt extension, go to recovery, mount system(which I'm pretty sure stock recovery can'' do) and adb push the new file.
Click to expand...
Click to collapse
Yeah, I attempted multiple wipes which is why my usb debugging was disabled. I'm really new to adb, how do I mount /system? I've tried multiple commands, but most of them come up to error: closed.

Klamman said:
Yeah, I attempted multiple wipes which is why my usb debugging was disabled. I'm really new to adb, how do I mount /system? I've tried multiple commands, but most of them come up to error: closed.
Click to expand...
Click to collapse
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.

AJM-hackers said:
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.
Click to expand...
Click to collapse
http://www.smartmobilephonesolutions.com/content/stuck-android-system-recovery
If you go to that link, the first photo shows you what my recovery looks like.
Is there a specific forum for the Memo Pad 8?

AJM-hackers said:
I meant the factory reset option not wipe, as I said dig through recovery options I really don't think it'll be there though. BTW I think you should go to your respective forum on XDA I only have an ASUS TF700 and can't really help you unless you take pics of your bootloader options and recovery options and upload them here.
Click to expand...
Click to collapse
I'm not 100% sure what my bootloader is... is it the first thing that shows up when I hold down vol+ and power? When I do that, I get "No Command", then I have to do a series of taps (one quick power tap, then one quick power and vol+ tap) to get into the place where I can choose what to do.

Klamman said:
I'm not 100% sure what my bootloader is... is it the first thing that shows up when I hold down vol+ and power? When I do that, I get "No Command", then I have to do a series of taps (one quick power tap, then one quick power and vol+ tap) to get into the place where I can choose what to do.
Click to expand...
Click to collapse
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb

AJM-hackers said:
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb
Click to expand...
Click to collapse
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!

Klamman said:
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!
Click to expand...
Click to collapse
Do you still have the problem? If so tell whoever it is to make a system dump of the firware, it;s very straightforward, it's like the first result on Google. Cheers, you're almost there!

Klamman said:
Originally Posted by Klamman View Post
"But it seems that, due to the Memo Pad 8's limited recovery settings, a full ROM is required to unbrick my device.
If anyone can provide the full ROM for the stock Memo Pad 8, I'd be forever grateful, and I'm sure other people would be as well!
If you need instructions, I can provide them as well
Thank you so much in advance!"
I may be able to help. Am I just dd'ing partitions?
Is this was he has to do? It seems that my hopes of reviving my Memo Pad may come to reality!
Click to expand...
Click to collapse
As I've already written a how to in german,I think I could help you:
Obviously there is a stock rom indeed, but you have to modify it (dl link is saved as a txt file in the attachments, because i'm not allowed to post URLs
After you have downloaded it you open it with 7zip and navigate to X:\UL-K00L-WW-2.0.0.4-user.zip\META-INF\com\google\android\
and push the modified updater-script to there(it is attached as a .txt file but remove the extension, otherwise it won't work) .
i hope i could help you

AJM-hackers said:
Yes, when you first power on using vol+pwr that's it, can you take a pic of this "no command". Did you do data/factory reset in recovery? I'm you beg someone else for a rom.zip you can adb sideload it using the option that says install from adb
Click to expand...
Click to collapse
if there's a "no command" you're already in the recovery, just press power and vol+ and then it shows you the recovery.
I recommend installing cwm although, you're not able to update OTA anymore, but its way better than the stock recovery

Nexus 5 bootloop, stuck in Rom intro - Don't know how to connect it to my pc

First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:

Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw

Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird

It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.

No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!

audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad

ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.

audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked

ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.

audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great

It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.

hmm not a bad idea at all. Thank you!