[SOLVED]
Verizon Developer Edition. I just did a complete reset to 4.4, stock recovery and all. Booted up, got the 4.4.2 update, installed that. Flashed custom boot logo, then flashed TWRP again. Went to go wipe data/cache and accidentally wiped system. Now I've got no OS.
What do I do now? I've updated to 4.4.2 from 4.4 and can't revert back.
You'll need a good friend who can make a backup in TWRP of just the System partition. This friend probably should have an identical phone, in my case, we both have Verizon Developer Editions. He also needs to be giving you a TWRP system backup that matches what you most recently had flashed. In my case, I had just taken the 4.4.2 update. Luckily he had too already. A TWRP backup of the system partition from someone on 4.4 or 4.2.2 would, I'd guess, brick you. So best to find someone with an identical phone to you and matching software, otherwise I don't know what'd happen. There should be 3 files, a recovery.log, system.ext4.win, and system.win.md5. This is about 1GB so it'll take time to transfer/download/upload around the place.
I had downloaded the adb tools a while back from step 1 here: http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
You need adb and all the drivers and crap working for this
Put the 3 files in that folder, where adb is.
Next, boot into TWRP on your phone with no OS and make a backup of everything, should go quick as there's no system and I'd guess data is probably pretty empty...
Next, go back to TWRP main page and go to mounts, then mount the /Data partition.
Shift and right click in Windows Explorer where adb is and open command prompt, type in adb shell and you should get a prompt. Type ls and hit enter, should see contents of the /Data partition
Type cd sdcard/TWRP/BACKUPS and hit enter, then type ls and hit enter, you should see another folder named T something, this is the phone's serial number. Type "cd serial" where serial is the name of that T folder and hit enter again.
Type ls again and you should see a folder starting with 2014- or whatever year you may be reading this in... that's the folder that has the backup files you just made.
Type mkdir A and hit enter followed by typing ls again, now you should see that 2014- folder and another folder named A
Type exit to get out of shell. Now type adb push recovery.log /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like .005s or something.
You can type adb shell again, enter, and navigate to the directory to make sure there's a recovery.log file in the A folder. If there is, good. If not, no good, you did something wrong. Don't forget to type exit to get out of shell and back into Windows command.
Now do the same for the next small file, so type adb push system.ext4.win.md5 /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like .007s or something.
Finally, the big file. Don't panic like I did, it'll take some time, like 4 minutes maybe. Type adb push system.ext4.win /sdcard/TWRP/BACKUPS/XXXXXXXX/A where XXXXXXX is that T serial number, then hit enter. Should say it pushed a file in like 380s or something.
So, now you should have your TWRP system partition backup files in the A folder in the proper folder hierarchy. Now on the phone, just back out of mounts (hit middle button) and shut phone down and it'll warn you about there not being an OS.
Reboot recovery, Restore, you should now see the folder named A as an option. Hit that, and it should auto select System and nothing else. I did md5 check option. Slide to restore. Wait. Wait. Wait. Reboot.
If you're lucky, you'll see the boot animation and hopefully boot back into Android. It'll take a while the first go too so be patient.
Or, I have a buddy with a Verizon Dev Edition in close proximity... can he just make a backup in TWRP and then I could restore it?
Or is there a way to pull the System.img from his device and flash to mine?
Or how about the system.img from T-mobile? Could I flash that? Or... that wouldn't help would it...
CartlandSmith said:
according to this thread, you can:
[Q] Can you restore a nandroid backup on a different device?
But he needs to be on 4.4.2.
Click to expand...
Click to collapse
Yeah, he's on 4.4.2 already as well. He's making a TWRP backup of just System. So I guess I need to figure out how to get the folder hierarchy and the TWRP backup files onto my device. I assume through ADB somehow?
Also, I did grab the 4.4.2 OTA zip file before doing all this, so I have the update zip, but I don't think that helps me either does it?
Am I missing something, can't you just flash back system images from moto?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Just realized only 4.4 images are posted.
fml
yeah, I realized I could just make a TWRP backup of my empty partitions to get the folder hierarchy made. So now all I should need to do is figure out how to either:
A. Push a folder and sub-folders/files via ADB or
B. Create folders in ADB then push the files to the folders
Sounding good?
GloryUprising said:
Am I missing something, can't you just flash back system images from moto?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
From all I've read and understand, once you upgrade to 4.4.2, the bootloader also gets updated, and the new bootloader isn't backwards compatible, so you can't flash any images older than 4.4.2 else you'll brick somehow.
Just out of curiosity, anyone know how long it takes for factory images to be posted? I assume a metric &#@$ tonne of crap has to be done to get the files and poo from Verizon to Motorola to host.
Yeah. I'm pretty sure TWRP has already made the folder hierarchy for me. I think I just need to get my buddy's TWRP files and then push that folder to the device via ADB with "adb push /TWRP/BACKUPS /mnt/sdcard/TWRP/BACKUPS"
Yeah, I think maybe it's a folder with the device's serial number? T-something?
Okay so can you post the hierarchy I need to make? TWRP>BACKUPS>SERIAL#>BACKUPNAME>Backup Files?
Okay, I've got his TWRP backup of just system downloaded, 3 files. I booted into TWRP recovery and in the mounts sections, I mounted data. Now I can navigate the data folders via ADB shell. I've created a new backup folder "B". Now I think I just need to push the 3 backup files into that folder. Backup folder "A" was the one I made to get TWRP to auto-make the folder hierarchy.
How do I unmount now that I've pushed files?
Not that I can find.
I've got all the files/folders pushed and made. My phone is connected via USB and is in TWRP recovery. If I hit a volume button I get a gray screen with just "Updating partition details... Full SELinux support is present." I don't know what to do from here. I can still do "adb shell" and see my data partition in my command window...
Haven't tried, afraid to lose what I've done so far. If I back out to Restore in TWRP, the directories/backups don't show. I think it's cause my /data is mounted and being used by my PC so TWRP can't see the partition?
Believe it or not, I did this exact something, not paying attention and boom system wiped. I have been a lurker on XDA for years and years and never needed an account because I have never made a stupid mistake like this in the past.
I contacted Moto to see if they would bail me out, but if not I will just wait out the factory image its a tough lesson.
I have reverted back to my my old AOKPs3 until i can get this all figured out.
*I will be watching this to see if you figure it out, and if so maybe you can help me.
GL.
Fingers crossed. Backed out to main TWRP home screen, powered off. Booted back into recovery, Restore tab, my folder showed up with the System backup in there, restoring now...
Success!!!
CartlandSmith said:
there should be a popup warning saying when you wipe your system you run the risk of losing your OS or whatever something shorter, but enough of a warning that it would cause people to stop and think if this was what they intended to do.
Click to expand...
Click to collapse
There wasn't one for me. That or I just completely missed it flying through like I thought I owned those menus...
Mike7143 said:
There wasn't one for me. That or I just completely missed it flying through like I thought I owned those menus...
Click to expand...
Click to collapse
Me either.
Mike, Could you send me the file? Im in the same boat as you "were"
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
Mi3 Stuck on MIUI logo - can't backup data with adb pull
Hi
I've tryed to install Lollipop trough TWRP on my Mi3 without erasing the usera data (I know... it's not something that I usually do)
because I wanted to keep the data inside the internal sdcard
After that, the phone got stuck in the "MIUI bubble" screen, without wanting to boot the launcher etc
so I got back to mi recovery
I installed a custom mi3 Rom, but same problem
stuck at MIUI logo just before where the OS usually start working
now I'm on CWM recovery 6.0.5.0(R8) by furniel & donbot
trying to backup the internal sdcard trough adb
but something is not going right
adb pull /sdcard/0/ c:
start copying the files and the folders
but after a while, something with :nopm: shows, and "no such file or directory" text appear on the prompt window, and ADB stops copying the files
what can I do?
I just want to copy what's inside my phone, and the use the xiaomi pc tool (with phone in fast boot) to hopefully return to a working phone
why ADB stop copying files after a while?
any solution?
Hello,
I am hoping someone can assist with interpreting my log file or provide suggestions on how to convert my backups into a usable format that can be flashed back to the phone thus recovering it to a usable state. I have a logcat and dmesg in a text log file. I have put the file up on Google drive, the link is here-
https://drive.google.com/file/d/0B9e...ew?usp=sharing
I also spent time reading and studying the post about using logcat and dmesg posted here-
http://forum.xda-developers.com/showthread.php?t=2274119
I believe the last operation I tried before softbricking was installing the Xposed framework module for my device (running Lollipop 5.1.1).
I have tried one solution so far, go into recovery, clear cache and reboot.
To recover from this issue I think I have two basic options-
#1 restore from backup
#2 locate the problem that is causing the system to hang at startup in the first place
At the end of the day I am trying to find the simplest, quickest method to get back up and running. Both methods are acceptable to me. I am not worried about losing any data.
My phone is a BLU Studio C 5+5 LTE and therefore can't use TWRP or CWM (At least that is my assumption, maybe someone knows different). Before getting into the softbrick state I took 3 different types of backups in the hopes that one of them could be used in case it was needed. (like this)
Type 1 - I did an ADB shell backup from a completely stock device (unrooted). I used this command-
adb backup -apk -all -f fullbackup.adb
For this method I followed this guide here-
https://linuxiswonderful.wordpress.com/2015/04/04/full-backup-of-nonrooted-android/
Type 2 - I used Titanium backup and performed a complete system and application backup
Type 3 - I rooted the phone and backed up all partitions using dd after reviewing the partition layout of the device. For example, to backup the system partition I did the following at an ADB shell-
dd if=/dev/block/mmcblk0p21 of=/storage/sdcard1/firmware-img/system.img
I am able to still communicate to my device using ADB and I can get an ADB shell or enter fastboot mode.
My challenge/sticking point is how to turn my backups into a usable format to get me back on track or understand the boot process enough to get out of the boot loop. I am familiar with how Linux boots as I am a SysAdmin. I know Android is similar but just different enough to make me research this further.
The first thing I tried was mounting my raw image files created from the dd process. I followed this guide-
https://samindaw.wordpress.com/2012/03/21/mounting-a-file-as-a-file-system-in-linux/
I ran these commands-
#losetup /dev/loop0 /path/to/my/system.img
# mkfs -t ext3 -m 1 -v /dev/loop0
# mount -t ext3 /dev/loop0 /mnt
# cd /mnt
# ls
The various image files I created all seemed to mount "ok" OK meaning that the loopback mount process worked but it appears there is nothing but a lost+found folder in the mounted image. (I'm not sure why that is.)
I am still researching methods to turn my other backups into something usable for recovery purposes.
For using the adb backup file I created, this is what my understanding is-
Adb backup uses a type of compression (don’t remember what kind). I would need to uncompress the file first. After uncompressing and being able to view the file contents I would think I should be able to put together a flashable zip file of some sort.
I think the process for Titanium backup would generally be the same- uncompress/convert file format, create/assemble a flashable zip file
If there is any other info you need to see, please let me know. I made a lot of notes about the system architecture, partition layout, etc.
Many Thanks in Advance for your Advice!
Found my answer. Used ADB shell and mounted /system in RW mode. Changed /system/bin/dex2oat filename and the device booted normally. Issue solved!
[SOLVED] - Apparently, I lost the ability to *read* also. When I went into TWRP, I must have clicked the "keep the system read-only" button. That would prevent me from deleting files/folders. I hereby select one card from the Smacktard pile.
Evening all,
Sprint Note 5, Rooted.
Tried to manually make an application a "System App". This is what happens when you give a monkey the *tools* but not the *brains*. I'm plenty technical, but I've not done this before.
I installed an app, then went into the data\apps directory and copied the entire application's folder into \system\app.
When I rebooted, the phone gets stuck on the Sprint LTE screen.
When I boot into TWRP, and into Advanced / File Manager, then go into the offending directory, I get the following:
File Operation Complete
Failed
rm -rf "/system/app/com.incorporateapps.fakegps.fre-1" processes ended with ERROR: 1I get similar messages when I chmod, delete, move, or rename.
Any assistance you could provide would be MUCH appreciated. I'm bricked and cannot work until I get my phone back.
Thanks!
Pete
have you tried to flash stock rom or another rom ?