Related
So ive had my galaxy s 2 for a few months now, downloaded hundreds of songs, taken near a thousand photos, and yesterday the digitizer/lcd was shattered after being sat on. I can't replace this phone, and my parents who own the contract didn't purchase insurance for it. I am nearly broke, and the repair costs for this part is over 200$, and my parents refuse to pay for this. All I need to do is copy all of the files from my phone to my computer, but i cannot enable mass storage to access the pictures/music on the internal storage because the screen is out. Does anyone have an idea as to how I could fix this, or move the files off of the phone? A thousand thanks to whoever could help me in this/:
1) Questions belong in Q&A.
2) You can probably pull the files off your phone using ADB on your PC despite the screen being broken, as long as the phone boots.
I'm not going to tell you how to do this because it is detailed, somewhat complicated & is a very steep learning curve if you've never done it before. Do a Google search with "broken phone backup files with ADB" with XDA appended to your search terms & you should get a veritable mountain of results (I did).
Unfortunately, if you're looking for an easy way to do this, there isn't one. It's going to take a fair bit of work on your part if you really want those files.
Good luck.
MistahBungle said:
1) Questions belong in Q&A.
2) You can probably pull the files off your phone using ADB on your PC despite the screen being broken, as long as the phone boots.
I'm not going to tell you how to do this because it is detailed, somewhat complicated & is a very steep learning curve if you've never done it before. Do a Google search with "broken phone backup files with ADB" with XDA appended to your search terms & you should get a veritable mountain of results (I did).
Unfortunately, if you're looking for an easy way to do this, there isn't one. It's going to take a fair bit of work on your part if you really want those files.
Good luck.
Click to expand...
Click to collapse
Can't he just adb pull /sdcard/ ??? I've used adb pull /sdcard/DCIM/ to pull the whole dcim directory with all files in it.
Sent from my GT-I9100 using xda premium
Yep. Absolutely.
I was trying to convey that using ADB tends to be a bit of a stretch for n00bs & requires a bit of thought/reading/effort. Plenty of people find it difficult to get their head around it, and I'm not about to answer 20 questions about the process.
kyleforge said:
Can't he just adb pull /sdcard/ ??? I've used adb pull /sdcard/DCIM/ to pull the whole dcim directory with all files in it.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
DaltonCope said:
So ive had my galaxy s 2 for a few months now, downloaded hundreds of songs, taken near a thousand photos, and yesterday the digitizer/lcd was shattered after being sat on. I can't replace this phone, and my parents who own the contract didn't purchase insurance for it. I am nearly broke, and the repair costs for this part is over 200$, and my parents refuse to pay for this. All I need to do is copy all of the files from my phone to my computer, but i cannot enable mass storage to access the pictures/music on the internal storage because the screen is out. Does anyone have an idea as to how I could fix this, or move the files off of the phone? A thousand thanks to whoever could help me in this/:
Click to expand...
Click to collapse
Visit the following threads to learn how to replace your screen.
http://forum.xda-developers.com/showthread.php?t=1253969
http://forum.xda-developers.com/showthread.php?t=1175772
Usb debugging...?
kyleforge said:
Can't he just adb pull /sdcard/ ??? I've used adb pull /sdcard/DCIM/ to pull the whole dcim directory with all files in it.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I think usb debugging should be turned on before you can use adb...and its not on by default
DaltonCope said:
So ive had my galaxy s 2 for a few months now, downloaded hundreds of songs, taken near a thousand photos, and yesterday the digitizer/lcd was shattered after being sat on. I can't replace this phone, and my parents who own the contract didn't purchase insurance for it. I am nearly broke, and the repair costs for this part is over 200$, and my parents refuse to pay for this. All I need to do is copy all of the files from my phone to my computer, but i cannot enable mass storage to access the pictures/music on the internal storage because the screen is out. Does anyone have an idea as to how I could fix this, or move the files off of the phone? A thousand thanks to whoever could help me in this/:
Click to expand...
Click to collapse
THAT'S whatcha get for not having a backup of your SD card, which is just like having a backup of your PC's hard drive.
But yeah, your ONLY option to the best of my knowledge is to do an adb pull:
adb pull /sdcard/ "where these quotes are you put the name of the folder where you want all that stuff offloaded to"
So since you didn't research before you screwed up then you will have to research now to learn how to use adb and how to enable it without the phone being on
good luck newbie
cdzo72 said:
THAT'S whatcha get for not having a backup of your SD card, which is just like having a backup of your PC's hard drive.
But yeah, your ONLY option to the best of my knowledge is to do an adb pull:
adb pull /sdcard/ "where these quotes are you put the name of the folder where you want all that stuff offloaded to"
So since you didn't research before you screwed up then you will have to research now to learn how to use adb and how to enable it without the phone being on
good luck newbie
Click to expand...
Click to collapse
Go easy on him man, we were all learning at some point
Sent from my GT-I9100 using xda premium
DaltonCope said:
So ive had my galaxy s 2 for a few months now, downloaded hundreds of songs, taken near a thousand photos, and yesterday the digitizer/lcd was shattered after being sat on. I can't replace this phone, and my parents who own the contract didn't purchase insurance for it. I am nearly broke, and the repair costs for this part is over 200$, and my parents refuse to pay for this. All I need to do is copy all of the files from my phone to my computer, but i cannot enable mass storage to access the pictures/music on the internal storage because the screen is out. Does anyone have an idea as to how I could fix this, or move the files off of the phone? A thousand thanks to whoever could help me in this/:
Click to expand...
Click to collapse
As MB said, if you really want them it's going to be hard work.
3 other possible ways to do it:
1) Easiest way without adb - connect to your TV via HDMI/HML cable. You can now see your screen on the TV. If touch is somehow still working then copy the files from the internal card to an external one. If touch doesn't work, this won't help. Unless you already have Bluetooth on and have previously paired with a Bluetooth mouse.
2) Very messy way - If you've got a very good friend with an s2 who will allow you to swap motherboards over then copy your stuff to PC. Doubtful though.
3) Messy way - If you don't have an sd card or access to one, flash an ics rom like lpq with Odin. Yes I know you can't see the screen but boot into download mode using a jig or the 3 button method. Just hold them together for a while. Then flash once Odin detects the phone. You will lose your apps but music, pics etc will remain.
The reason I say ics is that when I was on it, it automatically displayed the sd cards on pc without me having to select / touch anything.
But I believe USB debugging may need to be activated, but not 100% sure. If not, your in luck.
If it does, connect via HDMI to your TV. That way you can see the screen and check the debugging option, assuming touch still works. Then connect to PC and copy/paste.
Sent from my GT-I9100T
The best and efficient way is to flash a kernel with recovery that can mount your internal and external cards.
Just ask someone who uses similar kernel recovery to make note of the number of.key press and direction required to mount your SD via recovery and follow the same for your mobile and now you can copy all the files you wwant
Sent from my GT-I9100 using xda premium
Thanks everyone, I've used adb in the past with my nexus one. I just tried using it on my phone but it seems like my debugging isnt right so I cant use that. I have CWM flashed to the kernel (not sure if thatd make much of a difference??) Anything else i could possibly try out?
DaltonCope said:
Thanks everyone, I've used adb in the past with my nexus one. I just tried using it on my phone but it seems like my debugging isnt right so I cant use that. I have CWM flashed to the kernel (not sure if thatd make much of a difference??) Anything else i could possibly try out?
Click to expand...
Click to collapse
You can try doing it in recovery. But you'll probably need to mount the internal SD card before you can pull from it.
1. boot to recovery
2. plug in your phone, start adb shell
3. su (if you don't have the "#" prompt)
4. mount /emmc (if you are interested in what is on the internal SD card. /sdcard is your external SD card while you're in recovery)
At this point, /emmc should show your internal SD contents. You should be able to exit from the adb shell and do an adb pull on /emmc/<whatever folder>
EDIT: BTW, I just tested this on my phone. I have CWM recovery installed via Siyah, turned USB debugging off, rebooted to recovery, and did all this, and was able to pull multiple files off my internal SD.
why dont u just buy the parts cheap off ebay that u need ?? and install them urself ... if not ... ull hav to do as every1 else has said and pull those files :|
Welp, after spending over 26 honest-to-God hours researching a "cure" for this, I am still without a solution. I hope a kind soul will be able to guide me to the light, because I have been unable to find it on my own.
I am going to try to be as through as possible, if for nothing else than doing a mental checklist to see if I missed some obvious step along the journey. Also, maybe a keen observer will be able to spot what I'm doing wrong.
So,
My Asus Prime is bricked. I'm stuck on scenario 3 (according to this post:http://forum.xda-developers.com/showthread.php?t=1514088&)
In chronological order, here's what happened:
1. I'm running Virtuous Prime 1.0
2. I flash ClockworkMod Recovery Touch v5.8.1.8
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
5. I flashed a new ROM, then hit 'reboot system now'
6. I'm stuck at the Asus logo screen; Android won't boot.
I am able to access recovery and activate Fastboot mode; definitely scenario 3.
Then, also in chronological order:
1. I restarted the tablet, pressed the up volume key and accessed the other menu with 3 options
2. I hit the 'wipe data' option
3. Try to boot Android
4. Still stuck at the 3 option screen
From what I read, this situation is likely the result of clockworkMod Recovery flashing a bad kernel. Supposedly, it can fixed by flashing a 'good' kernel via fastboot, which requires both a "stock kernel" and a more recent clockwork mod recovery image.
I downloaded the SDK package and downloaded pretty much everything, including the USB drivers. I downloaded a stock kernel called stock_9.4.2.21_kernel-signed and a CWM recovery image and placed them inside the "tools" folder.
I opened a command window and while having the tablet plugged in, typed 'adb devices'. I get 'List of devices attached' but then a blank space.
Here's what happened next:
1. I re-plugged in the tablet in Recovery mode to my AMD X64 Windows 7 PC and got an "USB device not recognized" message.
2. I went to Device Manager and under "Universal serial bus controllers" I see a yellow triangle mark besides an "unknown device" option.
3. Right click on "unknown device" and try to update the drivers manually using the Universal_Naked_Driver_Beta_0.6.1
4. When I select the folder in which the drivers are located Windows gives me a message of "the best driver software for your device is already installed". Back to step 3.
5. I try "let me pick from a list of device drivers on my computer" and hit "have disk option"
6. Upon choosing the android_apxusb file inside the universal naked drivers folder, I get the following error: "the folder you specified doesn't contain a compatible software driver for your device (...) make sure it is designed to work with Windows for x64-based systems."
7. Try again this time choosing file android_apxusb; same error.
I heard that some Windows 7 x64 users are having issues installing drivers; that may be my case too. I, however, don't have access to any other Window or Macs or Linux PCs in my house. Still, if this is the issue, then I might try redoing things in a different PC at a friend's house or something.
Bottom line? I think I know what to do, but I can't install the universal naked (nor the official Asus Prime) drivers. What now? Is there an easy fix for Brick scenario 3?
I have read God knows how many discussions on the subject, but I haven't been able to find a solution to my issue. I got no support from Freenode #asus-transformer; some ops were even downright rude. Any help is greatly appreciated.
For what is worth, I'll be donating $50 to whoever is able to help me navigate through this issue and get my tablet back and running.
Thanks again for reading this far.
TL;DR: I bricked my Prime and I'm stuck in scenario 3. I will donate $50 dollars to whoever can help me unbrick it.
Hey,
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Go to the freenode IRC Channel "#asus-transformer" on Freenode (http://webchat.freenode.net/?channels=asus-transformer) and ask for help like described in the unbrick thread!
Greetz
Edit: No need for donate!
hanzo001 said:
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
Click to expand...
Click to collapse
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Thanks for your answer; I'll answer yours
djmcnz said:
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
Click to expand...
Click to collapse
1. Yes, in that order; I backed an empty ROM
2. No, I don't have a valid nandroid backup (go figure; just this single freaking time I forgot to backup before wiping data/cache/dalvik cache)
3. No other ROM on my device. I had a new ROM when I performed the flashing, but when I got to the point where I hit "deleate data" in the 3-option menu, I lost everything on the SD card
4. When I wipe and reflash I'm stuck on the same loop. Maybe flashing a 'good' ROM will fix it; the issue is, my PC doesn't know what I'm plugging in when I connect the tablet to it.
Thank you for your support
Thank you, I'll try a Live CD. I'm downloading now even as we speak.
When that's finished, I'll grab the Linux files.
I guess that sorts of confirms my hypothesis that my main issue is with Windows... *sigh* WINDOWS!
I tried getting help from freenode's #asus-transformer in the past, but... lets say that on the overall my experience could have been better. I'll try again later tonight, where hopefully I'll be able to talk to RaYmAn, a volunteer in the original Diamonback post who is offering supports to users in my specific situation.
By the way, thanks for pointing me with a clickable link to the IRC chat; I've never used IRC before in my life, and getting it to work, dumb as it may sound, took me quite to figure out. Thank you again for your help and support!
chrischdi said:
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Click to expand...
Click to collapse
Thank you for your answer. It is really nice to have a helpful person around; Like I mentioned in my op, my experience on freenodes' #asus-transformer chat was a bit... discouraging. I figured most would want some form of payment for their time, but here you both are, proving that there is kindness in this world.
I'll address your comments:
1. I did wipe /System; after NOTHING I tried on recovery worked, I did manual wiping of everything, trying to boot each time; similar results.
2. I do not have a good ROM on the memory card. Before doing the 'wipe data' from the 3-option menu, re-flashing a good ROM did no good nevertheless. From here is where I started suspecting that it was the fault of CWM not flashing a proper kernel.
3. I tried the advanced restore as well, an like in #1, I tried rebooting each time, just to make sure it would work. But it didn't.
Thank you again for your support. It feels great to know there's someone backing you up out of the goodness of their heart.
Right now I'll try to redo my steps from a Live CD Linux environment; hopefully that'll work. Freaking Windows...
Doktaphex said:
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Click to expand...
Click to collapse
Thank for your support, guys
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
hanzo001 said:
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
Click to expand...
Click to collapse
Hope it works out for the best, life is better with a little Nix in it.
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
You cannot use an external SDcard with any version of CWM for the Prime.
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the thought. I tried that too; for some reason, ClockworkMod Recovery won't read the SD card at all!
Linux
[Update]
In general, this could be going better.
I finally got Ubuntu.
I plugged in the tablet while (the tablet is) on recovery mode, and nothing happens.
I was expecting a pop-up menu, or a notification somewhere acknowledging that I connected a device to the PC, but nothing. I'm just going to assume that Linux somehow knows.
I then downloaded the Android SDK for Linux, unziped, and there's no executable file inside. I'm supposed to download the rest of the file via the terminal, apparently, but this one doesn't work like its Windows counterpart either, so I have no clue what to do now.
Jesus...
Bottom line: I'm in Linux, I downloaded the Android SDK, the universal naked drivers and a stock kernel. Now what?
Try to get ADB running in the recovery mode.
In the files of ViperMOD are the executables. Just open up a console / shell and go to the directory via the "cd" command.
Then in the ViperMOD directory execute "sudo ./adb shell" to try the adb connection.
If the adb connection is ok, mount the sdcard via Recovery Menu and then push a file / rom to the sdcard.
For example with the command:
"sudo ./adb push /media/rom.zip /sdcard/"
(I don't know if this are the correct paths.)
Greetz
Thank you, Chris.
While on the terminal, I'm inside the viperMOD folder. Whenever I try execute "sudo ./adb shell" I get this: "sudo ./adb: order not found"
The tablet is plugged in, and in recovery mode.
I haven't installed Java nor the Android SDK because I haven't figured out a way to do it --why can't Linux be double-click action-oriented? *sigh* Anyway, does not having those things installed have something to do with the answer I'm getting from the Terminal?
If so, how in the world do I install them?
I'm never using Touch Recovery again, my word.
Thanks in advance.
Hey,
are you sure that there is "order not found?"
Try the command "ls" to see what files are available. If there is one, called "adb" you are in the right directory. If there is no "adb" then you have to move to the right directory.
Maybe you could try a "chmod +x adb" first and then execute "sudo adb shell" or such if you are in the right directory.
This is going to sound like a stupid question and sorry if it does. but you can access clockwork still right? what happens when you try to flash back your backup? This is important because I had an error sort of like yours that no one could solve here want to make sure its what happened to me. When i tried to restore the original rom it would get to the part where it was restoring data partition and then error on me reading file or something like that. If thats what you see i know the answer. or at least how i fixed mine.
push a rom
Read NIlsonf post about how to adb push a rom to cwm, you get a stock rooted rom
And adb push the blob file, then run the dd command, unmount staging mount data.
This is what fixed mine, and it looks like it fixed nilsonf's also.
Was this ever resolved? I have the same issue and it looks like I've been through many of the same steps as you've gone through. If you were able to do anything to fix it, please let me know.
I would even up the reward to $100.
Just thinking
Why dont you get someone elses CWM backup and adb push it to the device and restore it from that?
Hi anyone and everyone,
So let me start by saying I am really in need of help two months ago i had a flawless CM7 Nook Tablet 16GB that worked like a dream and now i have a useless brick and im about to through it away the problem i have can be viewed here............ http://www.youtube.com/watch?v=0BAZ...&playnext=1&list=PL05B917C134DF82A7........It gets stuck on the white screen everytime i was able to boot into CWM with a bootable sd card and I have tried to flash many roms from there and yet every time i get stuck at white screen please help help help help!
WOW!!!!!!!!!!!!!!!!!
Thanks in advance to all that reply!
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
ShinnAsuka said:
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
Click to expand...
Click to collapse
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
and as to where I am now......everytime I turn on my nook it gets stuck at the white screen with the cardboard box.....unless I use a bootable sd card which then I have tried to flash old roms new roms and I get nothing
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
Your partitions are : shot / corrupt / messed up. They "really" gotta be working okay . . . Will the near by B&N store put them back in good working order for you ?
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
With a bootable SD card are you able to.use ADB? If you are you might be able to push a normal build.prop to /system and be able to boot back into your rom. If not then like old fart said you may have messed up your partitions.
Sent from my Nook Tablet CM7 BETA using xda premium app
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Clksk8 said:
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Click to expand...
Click to collapse
assuming you have adb setup correctly the commands aren't too difficult. i believe the following should suffice. i only know windows commands so yeah..
open your start menu, type in cmd and then enter.
navigate to directory where you have adb installed. in my case it was -> cd C:/ntroot
then connect your NT to your computer, make sure usb debugging is enabled which it most likely is if you can get into cwm.
use adb devices, and there should a string of numbers which is your serial number. if you see it then that is a good sign.
then adb remount, which makes the file system writable.
next make sure you have the normal build.prop in that directory that you have adb installed in.
then do adb push build.prop /system
should be very quick, if all goes well you should be able to boot back into your rom. otherwise, your partitions are likely screwed up...
if your partitions are screwed up, there should be a couple of links in the android development section that tell you how to repartition so you can start anew.
good luck.
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
that serial number is normal, you should really learn to use the search function provided by this forum but here are two that i found...
http://forum.xda-developers.com/showthread.php?t=1562130
http://forum.xda-developers.com/showthread.php?t=1605664
those two are assuming you screwed up your partitions.
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
adb is hooked up correctly but when i put adb devices i get
0000000000 recovery instead of a serial number?
So I have bricked my Nook dozens of time but when I do I just download the acclaim_update.zip from one of these threads and go to a file in it.
Go to /META-INF/com/google/android/updater-script and then I just edit the first two lines. Edit both parts where it says "blaze" and change it to "acclaim". If you're on ubuntu then all you have to do is press saveand it will ask if you want to update the file (or something like that) and click yes. Then just make a CWM bootable sd card and flash that file Hope it helps!
Alright, so you have "lost" your files when flashing ANY of the 4.2 AOSP based rom's
(CM/PA/AOKP/AOSP/SLIM and so on)?
Don’t panic!
The pictures of your baby and nudes of your girlfriend are still there! here's what you need to do:
*Easy method* (SHOULD be done pre-installing any AOSP based rom)
Reinstall ANY stock rom and boot into it. Once you have booted into it, connect the phone to the pc,
and open the phones internal drive on the pc. You should now see all your pictures and music files
and likes again!
See, I told you not to worry.
Now, I suggest you backup all the files that you see to your PC incase you actually do lose them
sometime in the future.
What we are going to do now is prepare your phone for the android 4.2 ROMs out here, in order to
do this you create a folder on the sdcard called 0 (yes, the number 0).
Now copy everything you got on your sdcard into that folder! Once that is done you are ready to flash
any of the 4.2 ROMs!
Tadaaa! You’re done! Welcome to the world of android 4.2!
That wasn’t that hard right? Coolcakes.
Now there are other methods you can use:
If you are familiar with ADB then you do not have to move away from the 4.2 AOSP based ROM while
not being able to access your files (see Alternative method).
*Alternative method*
Code:
adb shell
cd data/media/
mv * /0
However, for the people unfamiliar with ADB. Stick to the Easy method.
Hope this helps! Goodluck folks
rewritten by @aardappel12 because he couldn't read it
Lloir said:
rewritten by @aardappel12 because he couldn't read it
Click to expand...
Click to collapse
Ouchh:silly:
Lloir said:
Alright, so you have "lost" your files when...
rewritten by @aardappel12 because he couldn't read it
Click to expand...
Click to collapse
I think this post should popup when any one opens to Original Dev forum :silly:
What I do after flashing Any Rom like AOSP+ or CarbonRom is I use solid explorer and look for the files and move them manually and that's it I merge all this folders and tada easy as pie
Enviado desde mi HTC One X+ usando Tapatalk 2
Im gona see if i can get a build and rry it thanks for the tip stay tuned for the edit for my conclusion
Sent from my HTC One X+ using xda premium
gothicasshole said:
Im gona see if i can get a build and rry it thanks for the tip stay tuned for the edit for my conclusion
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Edit the rom is no longer availibke until further development is made please dont scrap this rom i really want to try it
Sent from my HTC One X+ using xda premium
Lloir said:
Alright, so you have "lost" your files when flashing ANY of the 4.2 AOSP based rom's
(CM/PA/AOKP/AOSP/SLIM and so on)?
Don’t panic!
The pictures of your baby and nudes of your girlfriend are still there! here's what you need to do:
*Easy method* (SHOULD be done pre-installing any AOSP based rom)
Reinstall ANY stock rom and boot into it. Once you have booted into it, connect the phone to the pc,
and open the phones internal drive on the pc. You should now see all your pictures and music files
and likes again!
See, I told you not to worry.
Now, I suggest you backup all the files that you see to your PC incase you actually do lose them
sometime in the future.
What we are going to do now is prepare your phone for the android 4.2 ROMs out here, in order to
do this you create a folder on the sdcard called 0 (yes, the number 0).
Now copy everything you got on your sdcard into that folder! Once that is done you are ready to flash
any of the 4.2 ROMs!
Tadaaa! You’re done! Welcome to the world of android 4.2!
That wasn’t that hard right? Coolcakes.
Now there are other methods you can use:
If you are familiar with ADB then you do not have to move away from the 4.2 AOSP based ROM while
not being able to access your files (see Alternative method).
*Alternative method*
Code:
adb shell
cd data/media/
mv * /0
However, for the people unfamiliar with ADB. Stick to the Easy method.
Hope this helps! Goodluck folks
Click to expand...
Click to collapse
hm, thanks for the tip - sounded proof but unfortunatelly I had this /0 folder already with all conetnt from outside /data/media/ in it.
But still, all apps kept closing immedaitly stating that there is no memory or sdcard inserted.
I used the TWRP function for formatting everything.
Used advanced Wipe to clear every partition.
Phone was so wiped it said "no OS installed" when i hit the reboot recovery button.
Used ADB sideload to push CM10.1.zip to the phone and flashed the sideload.
boot.
AGAIN no apps working, file manager keeps saying there is no memory.
WTF. sorry for the language, but I'm out of options right now. and do not know what to do next with my Hox+
Setup:
TWRP 2.6.0.0
boot.img (from CM.zip)
Hox+ ADB AIO tool 3.0
cm10.1-20130714
gapps 20130301
Please help, thanks
You have to reformat it most likely if yoi deleted all partitions and basically nuked the entire internal sd even thoe you side loaded cm10 mostlikely with reformated sd you currupted it thats the whole reason android is moving away from external sd so im thinking reformat it and put a clean build and if you have anything on the sd worth saving (assumings its not wiped back it up
Sent from my HTC One X+ using xda premium
gothicasshole said:
You have to reformat it most likely if yoi deleted all partitions and basically nuked the entire internal sd even thoe you side loaded cm10 mostlikely with reformated sd you currupted it thats the whole reason android is moving away from external sd so im thinking reformat it and put a clean build and if you have anything on the sd worth saving (assumings its not wiped back it up
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
thanks, I already thought i had to go in this direction (and wipeing all data is fine, as long as the device itself will come back to life).
Just wondering how to do the formatting as the HOX+ has only internal memory/sdcard (64GB).
Is there another way beside the TWRP function for formatting the sdcard?
ADB tools, e.g.
I have downloaded the ADB tools and fastboot so I do have this adb-tools folder on my desktop.
if ADB would be the solution may someone pls advise step by step how to do so..... I've spent so much time on that HOX+ that I do not want to try&error any more....
thanks.
Did you try a wipe and a reinstall of a sense ROM ?
Wait you need the updated adb files from the 4.2.2 android sdk most likely all your commands are out dated adb changed so basically for 4.2.2 you gotta re learn it
http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
Sent from my HTC One X+ using xda premium
---------- Post added at 05:45 AM ---------- Previous post was at 05:24 AM ----------
Found a nother post
What none of the articles about this 4.2.2 update tell you is that you need to be on a current version of ADB - that is currently 1.0.31 (I was previously on 1.0.29) in order for the RSA key exchange to work. Otherwise you may connect with ADB but cannot interact with the device running Android 4.2.2 - "show devices" comes up with "offline".
Basically, you need to update your SDK to the latest version to gain access to the ADB and Fastboot apps. XDA have a simple set of instructions here -->
http://forum.xda-developers.com/showthread.php?t=1917237
Sent from my HTC One X+ using xda premium
I know this may not be the correct thread, but I've only come here after extensive searching and came up with nothing to help me.
I performed a NANDroid Backup using TWRP Recovery.
After the backup completed, when I rebooted all my sdcard data is gone. Using a file manager I can see nothing, however Clockwork Mod ROM manager can see the backup name... I used a custom name containing the name of the ROM I am currently running.
'Internal Storage' when connected to the PC shows empty folders.
Is there anything else possible I can do to try recovering my 'sdcard' files?
Thanks
gothicasshole said:
Wait you need the updated adb files from the 4.2.2 android sdk most likely all your commands are out dated adb changed so basically for 4.2.2 you gotta re learn it
http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
Sent from my HTC One X+ using xda premium
---------- Post added at 05:45 AM ---------- Previous post was at 05:24 AM ----------
Found a nother post
What none of the articles about this 4.2.2 update tell you is that you need to be on a current version of ADB - that is currently 1.0.31 (I was previously on 1.0.29) in order for the RSA key exchange to work. Otherwise you may connect with ADB but cannot interact with the device running Android 4.2.2 - "show devices" comes up with "offline".
Basically, you need to update your SDK to the latest version to gain access to the ADB and Fastboot apps. XDA have a simple set of instructions here -->
http://forum.xda-developers.com/showthread.php?t=1917237
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
---------- Post added at 12:39 PM ---------- Previous post was at 12:14 PM ----------
Edit: Found a path '/mnt/shell/emulated/" which contains my previous directory structure (names etc.) but all the folders are empty. Except for the Titanium Backup I did just prior to the NANDroid backup. As well as the NANDroid backup.
I don't know what happened.
Someone please assist.
Thanks.
Edit: Found a path '/mnt/shell/emulated/" which contains my previous directory structure (names etc.) but all the folders are empty. Except for the Titanium Backup I did just prior to the NANDroid backup. As well as the NANDroid backup.
I don't know what happened.
Someone please assist.
Thanks.
Click to expand...
Click to collapse
Every so often I plug in the HOX+ to the PC and it does an automatic sync.
I thought it was just setup to do contacts. Turns out all my data from on the sd card is all there. Pictures, Video, Documents, etc.
I had no idea.
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Android Cowboy said:
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
johnnydowngrief said:
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
Click to expand...
Click to collapse
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Android Cowboy said:
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Click to expand...
Click to collapse
Then maybe this. http://forum.xda-developers.com/showthread.php?t=1379875 But I'm just guessing here. I dont want to spam this thread. Maybe someone more experienced can help you.
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I will try that. If I could just push a new build.prop to overwrite the old one I put probably be okay. How did restore system files using ADB.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That didn't work for me, I've also trying factory resetting again multiple times through recovery, but no dice.
I got my fastboot cable working, and was able to get the device recognized as "Qualcomm USB modem converter"
I opened a thread about it, any help is appreciated!
Android Cowboy said:
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
Click to expand...
Click to collapse
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
GSLEON3 said:
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
Click to expand...
Click to collapse
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Android Cowboy said:
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Click to expand...
Click to collapse
Did you try either of these drivers:
http://www.4shared.com/rar/kRIFBtGe/qualcomm_hsusb_device_drivers.html
http://drivers.softpedia.com/progDo...dows-7-x64-Windows-8-x64-Download-179130.html
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Since you didn't factory reset, does it show up on adb devices at all while it's trying to boot ?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
So currently its not showing up on adb while its booting, but that's probably because I haven't updated adb in a while. I'm going to update when I get home from work and report back.
EDIT: So I update ADB, which isn't recognizing it, but oddly enough, my computer can see it even after the screen shuts off as an android device. My only guess then is I'm missing a driver or something. Any suggestions?
Android Cowboy said:
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
S_transform said:
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
Click to expand...
Click to collapse
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Android Cowboy said:
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Click to expand...
Click to collapse
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
S_transform said:
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
Click to expand...
Click to collapse
When you ADB shell, are you seeing a "#" which means you are rooted. I'm not the world's expert on ADB but this should help. Once you are shell and rooted you can just chmod 644 or 777 on /system and see if that works. http://gizbeat.com/2103/how-to-change-file-permissions-through-adb/