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.
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Dees_Troy said:
[RECOVERY] TeamWin Recovery Project (twrp) 2.0.0RC0 [2011-12-17]
Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind.
Special thanks to xboarder56 for helping test the port and a couple of other testers that I forget the names of at the moment.
Click to expand...
Click to collapse
NICE, thanks to the both of you! Goin' on tonight fo sho.
Very nice job guys! I just might have to update my signature now.
Is there any future in external sdcard support?
Looks good I guess I'll have to update from the old version, thanks.
Awesome work guys.... this kicks total butt!
Nice! It's come a long way since I used it on my 3D. Alot faster compressed backup, thanks
Sent from my HTC Amaze 4G using xda premium
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
milo356 said:
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I have. I can do it in different ways. flash_image recovery recoveryname.img command from the phone itself if you have the flash_image binary installed or by fastboot flash recovery recoveryname.img with the phone in bootloader mode.
Not complicated at all.
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Sikety said:
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Click to expand...
Click to collapse
Use this one if you want to backup and restore to and from external sdcard.
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
gregma said:
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
Click to expand...
Click to collapse
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Binary100100 said:
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Click to expand...
Click to collapse
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
gregma said:
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
Click to expand...
Click to collapse
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Binary100100 said:
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Click to expand...
Click to collapse
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
---------- Post added at 01:55 PM ---------- Previous post was at 01:22 PM ----------
gregma said:
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
Click to expand...
Click to collapse
I LOVE answering my own darned post.... Didn't realize you had to battery power cycle the device to get it back into hboot. I'm good to go now!
Greg
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
2sh0rt said:
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
Click to expand...
Click to collapse
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Binary100100 said:
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Click to expand...
Click to collapse
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
2sh0rt said:
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
Click to expand...
Click to collapse
I came from the vibrant as well however I wasn't so active there.
I don't understand why you don't see any zip files then. Strange.
Me either... think i'll just try and reload it and see what happens. Thought maybe i was clicking the wrong thing or not clicking something.
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
and its not just that i dont see any zip files. i dont see ANY files at all! every directory i click is empty! even on the system partition! not a single file shows up. only directories and when i click them there is nothing except /.. and /.
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?
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of additional features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
HTC Droid Incredible 4G LTE product page on TeamW.in
Older versions can be found here if needed.
Download
Download TWRP 2.6.3.0 Official (Change Log)
MD5: 22c58a87402b4049f8bafa1b07b1a765
Download TWRP 2.6.3.0a Unofficial
MD5: fd9f7b520bec55c980d0ea39616aa271
Includes these commits on top of 2.6.3.0: Never generate empty backup name, Remove unneeded images, check for space after = too, Improvements to Update_Log_File, Fix checking for file_contexts in updater
GooManager Installation:
Automated installation through GooManager will only work if you have the su binary (root access) on your ROM. If you have just performed unlock or S-OFF, you must use the manual installation method for the first recovery installation.
Install the GooManager application from Google Play
Open GooManager, pull up the menu, and select Install OpenRecoveryScript
Confirm the first prompt, then verify the filename in the second prompt (openrecovery-twrp-2.6.3.0-fireball.img) and confirm again
After the recovery has been installed, pull up the menu and choose Reboot Recovery
Manual Installation:
Requirements: you must have fastboot set up: Windows Guide, Mac Guide, Ubuntu Guide
1) Reboot your phone to the bootloader:
Method 1: Disable fast boot under Settings > Power > Fast boot. Shut down the phone. Hold Volume-Down and Power simultaneously until the phone vibrates. Continue holding volume down, but release the power button. When you reach the bootloader, choose the FASTBOOT menu option using the volume keys to move up/down and the power key to select.
Method 2: If you have adb installed, then with your phone fully booted up, type: adb reboot-bootloader
2) Flash the recovery image using fastboot. Open a terminal and navigate to the directory with the downloaded image. Type:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-fireball.img
When the image has finished flashing (usually less than 10 seconds), issue the command
Code:
fastboot reboot-bootloader
3) Use the volume keys to navigate to BOOTLOADER and then select it with the power key. After the phone finishes scanning for PJ____.zip images, choose RECOVERY from the menu. This will start TWRP recovery.
Themes:
TWRP supports themes! Create a folder called theme within the TWRP folder on your internal storage and copy ui.zip into it. You can either search for themes compatible with the 540x960 resolution (check out the EVO 3D forum for instance) or build your own. Known themes listed below:
Holo TWRP Theme by prairiedogn
HTC TWRP Theme by prairiedogn
Blue Dalek Theme by agentc13
Sports Recovery Themes by lnando84
Gray Theme by lnando84
Themes written for earlier versions of TWRP may not have themed elements for new features. Be sure to compare the user interface before and after applying a theme to make sure everything shows up. You can check the log for errors as well (the middle button on the bottom of the TWRP interface), it will say something like: "unable to load button image" if resources are missing.
Additional Information:
The boot image comes from RUU 2.17.605.2
This build includes HTC Dumlock in case it is needed. S-OFF users can safely ignore it. HTCDev Unlock users (who are still S-ON) can try it out if experiencing trouble writing to the /boot partition. It can be found under Advanced in the recovery.
Credits:
Dees_Troy for adding the Inc 4G to TeamWin's officially supported devices for TWRP
con247 for putting in the original effort to build TWRP on the Inc 4G
utkanos and KemoNine for building assistance
TeamWin for TWRP and their great building guide
CyanogenMod for way too many reasons
Release History:
Official 2.6 - In addition to TWRP's official changes, this version also introduces support for AOSP data encryption. Additionally, Aroma installers should not fail anymore.
Official 2.4 - Builds are now maintained by TeamWin: Change Log
Official 2.3.3.0 - Identical to Build 1.2
Build 1.2 - Mount internal and external SD to computer via USB
Beta 1.1 - HTC Dumlock included
Beta 1.0 - Initial Release
Known issues / Workarounds / To Do
The charging status LED currently does not turn on when the phone is charging. This is really a non-issue since there is a charge level and charging indicator within the recovery.
If the phone is powered off while plugged into USB, it will temporarily reboot into recovery then shut down 20-30sec later.
Source
The device tree is at github.com/cyanogenmod/android_device_htc_fireball.
great, glad to see this coming
Do you think this could get goo manager support? Thanks for all that you do.
Sent from my DROID RAZR using Tapatalk 2
Awesome! Thanks updating now
jamminjon82 said:
Do you think this could get goo manager support? Thanks for all that you do.
Click to expand...
Click to collapse
I need successful user reports for all the features. Once I get confirmation that everything works as expected, I'll submit my device tree to TWRP and ask for official builds. Goo manager support would follow from there.
I updated the build to version 1.1. For those who are S-OFF, there's no difference from 1.0. For those who are S-ON and using HTCDev Unlock (from team fireballas), there's now HTC Dumlock included. I'm still not sure if it is even needed...
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Linch89 said:
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Click to expand...
Click to collapse
Relevant posts about androidsecure:
http://forum.xda-developers.com/showthread.php?t=1934739
http://forum.xda-developers.com/showpost.php?p=27172605&postcount=218
Internal wipe clears out your internal sdcard's media partition (pictures, music)... probably don't want to do that.
Good look glad I didn't. Well as far as I can tell this is recovery is a win pun intended
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
The ability to mount the phone's sdcards on the computer while in TWRP was unknown to me. I'm working on the issue. The attached recovery is a first stab at a fix, let me know if it works (my faith is low though since the devices didn't mount in ubuntu for me).
MD5: 6fa24210afa860c38fef3f2a7d4360d1
Edit: the attached recovery did not fix the issue. I'll try to look into this sometime this week (research presentations and job interviews over the next few weeks so time is very scarce right now).
Linch89 said:
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
Click to expand...
Click to collapse
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Edit: Never Mind, I am running TWRP v2.2.0, this may not have any validity with the OP's version, sorry.
Edit my Edit: OK I just flashed v2.3.3.0 and same goes, I can get in through ADB and I have shell root once in shell. However, the file system looks like it should with "sdcard" and internal and "external-sd" as external. All else seems normal.
DavDoc said:
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Click to expand...
Click to collapse
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
DavDoc said:
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Click to expand...
Click to collapse
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
It doesn't auto mount upon connecting usb, I didn't try mounting it though, through TWRP settings. From what I can tell, both versions work the same, they just have different names for the file structure, and only for the external and internal sdcards - didn't really investigate any other files.
Edit: To answer your first question, no it didn't work in either version. Don't know who's v2.2.0 it is, but it is the recovery that was added into the supercid.auto script.
mdmower said:
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
Click to expand...
Click to collapse
i think they mean usb mounting is gone it is suposed to be under mount option
jose51197 said:
i think they mean usb mounting is gone it is suposed to be under mount option
Click to expand...
Click to collapse
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
mdmower said:
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
Click to expand...
Click to collapse
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Does your .android_secure folder actually have anything in it? Mine is empty on Viper 2.1.1. I just moved an app to SD and the folder is still empty. The reason I ask is because the and-sec folder is correctly mounted and linked to /sdcard/.android_secure when in TWRP.
I've never seen anything in android secure ever on any phone
Linch89 said:
I've never seen anything in android secure ever on any phone
Click to expand...
Click to collapse
On my OG DInc running AOSP that folder would indeed store sdcard apps... strange its different now....
I moved all apps my apps to sd card and I checked android_secure under sdcard and sdcard2 in root explorer and nothings in there. I can't delete the folder though so it must be of some importance
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
I pretty much just need a way to get my zips back to internal storage
Sent from my SCH-I605 using xda app-developers app
trinitystudio said:
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
Click to expand...
Click to collapse
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
qery said:
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
Click to expand...
Click to collapse
thanks ill give it a try and get back with you
ok i found and did what it says it sees my prime but im getting this error now failed to write data 'protocal fault <no status>' *3%
now this
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
trinitystudio said:
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
Click to expand...
Click to collapse
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
alias4ever said:
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
Click to expand...
Click to collapse
i have done that all but putting it on the c:\ drive ....yes im pointed to that folder ill try c and get back to you thanks
edit: try c drive thing still a no go still getting protocol failure
Hardbricked!!!!!!!!!!!!!!
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
trinitystudio said:
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
Click to expand...
Click to collapse
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
alias4ever said:
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
Click to expand...
Click to collapse
What would you plan on doing or what does anyone do with a hardbricked Prime as I am curious? Sorry to hear it.
It happens I have done roms for years from droid one to note2 never had a issue till now it was my own mistake so... I guess nothing to do but trash it prob going today to get Samsung note 8 or 10.1
Sent from my SCH-I605 using xda app-developers app
Do you by any chance have Asus sync running on your pc? It seems that this can interfere with adb.
Try killing all asus related programs on your pc through task manager and then try adb push again.
Sent from my SO-04E using xda app-developers app
This is what I'm curious about too. If there were photos on this SD card before you put it in the device, they will remain intact after a security wipe.
This is unclear to me based on the OP: You got the Bold as a graduation gift and would like to start using it i assume. (I also got this bold a couple days ago after my HTC One S died, bringing me to Blackberry after years of faithful service on Android. The 9900 is a great phone)
When you tried to use the phone, you were prompted to input your BBID credentials, which subsequently failed repeatedly. The phone has since been security wiped due to too many failed attempts. Upon opening the phone, the microSD that you had in there is gone.
After a long time of trying to get things right, i finally got things right.
So here it is:
TWRP RECOVERY 3.2.1-0 FOR THE MOTO X FORCE (KINZIE)
This is an actual port and not a recompile of a different version for another device.
It is not yet official but i intend to submit my device tree, so it gets official.
It is probably never going to be official, but i'll try and provide frequent updates.
Everything *should* work, as far as i was able to test.
I am not sure about encryption though, as i have not encrypted my device, nor do i intend to do so atm.
Encryption should be ok now. (TWRP team has put a lot of effort in this).
Encrypted partitions cannot be read atm.
This would probably also work for the Droid 2 Turbo, if someone finds a way to unlock the BL.
I will try to maintain TWRP for this device, fixes may take a while though as i am not having a lot of time to work on this.
Installation:
1. Unlock your device
2. Download the image
3. Power off the phone
4. Boot to fastboot (VOL DN + POWER)
5. plug your usb cable install via fastboot:
Code:
fastboot flash recovery TWRP_3.2.1-0_Kinzie.img
If you want to keep OTA Update ability you can also temporary boot to TWRP. You would have to repeat this step everytime you want to go to TWRP then:
Code:
fastboot boot TWRP_3.2.1-0_Kinzie.img
Download here:
Version 3.2.1-0
http://www.mediafire.com/file/o6gcj4hhjahf936/TWRP_3.2.1-0_Kinzie.img
Version 3.1.1-0
http://www.mediafire.com/file/y2k08c6m5tazhbo/TWRP_3.1.1-0_Kinzie.img
Version 3.1.0-0
https://www.mediafire.com/?7h4u37ddiohwy45
Credits go out to the people of Teamwin Recovery project for creating this nice piece of software!
And credits go to @Arasthel, who is a great dev!
Official Changelog 3.2.1-0
Fixes for kinzie:
- USB OTG now working
- TWRP internal folder should be now accessible via /sdcard symlink
- cm updater is reporting device correctly now as kinzie
Amazing, the most beautiful and wanted TWRP version! Tested and working perfectly! Using it as my recovery, not boot only.
Enviado de meu XT1580 usando Tapatalk
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Arasthel said:
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Click to expand...
Click to collapse
To be honest, differences are marginal at this point, as of now we've got the fstabs by-name assignments there is almost no way of messing things up with partition assignments (which is kinda the no. 1 thing to do right in recovery). At the moment i am still using a prebuilt kernel and ramdisk i extracted from the device, because when i started building the device tree the kernel sources haven't been available. And when they finally were i decided to first fix the issues i already had, before introducing new ones. The whole graphics sub routines of TWRP (minuitwrp) recently had undergone a pretty big overhaul and so we've lost ability to flip screen on the way. I recently made a patch to fix this for overlay devices (which the kinzie is), and since then, TWRP is running fine on the native kinzie build. The overhaul also made the use of a custom graphics.c obsolete. (I suspect you had to use that?) I made the device tree mostly from scratch, only looking at similiarities at trees from hima and clark. (Hima has msm8994 too, clark has a different chipset as you know, but is a moto device).
You can have a look at it here. Please note that this is not absolute latest configuration (haven't uploaded it yet) and it still needs a little cleanup before submission. After that, i am going to throw in kernel sources from motorola and fetch the prebuilts necessary.
If you are interested in learning more you can contact me via PM.
Just flashed and working 100%. Moto X force BR version.
Thx a lot dude :good: just flashed and working.
no more upside/down issue :silly:
and nice theme btw
Thanks a lot mate! working as expected.
Perfect and beauty one! Thanks!
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
marzliak said:
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
Click to expand...
Click to collapse
I'll look into it as soon as I can. Might also be a general issue in twrp.
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Moderator Edit: @MuyKurioso - it is not necessary or desirable to quote the entire OP. Some users have limited bandwidth or are Mobile - this can affect page load times. Please consider this in the future. Thanks.
Are you currently trying to port CM to Kinzie? Or just waiting to help out someone? Just curious, and thanks for all your hard work in this recovery!
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Does this work for the turbo 2?
Xadro said:
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Click to expand...
Click to collapse
I have backed up to the internal emulated sdcard.
I wanted to sync the folder and backup to my NAS
Sent from my XT1580 using Tapatalk
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
AztekSoul said:
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Click to expand...
Click to collapse
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Sent from my XT1580 using Tapatalk
fubofo said:
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Click to expand...
Click to collapse
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Xadro said:
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Click to expand...
Click to collapse
Thanks, managed to chown the directory in terminal emulator. All works great now, thanks
Sent from my XT1580 using Tapatalk
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
rodrigoger said:
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
Click to expand...
Click to collapse
There is something for you in the OP