Database Develop

Nexus 7 2012 hspa soft brick on 4.4 ota need my files accessed

Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?

I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.

chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.

Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.

chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.

When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.

[Q]Stuck in boot after root attempt, even after factory reset. Help!

Hey guys, last night I tried to root my device (XT1058) following the guide [here](http://forum.xda-developers.com/moto-x/general/howto-root-moto-x-ver-4-4-4-xt1060-t3118342). Stupid me decided I wouldn't need to go back to stock ROM like it says in the first step. I continue with the guide, follow every step, until I reboot. After rebooting my Moto X gets stuck at the white screen with the blue circle M. I panicked, read a lot of things online, followed them, and nothing worked. I reset the cache partition in recovery mode when rebooting into fastboot, still nothing. I also noticed that my device is no longer detected in ADB at all, even in fastboot. So after just giving up, I read online in multiple places going to recovery mode, and wiping the whole phone/factory resetting would fix it. It still is not recognized by ADB or finishing booting. I realize I should've been more careful. Please help!

First thing... when the phone is in Fastboot AP menu, you can't use ADB. ADB wont work and wont see your phone unless the phone is fully booted. (i.e. adb.exe and fastboot.exe use two different modes on the phone).
Next, I've seen that symptom before, but I don't recall how to fix.
I would really consider asking in the thread for the process you were following.
If no one gives you any suggestion, you could always try re-flashing the stock image for your phone that matches the highest version you've had installed on your phone. (On fastboot screen you can see bootloader version, so match you stock version to that. see the list of known bootloader versions at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 ) And use mfastboot to flash it (follow option 5 in the 2nd post at -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )

I'm pretty sure I saw this on reddit. You had a mac right?
You need fastboot installed on your mac:
http://forum.xda-developers.com/showthread.php?t=1917237
Assuming you have fastboot working on your mac and your phone this thread method two:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Use fastboot instead of mfastboot for the sytem.img file.
If you receive an error with flashing system you could try:
Code:
fastboot -S 0 flash system system.img

If u can still enter recovery mode, factory data reset from it , if u can't boot still after resetting , u have to flash the full stock ROM.....
Sent from my HM NOTE 1LTE using XDA Free mobile app

Moto G 4G (uk model) Stuck on wallpaper

Hey Guys, i'm really struggling to find a solution to this as every time i try to google a solution it just comes up with a load of results trying to tell me how to change my wallpaper :/
So basically, overnight, my dad's Moto G 4G started to act strangly. It can still:
Boot up normally
Power Off normally
Vibrates when notifications come through
Rings, all be it temporarily when called and can be answered if connected to the car's bluetooth.
However, it will no longer display any of the UI (other than the Power Off dialogue) and the wallpaper. I can see that the phone isn't completely frozen as the wallpaper in use is a live wallpaper which you can interact with via touch.
When the phone is plugged into my laptop the phone is showing in 'my computer' but it shows no files, same situation in recovery and fastboot too.
I've tried wiping the cache from recovery but it's still the same.
There was one instance where the first time i plugged the phone into the laptop via usb it brought up the whole ui, icons, status bar and all, for like 2 seconds.
Now, back to nothing. Not sure what to do from here. I'm desperately trying not to factory reset it as my grandfather (my dad's dad) passed away recently and i'm pretty sure there are files on here which are now irreplaceable

jhaedee said:
Hey Guys, i'm really struggling to find a solution to this as every time i try to google a solution it just comes up with a load of results trying to tell me how to change my wallpaper :/
So basically, overnight, my dad's Moto G 4G started to act strangly. It can still:
Boot up normally
Power Off normally
Vibrates when notifications come through
Rings, all be it temporarily when called and can be answered if connected to the car's bluetooth.
However, it will no longer display any of the UI (other than the Power Off dialogue) and the wallpaper. I can see that the phone isn't completely frozen as the wallpaper in use is a live wallpaper which you can interact with via touch.
When the phone is plugged into my laptop the phone is showing in 'my computer' but it shows no files, same situation in recovery and fastboot too.
I've tried wiping the cache from recovery but it's still the same.
There was one instance where the first time i plugged the phone into the laptop via usb it brought up the whole ui, icons, status bar and all, for like 2 seconds.
Now, back to nothing. Not sure what to do from here. I'm desperately trying not to factory reset it as my grandfather (my dad's dad) passed away recently and i'm pretty sure there are files on here which are now irreplaceable
Click to expand...
Click to collapse
Ouch, looks like an emmc problem, some partitions may be corrupted.
1st be sure if the usb cable is ok, i have seen many cable going nuts and loosing data but still charging.
If the usb cable is dead you will need a working one anyway to try to recover the phone after you got your data.
Also try apps like airdroid works, you can save everything wirelessy from your pc.
When you have a working cable and still failed to save data you can try to flash a recovery that allow mounting partitions to your pc ( twrp ) whitout booting the os, since for what i understood your android installation got corrupted somewhere and is borked.
Wich model is that one ? should be an XT1072 right ? YOU MUST BE SURE or flashing the wrong stuffs can totaly BRICK your phone.
If it's an XT1072 i have uploaded for you the latest UK stock image to mega.nz so you can dl it quickly
https://mega.nz/#!fId0yD4a!LjyEIjRXse092l7j_JL0Ky324EK6SS4vK4kdqGcS9XY
You will need fastboot + mfastbbotv2 and here they are
https://mega.nz/#!bdEDBDiQ!3KlB6WfUxUep1QR7XSvwpuCuxWnktfCh7YBX020HqmY
Put everything in the same folder ( ex c:\phoner )
open a dos shell whit admin privileges and navigate to that folder, then use this commands and check after every commands if you get back the OK on flashing (you can copy-paste them into the shell)
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata <--- DON'T use this only if you wasn't able to recover your data whit the others methods
mfastboot.exe reboot
The phone should have rebooted, may take longer to boot don't panic, now the phone should be ok and if you didn't wiped the userdata it should be 100% the same as before whit the latest stock fw, my advice is to do a full factory restore to use it, so once you recovered your data do a factory reset from the android menu.
If the phone isn't a 1072 as supposed dl here the correct zip http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC
If you have more questions, especially on flashing twrp/stock just ask before doing anything that could turn the phone into a stone.

Thank you Dr. Nic for your incredibly informative response
Firstly, I was wrong initially, it is actually a XT1039 (first gen 4g) but this does appear to be listed on the file factory page you linked so I should be fine with the instructions.
What I do want to ask though is:
Is there anyway for me to boot twrp without installing it as a temporary basis? I'm sure I've done this before previously on my old moto x but it has been a while. I seem to recall you can type in a fast boot command and get it to boot to twrp. The phone is not rooted or bootloader unlocked (which i know will wipe the phone if I do it so that isn't really a permanent option yet)
Secondly, is there any way for me to find out which stock rom files I need without being able to access the os and looking in settings? I know it is a xt1039 but there are about 5 different, carrier based versions available and I don't want to flash the wrong one.
Thanks again for all your help
If this goes to plan you will have made my father's Christmas special

jhaedee said:
Thank you Dr. Nic for your incredibly informative response
Firstly, I was wrong initially, it is actually a XT1039 (first gen 4g) but this does appear to be listed on the file factory page you linked so I should be fine with the instructions.
What I do want to ask though is:
Is there anyway for me to boot twrp without installing it as a temporary basis? I'm sure I've done this before previously on my old moto x but it has been a while. I seem to recall you can type in a fast boot command and get it to boot to twrp. The phone is not rooted or bootloader unlocked (which i know will wipe the phone if I do it so that isn't really a permanent option yet)
Secondly, is there any way for me to find out which stock rom files I need without being able to access the os and looking in settings? I know it is a xt1039 but there are about 5 different, carrier based versions available and I don't want to flash the wrong one.
Thanks again for all your help
If this goes to plan you will have made my father's Christmas special
Click to expand...
Click to collapse
So 1 thing at time
Probably the others fw you saw was olders versions too or for others regions, i suggest to use the same as you have or the latest
You are completly unable to check your current os installed from phone infos ? have you checked everything on the box ? somewhere there must be some infos, maybe under a barcode sticker.
This should be your latest UK stock, XT1039 aka "peregrine", do you rember if you was on 4.4.4 or 5.1 ? you should flash the same version to improve the % of not loosing something.
Clean Stock 5.1 http://www.filefactory.com/file/dpx...RINE_RETGB_5.1_LPB23.13-17.3_cid7_CFC.xml.zip
So, the cable is ok ? are you able to issue commands whit fastboot ?
If yes unlock the bootloader to install a modded recovery, you will need that to copy your files, and if that fails last try is flashing stock whitout deleteing userdata, but the corruption could be both in /data and /system so after the recovery you will have to do a factory reset anyway.
To boot twrp you have to flash it, don't worry if you want the phone full stock again is the last step you have to do that to fix the corruptions happened, and it's no 100% success rate too since that could happened becouse the emmc is failing

I can no longer reach the boot animation?

Hello, XDA forums. I was trying to get Miracast to work on my cousin's Nexus 6 device; doing sone research I found that it was as modifying a value in the build.prop file. Naturally, I was like "Pshh, easy!" (Note that the device was already rooted.)
So I download a build.prop editor and apply the edit, save the file. Superuser request, granted, saved. I noticed that the editor now displayed build.prop as an empty file, but still had the values loaded; okay, whatever.
I rebooted the device to apply the changes. It was stuck at the Google post screen and had not continued to the boot animation.
After waiting a couple minutes I realized there was an issue. Okay, so I would just use the adb interface to replace the build.prop file with the stock file, easy, no issue. Turns out when I rooted the device a while back I never flashed CWM or TWRP, so I had to get into the backup recovery, since attempting to factory reset from the bootloader resulted in the same as a normal boot.
Once I had gotten into the backup recovery I plugged the device in and attempted to update the build.prop file. I couldn't get further than 'adb root', it would result in an error for every command except sideload and USB. I tried for quite a while to resolve that issue.
That wasn't working so I was like "I'll just flash the OS since I have the ability to sideload", so I flashed the stock Nexus 6 ROM and still had the same issue.
Does anybody know of a solution?

@Drasid,
Download the factory image from Google developer site. Extract all the files. Fastboot flash the system, and boot image files from bootloader.

@cam30era,
I can do this with the stock recovery?
I can only secure an adb connection through that; fastboot commands do not work in it.

Drasid said:
@cam30era,
I can do this with the stock recovery?
I can only secure an adb connection through that; fastboot commands do not work in it.
Click to expand...
Click to collapse
No you use fast boot to flash factory images, adb to push a factory ota file

@Holeibdalip, Oh yeah, I was explaining the issue then my friend then realized "Wait, you can't fastboot like that, you fastboot in the bootloader."
It was one of those "Duh" moments.

Drasid said:
@Holeibdalip, Oh yeah, I was explaining the issue then my friend then realized "Wait, you can't fastboot like that, you fastboot in the bootloader."
It was one of those "Duh" moments.
Click to expand...
Click to collapse
And if you reread carefully what I wrote, I said "fastboot flash"....

Drasid said:
@Holeibdalip, Oh yeah, I was explaining the issue then my friend then realized "Wait, you can't fastboot like that, you fastboot in the bootloader."
It was one of those "Duh" moments.
Click to expand...
Click to collapse
Happens to the best of us lol

Alright so I reinstalled Android and it worked. Though on the setup page it said that my cousin couldn't log in and had to wait 24 hours (FRP). So, we waited a day and it persisted. I did some research and found a couple ways to fix it. Using adb I launched the settings app and performed a factory reset in the os. I still got the error afterwards, though I read that would fix it. Then I wiped the partition which is supposed to contain the frp information, that didn't work. I also tried to enable OEM unlocking in the os so I could fastboot OEM unlock and fix it, though the developer options appeared empty. I am unsure what to do next.
Edit: I flashed the system with the google developer image and reinstalled it, I got it to work, thanks for your guys's help.

Oddest Brick Ever - Kindle Fire (Tate)

History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.

Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!