Database Develop

[Q] Tough time going back to stock

I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.

I am not sure if it would make a difference in your situation but I do everything for my phone on an x86 system. I have had issues with LG and Samsung phones in the past when trying things on an x64 computer.

ifixgse said:
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
Click to expand...
Click to collapse
you said you are stuck on startup splash meaning bootloop? if it is you should try again with rsd lite.
else you may lose all your data in the memory but do a format media/data and sdcard, so that it can mount /data, it worked for me. then format system mount everyting and do a fresh install of any rom you can sideload or just have it in the sdcard.

I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.

ifixgse said:
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Any questions don't hesitate to ask.
If this helps you hit that thanks button!

[Q] Brick Help vs980 LG G2

Currently irate because I already typed all this then hit enter to be told I can only register once from this ip.
Any way...
Rooted vs98027a Android 4.4.2 via Stump Root
Used AutoRec which installed TWRP 2.7.00
Backed up Stock Rom
Mount button is missing
Rebooted into Stock to transfer backup to PC and place "cm-12-20150603-NIGHTLY-vs980.zip" as well as Lp gapps.
Rebooted back into TWRP
Wiped, then Installed the CM Nightly, wiped cache and rebooted.
Stuck in LG Boot loop.
Use buttons to boot back into TWRP, open Restore and It's just a blank navigation window.
TWRP just became ****ing worthless
Tried to wipe and possibly install same CM again. Still boot looping.
Tried getting to download mode, but it reboots before installing driver.
I have not a clue as to what to do next.
I can't get it to mount.
ADB Sideload Fails.
Terminal Command lets me select a blank navigation window.
And my original file structure is in like sdcard/0/0/0/0/0/0/0/0/ etc.
Please help, or at least redeem CM and TWRP's value somehow, because this is bs.

I sort of fixed it.
Restore showed up blank, because within the many /0/0/0/0/0/0/0/0 a new TWRP folder would be made or course containing nothing.
I also learned the adb is this magnificent goddess that can do things even when your phone can't.
Throughout further reading I glimpsed upon something about "loki" files that aren't compatible with specific versions of twrp or something. So If you've also been through this and still feel brave enough to flash a custom, then make sure you get the newest version of twrp...
As for the Restore issue, assuming you have a backup saved on pc, wipe everything then adb push the whole file (TWRP/BACKUPS/BLAHBLAH/BLAUGHESDIHF) to /sdcard/.... then it should show up in restore, if it doesn't then use file manager to place it in the right TWRP directory... You can also use the file manager to move the restore folder to the "correct" twrp folder if you don't have it backed up.

Asus MeMO Pad 7 unusable please help!

Hi,
I am really desperate! I turned on my rooted Asus MeMO Pad 7 ME176CX after several months of no use, but apps/services won't load (loads of error messages, all apps/services stopped etc.) like it was obsolete or screwed up. So I unrooted it and the issue got worse!
There is a Asus demo app in the notification bar that disables WIFI and software reset and says to plug in the power adapter (no difference, it won't go away).
1) I copied the necessary files to my memory card (to get rid of the Asus demo app as per other threads) but once I insert the memory card, even though it is recognized, it says no files present.
2) I did a hard reset with Vol - (or +, tried both) and Power but nothing happens (no recovery screen, it just stays black).
3) I removed the battery & waited 10 mins, no difference.
4) I formatted a card to FAT32 and copied the cleardata.zip unzipped files from Asus then rebooted pressing just Power but it just reboots normally like the card is not inserted.
Now basically the tablet shows a few apps (Calendar, Gallery etc.) and nothing else.
I cannot connect to wifi, bluetooth does not work, the memory card says no files present, vol + power does not work, cleardata trick did not work, I cannot send it back under warranty (ex-rooted) ... what else can I do??????
Many thanks!

Reboot into Droidboot (Volume Down + Power IIRC, could be up), boot the Temporary TWRP (http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096), flash ROM

After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????

boredfish said:
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
Click to expand...
Click to collapse
Well, theres quite a lot of options do recover your tablet, before doing anyhing, if you have access to adb, then you should do: download .17 rom and extract it, after extracting go to META-INF\com\google\android\updater-script and open it with notepad, and remove the first 2 lines, then save, and make the zip file (rename it to update.zip {careful not to make the file "update.zip.zip"}), then put the zip file in adb folder (for me its C:\\adb) and do adb push update.zip /sdcard/ (make sure adb is working) after it finishes pushing, go to bootloader (if not there already) and run temp recovery (twrp or cwm), and then install the zip, then clear dalvik and cache, and reboot, if first reboot doesnt work, reboot again, if it still doesnt work, install update.zip again. Hope i helped, if u have any questions tell me :3
=====
edit
=====
if you really cant get out of recovery theres still a way of fixing your tablet (same problem happend to me today and its fixed), if you already did all the steps above on the download .17 and extracting and changing the file of updater script then its already almost done, to access the bootloader you need to shutdown your tablet, press Power, Vol+ and Vol- at same time, it will go to fastboot, copy the file "droidboot.img" from the update.zip and place it in the adb folder (for me its c:\\adb), then do "fastboot boot droidboot.img" and it should download the img to the tab and boot to droidboot (you need to do this a few times, because 5/1 only 1 goes to bootloader), after booting to droidboot you can easily recover from there, on bootloader you have adb access, which means you can push the update.zip to the tablet (with update.zip in adb folder already, do on cmd, "adb push update.zip /sdcard/") after pushing go to temp recovery and install the update.zip normally after installing. format cache and dalvik, and reboot, if its stuck on logo, shutdown and reboot, if still doesnt work install the update once more by turning your device off and go to bootloader normally, (it works now, because it has the software now, (to enter bootloader press press power + vol-), and load temp recovery and reinstall). i hope i helped

Xiaomi Mi3 Locked

I have a Mi3 wearing normally until this morning I found him to touch off. On power it is left in the IM logo with nothing. I tried to change the system 1 to system 2 and again it stays in my logo. Then I tried to do a complete wipe and still not working. At least you can seamlessly access to recovery and fastboot. I have again changed to System 1.
Finally, and I had left was to use the application MiFlash Xiaomi, so trying to solve with the latest build of Global MIUI gives me errors.
IMG: h**p://i.imgur.com/V5A8cmT.png
Grated and lost, it struck me as TWRP install a recovery by ADB. In doing so I was having problems with the partitions as they could not mount volumes.
IMG: h**p://i.imgur.com/UisZrXz.jpg
I would also like to mention that when I present the TWRP recovery and also try to mount the systema in Windows Explorer I get the MTP "MI 3W" icon, let me get inside but I have "permission" to create nothing inside the folder contains nothing (I guess when to make the flash was not due to complete by bugs and does not have any system).
To all this, I think it can be solved because you can seamlessly access and fastboot recovery. I hope someone can help me really...
Sorry for my bad English, I used Google.

[Q] bootloop after insufficient space rooted

I have rooted my m10g using magics via twrp and also applied the "no-dm-verify" patch but I didn't notice about the "forced data encryption" patcher here so that's reason why I didn't patch it at this point! anyway the data section was mounting without any problems but after I reboot recovery I was getting error In mounting the data section I just ignore it and I was able to boot into system normally but after some days exactly after "insufficient space" I just rebooted for some reasons and after that the device won't boot anymore / stucked at bootloop...!
I was able to see the home screen/touch wiz about 4 seconds and after that it's reboots again and again (In this point I tried to delete unwanted files quickly but there's no luck).
Things I have tried:
- flashed an recovery.img extracted from combination firmware and tried the "lacking storage booting" an option from stock recovery menu the device started in safe mode (It's says something like this: please bacup your stuff and then perform factory reset) but it's still won't boot (bootloop).
- twrp decrypt (I set no password there but I just tried In hope of chance) btw twrp never asked before to decrypt my data or to enter any password.
- I did twrp backup to my ext-sd and decompiled the boot.img to see what can I do (but after magics's patch I can do nothing).
- Pulled full userdata (mmcblk0p26) section also the emmc (mmcblk0) and tried to mount via linux reader windows tool / opening via 7zip but still can't access the userdata section. also tried to open the dumped userdata via hex editor but still can't see anything(looks like encrypted).
Things I want to try next:
- Format the data section after that try to restore the dumped userdata section via dd command.
- Enable usb debug at boot time and try to adb shell stop then pull all important data from the device.
- Inject custom script in stock_recovery.img to copy all internal files to the externel-sdcard (or even delete some huge files that I'm pretty sure of their path).
Notes / just to be clear:
* Flashing the stock kernel will encrypt the userdata section and the bootloop will stop but I'll lose all my data (I know that so I was just switching from the stock recovery to twrp).
* I could just perform a format data from the recovery menu / twrp or just flash the stock firmware to fix the booting problem but first I need to all my files get back.
Looking for any help in things that I want to try next.

Finally after a lot of tries I have solved my problem...!
How?
Short answer: ClassyKitchen
Long answer:
I just started creating my first rom In ClassyKitchen and I just enabled adb and removed dm-vertify via the kitchen and after the rom has prepared I just flashed through TWRP after I reboot the phone wasn't able to boot (stucked at first samsung logo) switched the device to download mode and I flashed system only using odin... after that phone started with setup wizard! and it's was still in safe mode (the backup message was still showing also) anyway I completed the setup wizard then check the home screen and apks I have installed wasn't there...!!! I opened "My Files" and finally I was able to see my files again!
I just copied all my internal sdcard to my external sdcard...!
After the copy ends I tried to exit safe mode to get my installed apks/contacts again so I just rebooted the phone to exit from the safe mode! But after the reboot "custom binary flashed bla bla".
I flashed stock "boot.img" and "recovery.img" using odin But as I said in the first post data encryption was there...!!!
Anyway I flashed full stock firmware after that I unlocked my OEM and flashed TWRP again and I restored the emmc dump using dd after restore completed rebooted the phone and it's back to it's state...!
this time I just flashed the patched boot.img (ClassyKitchen) and after the reboot phone started normally with setup wizard as said above! Connected to wifi unlocked my OEM and I was trying to get out of safe mode I rebooted and rebooted and power off but I wasn't able to disable the safe mode...!!!
I tried to root using magics but it's failed (the boot was patched by bla unsupported something like that) also the data section was still unmount able! In the TWRP
Anyway I just stopped at this point! Because I have reach my point (Getting back my sdcard data).
Notes!:
* All thanks goes to the author of ClassyKitchen.
* TWRP I was using found here.
* Odin I have used found here.
* I was using the same firmware version (PDA) installed in my phone.
* I have unlocked my OEM using this method the first time I have used it's taked from me only 3 days!.
* The idea of taking full encrypted emmc backup was by this post (I was getting some error messages so I just used "dd if=/dev/block/mmcblk0 of=/your_external-sd/mmcblk0.img" In case of "no space left error" format your externel-sdcard to ext4 and try again).
Sorry for my bad English x).