Related
Hi folks,
we have some lucky users among us with a generic (Dev) IMEI - some of these are able to get OTA updates, thought for testusers and/or developers from Samsung, after they install latest Test firmware XXLSA from sammobile....some got updates up to XXLSC and already provided a dump. Others got updates up to XXLSD (and maybe higher in future - who knows, where the journey ends...), but don't know what to do to share this firmware with us 'Flashaholics' here on xda and other forums...
Now, as more and more people asking me (why ever me...) how to make a system dump from Stock Firmware, I decided to write a short 'HowTo for Dummies'. So if you know about someone, who has a unknown Test Firmware installed, or YOU are the chosen one, just follow this tutorial and make us happy
This is just one way of several to do this - but as I think, it is the easiest way for newbies (without having to use Android SDK and adb shell on PC --> that's what experienced would do )
Prerequisites:
- at least 1,4 GB free space on internal SDcard
- a brain (and above 80 IQ-points...)!!!!!
Step 1) Rooting your Stock Firmware (thx to Phil for the steps, I just copy/pasted them) --> if you already have Root + busybox installed, go to Step 2) directly
download this Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip and this cwm-non-touch-6.0.1.4-i9100.zip
Put the previously downloaded cwm-non-touch-6.0.x.x-i9100.zip file on your external sd card
Copy the Root_XXX.zip file you downloaded to internal or external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-non-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the "Root_XXX.zip" file and hit power button to install it.
It will add SuperSU or Superuser last version apk to system/app, last superuser binary (su) to system/xbin and busybox last version to system/xbin, all with correct file permissions.
Reboot and you get permanent root + busybox installed on your stock kernel.
(You can easily unroot your device afterwards...it is also described in Phils thread, where I took all these from: [20 Sep 2012][ICS]Universal Rooting for most ICS phones, Any ROM, now with CWM6 )
Step 2) Making a complete System Dump of Stock Firmware:
Install 'Terminal Emulator' from Playstore
Open Terminal Emulator
type 'su' with your internal keyboard and press return button
grant Superuser access on upcoming popup window
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin
==> this will generate 'modem.bin' (= Modem) on your internal SDcard (will be finished after a few seconds)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p5 of=/sdcard/zImage
==> this will generate 'zImage' (= Kernel) on your internal SDcard (will be finished after a few seconds)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hidden.img
==> this will generate 'hidden.img' (= preload partition) on your internal SDcard (will be finished after a few minutes, as it is more then 300 mb!)
now type the following line and press return button after finished typing:
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img
==> this will generate 'factoryfs.img' (= system partition) on your internal SDcard (will be finished after a few minutes, as it is more then 800 mb!)
Now you have the following output / files on your internal SDcard:
modem.bin
zImage
hidden.img
factoryfs.img
==> zip these 4 together and upload them to a hoster ==> post the link here and devs can start building a new ROM (Stock + CustomROMs) and kernel devs (now we luckily have Phil for that) can preroot the kernel + put in CWM recovery.
That's all and really very very easy....
Disclaimer:
I am not responsible for any damages - it is your risk (though it is not a dangerous thing to do!)
hope this will be a very good guide in getting the new leaked rom from sammy
Nicely done my friend this should ease up on some of the users (the ones who get updates for us XD)
Congratulations on this, now you see why community loves you soooo. liebe endet nie !!
es ein vergnugen es zu lesen. gute arbeit eybee :good:
Thank very much boss
Hope you will be one of the prof when xda university will open.
Thank you very much
Hope now when we will see LS(any letter) it will be with the links of the dump
Envoyé depuis mon GT-N7000 avec Tapatalk
Funny
Envoyé depuis mon GT-N7000 avec Tapatalk
Cool bro thanks but you can use the supersu.zip and the busybox.zip from stock recovery
Tapatalking on my n7000
msedek said:
Cool bro thanks but you can use the supersu.zip and the busybox.zip from stock recovery
Tapatalking on my n7000
Click to expand...
Click to collapse
It was easy copy paste for me in the rooting part....you can root and install busybox in 567 different ways...in the end the result counts
Clicked for Newsworthy article. :thumbup:
Sounds really simple for someone who doesn't have the second prerequisite.
Back uped the info.
Sent from my GT-N7000 using Tapatalk 2
Sharing your valuable knowledge and experience is priceless for those who are interested. Well, me, I simply follow pros like you.
Sent from my GT-N7000 using xda premium
In addition to Step 2:
I made the dumps from my PC with a connected device with "adb", so I could copy them to the harddisk directly.
"adb devices" for checking if connection is established, "adb shell" switching to the device, "su" for root access, and then the commands eybee1970 explained in detail.
After that I fetched the files in my file manager from the connected device.
I prefer to work with terminal windows on the PC and not on the device.
With this you do not need Step 1 - because I didn't
another great one from eyebee
great guide for learners like me
thanks
ThaiDai said:
In addition to Step 2:
I made the dumps from my PC with a connected device with "adb", so I could copy them to the harddisk directly.
"adb devices" for checking if connection is established, "adb shell" switching to the device, "su" for root access, and then the commands eybee1970 explained in detail.
After that I fetched the files in my file manager from the connected device.
I prefer to work with terminal windows on the PC and not on the device.
With this you do not need Step 1 - because I didn't
Click to expand...
Click to collapse
That's why I said 'for Dummies'....no PC, no Android SDK, no adb shell...just the device
This is a superb guide! cheers eybee
Deleted
Sent from my GT-N7000 using xda app-developers app
Now the history rolls back...
as people raced to create their own custom roms.
The chosen ones with their great knowledge was kind enough to uncover about the custom rom things and shared it with some tutorials here in xda-dev for people who needed it.
Just like the old time...when WinMo has a bright future here.
Thanks a million for devs and chefs at xda-dev who always spread the lights.
ZacDerbyshire said:
Great guide. A little off topic but I don't know where else to ask and you are an expert in ROM making. How do I put things like all multiwindow apps and 4 way reboot in the ROM build before it goes on the phone? Sorry again for it being in here, can't find anywhere else to ask.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
4Way reboot mod is at the system/framwork/ directory "android.policy.jar" file is responsible for this stuff....
as for all multi apps after an investigation it appeared it looked for a certain statement to know whether its a sammy app patching that code to the launcher and editting the policy for this feature too gets you all apps access (almost all) as some just dont work....
there are plenty of guides and tutorials over the internet and forums... on different phones mostly but with a little time you can manage everything as you want to so READ some enjoy!
i'am guessing we need to start writing more tutorials in the N7000 section in here we have no knowledge sharing mostly developing and some new guys are ready to try their own so we have to share everything it started with eybee (thanks to him) and hopefully will continue with all other guys who do mods.... no matter how small it can be usefull.
believe it or not but even devs assist each other with mods its not like each one was born with all that OP-Code in his head
Ah...good guide eybee.Let me see if i can make a shell script to dump the partitions and make odin roms out of it.I already have scripts to dump and make odin rom for /system,/data partitions.will add preload,kernel and modem to the script.Let me see how my time permits today.Hope the script will help people.But the only drawback is it will work only on linux.Users may use cygwin too for it
Sent from my GT-N7000 using xda app-developers app
eybee1970 said:
That's why I said 'for Dummies'....no PC, no Android SDK, no adb shell...just the device
Click to expand...
Click to collapse
For my case adb shell was not succeed. Device reboots unexpectedly while dumping factoryfs. Maybe file size is too big. Thus I had to use terminal emulator though pc keyboard is much more convenience
Great tutorial!
Sent from my GT-N7000 using xda app-developers app
Two remarks:
Typing something like "dd if=/dev/block/mmcblk0p9 of=/sdcard/factoryfs.img" is never something I would call easy. If you do not have Linux shell commands knowledge, than these are about "50 characters without meaning" that you have to type (on the keyboard of your device - which is even more error-prone).
PC or Note: it is never dummy-simple.
Making a batch wich automatically generates an ROM installable with ODIN (so the result are tars) is dangerous.
The difference between "dump" and "dumb" isn't so big - as I just proved myself.
When you make a batch with a complete process from dumping, copying, building to a "blob" installable with Odin there will be no step in the process for quality control.
Example (hurts to write this): If there's something in the original Rom you are dumping that couldn't be shared then it makes its way through the process in to the final Rom. And the dummy user of these scripts will never know or can protect himself from it.
Only pro from this: after learning this the hard way you don't feel like a dummy user anymore.
Hi all,
I have a few small concerns about "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" - http://forum.xda-developers.com/showthread.php?t=1967124
I've now rooted my phone and done almost everything exactly as instructed (I also fell into the boot-recovery.p in system folder-trap, but got up again). I finished doing steps 1-5 including Nandroid backup from CWM recovery. Am now back at step 6: "Remember where you left off in 2nd step above? Well now you can go back and complete the partition backup of the efs folders. You should be left with 4 backup files for this final section of the backup process". This I don't fully understand.... I understand that I need to go back to this page: http://forum.xda-developers.com/showpost.php?p=33048706&postcount=1
And what I previously did at step 2 is the 3 headlines shown below with *....*. What I didn't do at step 2 is (---*....*---) below:
-------------------------------------
*Setting up QPST with your PC:*
*Backing Up IMEI / NV Data:*
(---*Restoring IMEI / NV Data:*---)
*Restore USB Settings after Backup / Restore:*
(---*Recovering IMEI And Data Connection After Flashing WRONG Root Package Intended For I9300:*---)
-------------------------------------
I don't really see any headlines regarding "partition backup of the efs folders"? But in the top it says: "Click HERE for information on the long awaited and all new EFS Professional v2.0 including download! Now supporting Qualcomm devices!". I downloaded this program, ran it but am a bit confused about all these settings and options in these programs. I'm also confused because I think that the "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" is a bit unclear here. I think it's unclear how I exactly get these 4 backup files aka "partition backup of the efs folders". I've tried to search the forum for instructions and it seems like I can do:
1) Download ktool app to phone - http://forum.xda-developers.com/showthread.php?t=1314719
2a) Install terminal emulator and issue the command: "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096" - http://forum.xda-developers.com/showthread.php?t=2269318
2b) Similar method, I think - with busybox and a few other commands: http://forum.xda-developers.com/showthread.php?t=1089039
3) Just copy/paste the /efs folder - http://forum.xda-developers.com/showthread.php?t=2369049
4) Use efs backup windows program - http://forum.xda-developers.com/showthread.php?t=1673059
Question 1: Are there other methods?
Question 2: Are any of these methods better or worser than the other methods? Consider the worst-possible cases, i.e. a some time the phone gets bricked. I suppose using a phone app for trying to restore /efs isn't a good strategy if you cannot even boot the phone?
Question 3: Do all backup /efs-folder applications do the same thing, only copy /efs so I don't need to use "multiple strategies" / "multiple methods"?
Question 4: Do you recommend something, e.g. using multiple of the methods above ("multiple strategies")?
I just would like to ask, because I think the "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305" is a bit unclear here and right now I don't really know what exactly to do. I think I'll go for method 3 above if all methods are equally appropriate...? I've never tried to restore /efs and hope I'll never have to do it...
If you have an i9305, you're in the wrong section. This is the i9300 Q&A within the i9300/i9305 section. The i9305 has it's own Q&A given that it has a different hardware specification.
If you have an i9305, please use the /!\ report button top right of your post to report the thread be moved by a moderator.
If you have the i9300, please clarify this in post 1 and remove the link to teh i9305 thread as yuou shouldn't use guides / info about other devices as you could end up bricking your device.
rootSU said:
If you have an i9305, you're in the wrong section. This is the i9300 Q&A within the i9300/i9305 section. The i9305 has it's own Q&A given that it has a different hardware specification.
Click to expand...
Click to collapse
Thank you very much - thread is now moved! I hope someone can still explain something to me about the 4 questions.
deleted
JJEgan said:
http://forum.xda-developers.com/showthread.php?t=1946915
Click to expand...
Click to collapse
I already linked to this page - this page is what my 4 questions are about. What are you trying to say with the same link to the same page I already linked to? I mean: We're only talking about EFS backup, ok? I also wrote that I did all the steps except doing the EFS backup - did you read that? At least I don't understand your answer, because I don't think your reply answers any of the 4 questions about EFS backup.
I give up .
newsboost said:
...
2a) Install terminal emulator and issue the command: "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096" - http://forum.xda-developers.com/showthread.php?t=2269318
2b) Similar method, I think - with busybox and a few other commands: http://forum.xda-developers.com/showthread.php?t=1089039
...
Click to expand...
Click to collapse
Also a very similar and IMHO simpler method is to use ADB with a very similar command line (it is also much simpler since you will be typing on your computer on presumably a normal keyboard and big screen).
To do that in ADB you need to have USB debugging enabled in your ROM (and very likely you need to be rooted). But even simpler/nicer is to actually use ADB with a smarter recovery (I am using Philz on my i9300) - in those ADB is enabled and you are rooted by default
JJEgan said:
Your questions refer to other phones not I9305.
AT Note
I9003
Samsung Vibrant
GT N7100
I9100.
So i don't have a clue about these other phones EFS backup and pointed you to the I9305 EFS thread as its not the same as others .
I did not realize you had edited your post that was in the I9300 forum.
Click to expand...
Click to collapse
I don't understand you. Why do you think my questions are not for the I9305?
I have NOT - I repeat: NOT edited anything in my original post, but as you can see the original post was in the wrong location and it was then moved to the correct location where it is now. I have no idea why you think my questions are not about the I9305 ?
Ok, now I think maybe I can guess what you mean:
The first question I ask is not very clear, agreed. I write: I think it's unclear how I exactly get these 4 backup files aka "partition backup of the efs folders" + "I don't really see any headlines regarding "partition backup of the efs folders"? " - so sorry about that. But my first question is: What do I do now, because the instructions seems unclear?
The next 4 questions are actually also for the I9305. Maybe you think this shouldn't work on the I9305 but AFAICS I would guess all the mentioned methods are valid on the I9305. Maybe you don't know the answer then - that's fair. My problem is that I haven't made my EFS backup yet, because I wanted to hear you guys first. I write that I'm stuck because the instructions are unclear to me and then I searched the forum for alternative methods. Am I supposed to use the "new EFS Professional v2.0" program and is this the recommended method for EFS backup on the I9305?
xclub_101 said:
Also a very similar and IMHO simpler method is to use ADB with a very similar command line (it is also much simpler since you will be typing on your computer on presumably a normal keyboard and big screen).
To do that in ADB you need to have USB debugging enabled in your ROM (and very likely you need to be rooted). But even simpler/nicer is to actually use ADB with a smarter recovery (I am using Philz on my i9300) - in those ADB is enabled and you are rooted by default
Click to expand...
Click to collapse
Ok, so you agree with my theory that all the mentioned methods are equally good and basically no method is better/worser than the others as long as you have a backup on your pc harddisk?
I think you understood the questions correctly - thank you very much for that. This implies that I can use all methods and there's no difference and nothing is "recommended" in favor of other methods, is this correct? I've never bricked my phone, so I'm a bit unsure here...
Thanks.
JJEgan said:
I give up .
Click to expand...
Click to collapse
Sorry, but I don't understand you. You only linked to a page which I already linked to and you didn't write any explanation or anything. I then explain that I already linked to this page - this page is what my 4 questions are about and I'm asking about how to proceed with making the EFS backup, because I think the page is unclear. I ask which tool is recommended. I ask what you are trying to say with the same link to the same page I already linked to?
I also wrote that I did all the steps except doing the EFS backup - did you read that? At least I don't understand your answer, because I don't think your reply answers any of the 4 questions about EFS backup. Then you deleted your link again (which I already posted to in the first place) and you write that you "give up" - sorry, but I don't understand a word of that. I'm very sorry - not trying to be rude or anything, but I don't have a clue about what you tried to say.
Another problem which I forgot to state earlier is that when I run the program "EFS Professional 2.0.68" I get this message:
BusyBox v.1.21.0 is an unstable release!
If you encounter any issues, it's strongly recommended that you downgrade to BusyBox v.1.20.2 before continuing to use EFS Professional.
Please visit (webpage) for more information.
Click to expand...
Click to collapse
This makes me afraid of making the EFS backup using this tool and this is also why I ask these 4 questions, before I actually do the EFS backup... Again: Not trying to be rude - so if I'm a noob, asking noob questions or something. I had the I9000 for 2 years and never really had any problems, forgot how I rooted the phone and how I made EFS backup. Now I get this "busybox"-warning, which I don't like... If I try to backup using this tool I use the "Backup"-tab + under "Backup Options" + "Device Filter" I select "*** All Partitions ***" and then I get:
"readlink: applet not found. Please install a BusyBox binary that contains the required applet. Busybox v1.20.2-Stericson is recommended for compatibility"
Click to expand...
Click to collapse
What now? The program hangs and nothing happens and I have to kill it - this made me post the 4 questions in the top. Sorry that I didn't give these details before now - now you got the whole situation I'm in and the background for my questions...
newsboost said:
Hi all,
I have a few small concerns about "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" - http://forum.xda-developers.com/showthread.php?t=1967124
..............
I'm also confused because I think that the "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" is a bit unclear here. I think it's unclear how I exactly get these 4 backup files aka "partition backup of the efs folders". I've tried to search the forum for instructions and it seems like I can do:
1) Download ktool app to phone - http://forum.xda-developers.com/showthread.php?t=1314719
2a) Install terminal emulator and issue the command: "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096" - http://forum.xda-developers.com/showthread.php?t=2269318
2b) Similar method, I think - with busybox and a few other commands: http://forum.xda-developers.com/showthread.php?t=1089039
3) Just copy/paste the /efs folder - http://forum.xda-developers.com/showthread.php?t=2369049
4) Use efs backup windows program - http://forum.xda-developers.com/showthread.php?t=1673059
Question 1: Are there other methods?
Question 2: Are any of these methods better or worser than the other methods? Consider the worst-possible cases, i.e. a some time the phone gets bricked. I suppose using a phone app for trying to restore /efs isn't a good strategy if you cannot even boot the phone?
Question 3: Do all backup /efs-folder applications do the same thing, only copy /efs so I don't need to use "multiple strategies" / "multiple methods"?
Question 4: Do you recommend something, e.g. using multiple of the methods above ("multiple strategies")?
Click to expand...
Click to collapse
Preliminary answers to unclear instructions (I edited this post and add the busybox question to the EFS-thread where I think it belongs):
Answer 1: xclub_101 proposed ADB and/or Philz? I haven't tried this yet - not sure if I want to try it.
Answer 2: I would like to hear other opinions.
Answer 3: I don't understand it - using the "root explorer"-method provides a backup of /efs around 2-300 KB. I then tried the "Samsung Galaxy S3 ToolKit" - it produces "efs.img" around 20.480 KB + efs.tar: 205 KB. The "terminal emulator-strategy" gives also a 20.480 KB efs.img-file, but not exactly the same size as the one produced by "Samsung Galaxy S3 Toolkit". So I must conclude that not all applications/methods produce the same /efs-backup. This is pretty weird, I think...?
Answer 4: Now I have a backup using 3 different "strategies"/methods. By the way, I found out ktool is only for I9300 - weird in my opinion because the /efs folder is the same on both I9300 and I9305 and both the 20.480 KB files are produced using commands that work on other phones than the I9305 too...
newsboost said:
Ok, so you agree with my theory that all the mentioned methods are equally good and basically no method is better/worser than the others as long as you have a backup on your pc harddisk?
I think you understood the questions correctly - thank you very much for that. This implies that I can use all methods and there's no difference and nothing is "recommended" in favor of other methods, is this correct? I've never bricked my phone, so I'm a bit unsure here...
Thanks.
Click to expand...
Click to collapse
All methods are very similar indeed - the only thing that you need to keep in mind is HOW you are going to restore the backup if things really go bad.
The "partition physical image" (with dd or similar) is IMHO simpler under all "normal" circumstances (and it might also hold older deleted files that other methods might not even see) but results in a slightly larger file. The only drawback that I see is if somehow you get bad sectors just in the middle of the memory for that partition - but as far as I know that is not really possible with modern NAND setups that have wear-leveling incorporated in their firmware.
xclub_101 said:
All methods are very similar indeed - the only thing that you need to keep in mind is HOW you are going to restore the backup if things really go bad.
The "partition physical image" (with dd or similar) is IMHO simpler under all "normal" circumstances (and it might also hold older deleted files that other methods might not even see) but results in a slightly larger file. The only drawback that I see is if somehow you get bad sectors just in the middle of the memory for that partition - but as far as I know that is not really possible with modern NAND setups that have wear-leveling incorporated in their firmware.
Click to expand...
Click to collapse
Thank you very much - I'm almost satisfied and relaxed now
I'm very happy with the "dd"-method, because it produces a file around 20 MB - the bigger the better, IMHO - better backup too much than too little!
If something happens to my phone, e.g. the /efs-partition gets corrupt, can I always expect that I can boot up the phone, put the backup on my external SD-card and start up a terminal emulator program and then use the "dd"-method to restore /efs? Or should I use the ADB-commands (not exactly sure how to do it). Most important: I have the impression that my two 20 MB backups are fine...
Q&A for [TOOLS] Touchpad Toolbox
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I guess I am an idiot because I cannot seem to get 3 downloads that work.
the fat kid said:
i appreciate the quick response, so im throwing in the zip file that says " update-cwm-jcs>>>>>>>>>>>>" along with the "gapps-kk>>>>>>>"
and then unmounting media volume?
again, thank you,.
---------- Post added at 02:47 AM ---------- Previous post was at 02:41 AM ----------
edit: just tried all 3 of the recovery files in the op and it still says same error message. any ideas? should i be renaming this from update-cwm blah blah, to the format that it is saying is accepted such as,
It will recognize as a compatible KitKat/DataMedia ROM files that look like:
cm-11-*-tenderloin.zip or
ev_tenderloin-nightly-2014.??.??.zip or
aokp_tenderloin_kitkat_*.zip
again im throwing the gapps-kk-20140105.zip in the ttinstall folder along with the update-cwm-jcs-dm-tenderloin.zip file and then ejecting the tp selecgint unmount media volume and am still getting the error message.
---------- Post added at 03:22 AM ---------- Previous post was at 02:47 AM ----------
geez im a freakin moron.... i had incompatible zip files... sorry folks for the clutter
all other noobs like me WATCH THE VIDEO TWICE.
thanks again, all of you are awesome and hopefully this makes my touchpad relevant again.
Click to expand...
Click to collapse
Would you be so kind as to tell me the 3 downloads you used because I have tried and tried and no success.
Can the Touchpad Toolbox be updated to so that it will accept GAPPS named pa_gapps-*4.4.4-*.zip instead of pa_gapps-*-4.4.2-*.zip?
Either that or remove or allow to skip the requirement that GAPPS zip must be present to do the "Install Android" selection. I eventually worked around it rejecting by renaming the 4.4.4 to 4.4.2 but it will probably frusturate novice users.
tweak42 said:
Can the Touchpad Toolbox be updated to so that it will accept GAPPS named pa_gapps-*4.4.4-*.zip instead of pa_gapps-*-4.4.2-*.zip?
Either that or remove or allow to skip the requirement that GAPPS zip must be present to do the "Install Android" selection. I eventually worked around it rejecting by renaming the 4.4.4 to 4.4.2 but it will probably frusturate novice users.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
TPtoolbox boot menu volume rocker not work.
Hi, I ran the tptoolbox and boots in to menu, but the volume button up or down does work, neither does pressing home. But home and pwer button will reboot device. I tried many times no response from volume rocker in menu. Please help, thanks.
I have the 4G Hp Touchpad 1.5 ghz, dual core 32 gb.
Anyone know if the charging dock will still work following an android installation?
Also, I will search for compatible rom builds, but do themes work as well? (Not sure why they wouldn't, just checking)
sj
Sent from my gTab3 (SM-T210R) on NoleKat v1.4 using [email protected] HD Mobile Pro
sjsharksfan420 said:
Anyone know if the charging dock will still work following an android installation?
Also, I will search for compatible rom builds, but do themes work as well? (Not sure why they wouldn't, just checking)
sj
Sent from my gTab3 (SM-T210R) on NoleKat v1.4 using [email protected] HD Mobile Pro
Click to expand...
Click to collapse
Yes the Touchstone charging dock works on android...
TP Toolbox failed; I'm OS-less; please help
I'm on a Mac.
I can't figure out how to make tptoolbox work on the Mac.
I went to a frustrated friend with a PC (Windows) who did not allow me enough time to complete my task.
My Touchpad is now OS-less, as in no OS; no WebOS, no Android.
I successfully did a full data wipe, twice. Thus no OS.
I couldn't get past the next step, install Android, on TPToolbox.
I got stimied after trying to copy the three files to the ttinstall folder. It said a proper recovery file was not found.
I followed the steps above to a T. I copied and pasted the three files from the windows batch to the ttinstall.
I realize in those three files there were no gapps, no recovery, no kitkat files.
So I hope I copied the right three.
Anyway, my frustrated impatient friend kicked me out, so I have no access to a PC anymore (just my old faithful Mac); I have a TP without an operating system on it; and I have no idea how to proceed (as I don't know which three files I'm supposed to copy and paste as it seems the ones I did copy and paste weren't the ones and there's no Gapps, no Recovery and no Android KitKat installs anywhere (I thought that would be within the TP Toolbox programme itself.)
Like I said, I clicked on the correct links, I went with JCSullins first link vs. the other two.
So somebody, anybody, write me back if they know either how I can proceed, or if I can just send you my TP and you can do a big favour for a small nobody.
Thanks everybody.
If not, anyone wanna buy a TP with no OS?
I still need help. HELP!
I still need help. Anybody? HELP!!!
vizspace said:
I'm on a Mac.
I can't figure out how to make tptoolbox work on the Mac.
I went to a frustrated friend with a PC (Windows) who did not allow me enough time to complete my task.
My Touchpad is now OS-less, as in no OS; no WebOS, no Android.
I successfully did a full data wipe, twice. Thus no OS.
I couldn't get past the next step, install Android, on TPToolbox.
I got stimied after trying to copy the three files to the ttinstall folder. It said a proper recovery file was not found.
I followed the steps above to a T. I copied and pasted the three files from the windows batch to the ttinstall.
I realize in those three files there were no gapps, no recovery, no kitkat files.
So I hope I copied the right three.
Anyway, my frustrated impatient friend kicked me out, so I have no access to a PC anymore (just my old faithful Mac); I have a TP without an operating system on it; and I have no idea how to proceed (as I don't know which three files I'm supposed to copy and paste as it seems the ones I did copy and paste weren't the ones and there's no Gapps, no Recovery and no Android KitKat installs anywhere (I thought that would be within the TP Toolbox programme itself.)
Like I said, I clicked on the correct links, I went with JCSullins first link vs. the other two.
So somebody, anybody, write me back if they know either how I can proceed, or if I can just send you my TP and you can do a big favour for a small nobody.
Thanks everybody.
If not, anyone wanna buy a TP with no OS?
Click to expand...
Click to collapse
Have you tried to install it using jcsullins recommendation that you use the Linux way with Mac?
Kit Kat working
OK, like the chap above, I moved the wrong three files into the ttinstall folder. I figured that out. It's the way the thread was written, easy to get confused as they have links right below and say it's those, when in fact it is not (a gapps, recovery and rom need to be moved in there, not the data version of android as that link downloads). Anyway, I sorted it out. Just putting closure on that. Thanks JCSullins! Now we need a Mac version so I need not borrow a friends PC laptop.
vizspace said:
I'm on a Mac.
I can't figure out how to make tptoolbox work on the Mac.
I went to a frustrated friend with a PC (Windows) who did not allow me enough time to complete my task.
My Touchpad is now OS-less, as in no OS; no WebOS, no Android.
I successfully did a full data wipe, twice. Thus no OS.
I couldn't get past the next step, install Android, on TPToolbox.
I got stimied after trying to copy the three files to the ttinstall folder. It said a proper recovery file was not found.
I followed the steps above to a T. I copied and pasted the three files from the windows batch to the ttinstall.
I realize in those three files there were no gapps, no recovery, no kitkat files.
So I hope I copied the right three.
Anyway, my frustrated impatient friend kicked me out, so I have no access to a PC anymore (just my old faithful Mac); I have a TP without an operating system on it; and I have no idea how to proceed (as I don't know which three files I'm supposed to copy and paste as it seems the ones I did copy and paste weren't the ones and there's no Gapps, no Recovery and no Android KitKat installs anywhere (I thought that would be within the TP Toolbox programme itself.)
Like I said, I clicked on the correct links, I went with JCSullins first link vs. the other two.
So somebody, anybody, write me back if they know either how I can proceed, or if I can just send you my TP and you can do a big favour for a small nobody.
Thanks everybody.
If not, anyone wanna buy a TP with no OS?
Click to expand...
Click to collapse
vizspace said:
--SNIP--
Now we need a Mac version so I need not borrow a friends PC laptop.
Click to expand...
Click to collapse
Have you tried running the script in terminal as jcsullins suggested?
C) Run the script provided with TPToolbox
Extract the contents of the TPToolbox zip file from above.
Navigate to the tptoolbox_v40 directory that was extracted from the zip.
On Windows, run the batch file named tptb_v40_win.bat
On Linux, run the script named tptb_v40_nix.sh
On Mac, try what I said for Linux and let me know what happens.
Click to expand...
Click to collapse
About the .sh file on a Mac; and, question about transferring files
shumash said:
Have you tried running the script in terminal as jcsullins suggested?
Click to expand...
Click to collapse
Hi Shumash, Thank you for writing and being interactive. Yes I did do as suggested and tried running the .sh (linux) file on my Mac. The file opened with TextWrangler and read:
#!/bin/sh
# This script is Copyright (c) 2014 James Sullins, All rights reserved.
# James (JC) Sullins, aka jcsullins
# No modifications or distribution without permission
TPTB=TPToolbox-2014-05-18-v40.bin
if [ \! -r ${TPTB} ];
then
echo "Cannot find Touchpad Toolbox binary file ${TPTB}"
exit 1
fi
echo "Checking novacom service ..."
novacom -l
rc=$?
if [ $rc -ne 0 ];
then
if [ $rc -eq 1 ];
then
echo "Cannot find novacomd service. Try rebooting or re-installing novacomd"
exit 2
elif [ $rc -eq 127 ];
then
echo "Unable to find novacom program. Try re-installing novacomd"
exit 4
else
echo "Unknown error rc=$rc checking for novacom service. (novacom -l)"
exit 3
fi
fi
echo "Loading TPToolbox ..."
novacom boot mem:// < ${TPTB}
rc=$?
if [ $rc -ne 0 ];
then
if [ $rc -eq 1 ];
then
echo "Cannot connect to Touchpad."
echo "Make sure Touchpad is connected with USB cable."
echo "Make sure Touchpad is in webOS Recovery (bootie) mode."
echo " (where big USB symbol shows on Touchpad screen)"
exit 5
else
echo "Unknown error rc=$rc loading TPToolbox (via novacom boot)."
exit 6
fi
fi
I did a quick search online and found that Macs don't handle the .sh command, rather the command is, believe it or not, .command.
More that that I'm a novice. So I can't say.
And that's when I went to borrow a friend's PC whereupon I double clicked the .win file, extracted it, then ran it in the ensuing window no problem.
--------------------
Now I'm glad someone is reading this thread. I have a question for you (or anyone). Now that I've TP Toolbox'd my HP Touchpad (and I did not select the option to install WebOS on it), how do I transfer files from my Mac (preferred method) to the HP Touchpad now?
I put it in recovery mode (the big USB sign) but it didn't show up on my Mac desktop. It was unrecognized in the Finder too.
So I went back to my friend on hands and knees and am now using TP Toolbox to put an updated file into the ttinstall folder. Is TP Toolbox now the only way to get files on and off my Touchpad? Say it ain't so (and walk me through the process if it ain't so).
There must be an easier way. What am I to do? Please help. Thanks.
vizspace said:
Hi Shumash, Thank you for writing and being interactive. Yes I did do as suggested and tried running the .sh (linux) file on my Mac. The file opened with TextWrangler and read:
--SNIP--
There must be an easier way. What am I to do? Please help. Thanks.
Click to expand...
Click to collapse
From a search on Google (I don't have a Mac):
First in terminal make the script executable by typing:
chmod a+x (yourscriptname)
Then in finder right-click your file and select "Open with" and then "Other...".
Here you select the application you want the file to execute into, in this case it would be Terminal. To be able to select terminal you need to switch from "Recommended Applications" to "All Applications".
NOTE that unless you don't want to associate all files with this extension to be run in terminal you should not have "Always Open With" checked.
After clicking OK you should be able to execute the script by simply double-clicking it.
Click to expand...
Click to collapse
file xfer and mac script
1. How do i xfer files from mac to touchpad and back? Need i use tptoolbox or is there anther way?
2. Second quetion, separate from first...
You wrote:
Quote:
First in terminal make the script executable by typing:
chmod a+x (yourscriptname) wrote:
I dont understand that. What is a script name? Is it my computer name? Other? Where would i find this info?
If my name were viz, and it isn't, would i type
chmod a+x (viz)
(With brackets, as you did)
Or
Chmod a+x viz
(Without the brackets)
Again, what is my scriptname?
3. Is this related to quetion 1? Does yor response suggest all files must niw be xferred using tptoolbox (in the method you described) if im using a mac and that there is no other way to accomlish that task?
vizspace said:
1. How do i xfer files from mac to touchpad and back? Need i use tptoolbox or is there anther way?
2. Second quetion, separate from first...
You wrote:
Quote:
First in terminal make the script executable by typing:
chmod a+x (yourscriptname) wrote:
I dont understand that. What is a script name? Is it my computer name? Other? Where would i find this info?
If my name were viz, and it isn't, would i type
chmod a+x (viz)
(With brackets, as you did)
Or
Chmod a+x viz
(Without the brackets)
Again, what is my scriptname?
3. Is this related to quetion 1? Does yor response suggest all files must niw be xferred using tptoolbox (in the method you described) if im using a mac and that there is no other way to accomlish that task?
Click to expand...
Click to collapse
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
vizspace said:
1. How do i xfer files from mac to touchpad and back? Need i use tptoolbox or is there anther way?
2. Second quetion, separate from first...
You wrote:
Quote:
First in terminal make the script executable by typing:
chmod a+x (yourscriptname) wrote:
I dont understand that. What is a script name? Is it my computer name? Other? Where would i find this info?
If my name were viz, and it isn't, would i type
chmod a+x (viz)
(With brackets, as you did)
Or
Chmod a+x viz
(Without the brackets)
Again, what is my scriptname?
3. Is this related to quetion 1? Does yor response suggest all files must niw be xferred using tptoolbox (in the method you described) if im using a mac and that there is no other way to accomlish that task?
Click to expand...
Click to collapse
This link may be of use to you :
https://www.android.com/filetransfer/.
TP Toolbox on a Mac
This system will not allow me to post my questions. It claims I have a URL in my message (which I do not) and won't allow me to post.
Is there another way to contact you?
Another email? Forum? Etc.?
I saved my questions as I can not submit them here.
There's a problem with the XDA forum.
Mac TPToolbox and other juicy issues
shumash said:
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
Click to expand...
Click to collapse
shumash said:
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
Click to expand...
Click to collapse
Thanks. I followed your link (to google) and read many results. The easiest looking result, which almost worked was this:
shumash said:
Google is your friend. Search first, ask second. I'm outta here:
https://www.google.com/?gws_rd=ssl#q=how+to+run+shell+script+mac
Click to expand...
Click to collapse
it was the fourth result, entitled: "How to run a unix shell script from the Mac Finder"
I followed those instructions.
Terminal opened (launched from the Finder window using their noted technique) and here is what was displayed in Terminal: (please note: I exchanged my computer name from it's real name to ABC and XYZ (for this thread; not my real computer name).
Last login: Fri Oct 24 11:27:14 on ttys000
ABC:~ XYZ$ /Users/XYZ/Downloads/HP\ Touchpad\ Tools/tptoolbox_v40/tptb_v40_nix.command ; exit;
Cannot find Touchpad Toolbox binary file TPToolbox-2014-05-18-v40.bin
logout
[Process completed]
I do see the .bin file in the same folder, the TPToolbox folder, as tptb_v40_nix.sh (which, by the way, I duplicated and changed the extension from .sh to .command, prior to searching in Finder as outlined in above links' description).
So I don't know what to do.
I know a lot of things you likely do not know; but you clearly know more about computers than I. Please be patient and explain succinctly.
I tried your method, first replied from , with and without brackets, that didn't help.
--------------------------------------------------------------
Regarding Android File Transfer, and I thank the contributor below for chiming in with that advice, I've used that, but it only works sometimes. It is not reliable; and doesn't see ALL the files (as a WebOS USB connection to my Mac used to).
Is there some way to put the HP Touchpad into USB mode and connect it to my Mac (like I used to before on the HP WebOS side (when I had an HP WebOS side)? This may be argument enough to keep the WebOS side. (I can put it in USB mode on Android, but the Mac does not recognize the HP Touchpad at all doing it that way).
---------------------------------------------------------------
Another unrelated question: What ever happened to PreWare? I can't find it anywhere. I installed Jason Robitaille's WebOS QuickInstall 4.5.0 and ran it ok. But when one clicks on the globe, there's no Preware. When one clicks on the Search field , there are zero results (except themes). No Applications, Kernels, Patches, etc.. Nothing. So what ever happened to Preware?
Not having been able to find that, and with Palm no longer supporting WebOS at all after Jan 15, 2015, was the nail in the coffin for WebOS for me. If I can't find Preware and all the apps and tweaks that come along with it, the only reason I can see keeping any WebOS on this tablet at all is to be able to put it in to WebOS USB mode and easily connect it to my Mac.
-----------------------------------------------------------
Lastly, I'm running JCSullins build titled/dated: cm-11-20141002-SNAPSHOT-jcsullins-tenderloin.zip
How do I take a screenshot with this ROM? It used to be Power button and lower volume button, but that screenshot option is no longer available in this JCSullins build, nor in the previous build: cm-11-20140625-SNAPSHOT-jcsullins-tenderloin.zip
Any ideas how to take a screenshot?
---------- Post added at 02:59 PM ---------- Previous post was at 02:43 PM ----------
sstar said:
This link may be of use to you :
https://www.android.com/filetransfer/.
Click to expand...
Click to collapse
Regarding Android File Transfer, and I thank the contributor below for chiming in with that advice, I've used that, but it only works sometimes. It is not reliable; and doesn't see ALL the files (as a WebOS USB connection to my Mac used to).
Is there some way to put the HP Touchpad into USB mode and connect it to my Mac (like I used to before on the HP WebOS side (when I had an HP WebOS side)? This may be argument enough to keep the WebOS side. (I can put it in USB mode on Android, but the Mac does not recognize the HP Touchpad at all doing it that way).
---------------------------------------------------------------
Another unrelated question: What ever happened to PreWare? I can't find it anywhere. I installed Jason Robitaille's WebOS QuickInstall 4.5.0 and ran it ok. But when one clicks on the globe, there's no Preware. When one clicks on the Search field , there are zero results (except themes). No Applications, Kernels, Patches, etc.. Nothing. So what ever happened to Preware?
Not having been able to find that, and with Palm no longer supporting WebOS at all after Jan 15, 2015, was the nail in the coffin for WebOS for me. If I can't find Preware and all the apps and tweaks that come along with it, the only reason I can see keeping any WebOS on this tablet at all is to be able to put it in to WebOS USB mode and easily connect it to my Mac.
vizspace said:
--SNIP--
Last login: Fri Oct 24 11:27:14 on ttys000
ABC:~ XYZ$ /Users/XYZ/Downloads/HP\ Touchpad\ Tools/tptoolbox_v40/tptb_v40_nix.command ; exit;
Cannot find Touchpad Toolbox binary file TPToolbox-2014-05-18-v40.bin
logout
[Process completed]
I do see the .bin file in the same folder, the TPToolbox folder, as tptb_v40_nix.sh (which, by the way, I duplicated and changed the extension from .sh to .command, prior to searching in Finder as outlined in above links' description).
So I don't know what to do.
--SNIP--]
.
Click to expand...
Click to collapse
My guess is that executing the shell script by double-clicking starts it in the wrong directory. Open a terminal in the directory where you have the Toolbox files and execute it from the command line there.
I'm seeing a few posts and qquestions about this with the latest Lollipop release being upon us.
There are several issues here and I wanted to write a quick note aboyut them both for you
1) You cannot SEE your /sdcard data after updating to lollipop
Cause:
Some strange difference between L and KK, where /storage/emulated and /data/media are not "alligned"
Fix:
Open a terminal emulator application and enter the following 2 line command (Press enter after each line)
Code:
su
restorecon -FR /data/media/0
Reboot
2) You have lost permissions to /sdcard
Cause:
You restored all your sdcard data using adb push or MTP whilst booted into recovery. IT screws up your permissions. These methods are fine for single files or backups that you waant to flash or restore, but as soon as you start pushing folders, this issue will be seen
Fix:
In a root explorer app, browse to /data/media/0 and locate your Download folder. Set the permissions for all on Download to read / write (Long press the Download folder > permissions)
Download and flash THIS ZIP from the thread below.
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] (by @osm0sis)
You can also download the zip to a computer and adb push it / MTP via recovery
3) 32 GB device shows the storage of 16 GB version
Cause:
Unknown. This has actually been happening since the Nexus 5 was released
Fix:
Wipe cache and data
4) TWRP backups are missing
Cause:
This is really unknown. We're not even sure that this can be fixed. Some say its a TWRP bug but that cannot be proven.
Sometimes backup folder is empty....
Fix:
Multiple things you can try. Some have to use restorecon command but usually that has to be done after every backup.
Others have just flashed the factory images
Some of us have never had issues so its hard to call it a bug, but there is definitely something funky going on here.
Other times, backups shows as an unknown file type, 0bytes in size. I haven't a specific fix as I have had no feedback from anyone who has fixed it. You could try deleting that unknown file then running the fix above.
Also, please update to TWRP 2.8.3.0
5) All I see in /sdcard is 0 folder
Cause:
Well known issue on /data/media/0 devices - which is the location of the /sdcard. Unsure of the cause on Nexus 5 though
Fix:
/sdcard is in /data/media/0. If you see a 0 folder in /sdcard, you're actually seeing /data/media/0/0.
To fix, just move /data/media/0/0/* to /data/media/0
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
alen1901 said:
I updated without a problem. Be sure to update to latest SDK and to wipe sdcard, eg. clean install.
Sent from Pure Nexus 5
Click to expand...
Click to collapse
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
I have used always Mixplorer and now after flashing 5.0 I cant see nothing under /root. Why so? Something with root permissions? everything else is ok. ( I want to modify build.prop a little )
do I need use some other file explorer?
restorecon -FR /data/media/0 fixed a problem I had with a bad TWRP folder on my Nexus 10 - many thanks!
rootSU said:
Yep, the first issue is fine if you wipe your /sdcard.
The second one is caused by restoring your sdcard afterwards
Click to expand...
Click to collapse
I restored everything except data and android folders back to sdcard, i even restored obb files and no problems at all. It is the best practice for users to restore only their data, not the ones android creates itself. Im sure most people just selects everything and transfer to pc/stick, then copy everything back.
Sent from Pure Nexus 5
Thanks dude. I wish I had this information this morning - would've saved me a lot of sweat.
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
vnvman said:
I'm facing some serious issues today with this.
At first I encountered the issue when installing the flashable update. The OP suggested to execute few command lines in a terminal emulator, but it would only have worked if you rooted your device with cfroot. So I tried to re-root with cfroot with no luck: it kept saying already unlocked. At this point in the settings said I had 3/3 free gigs of storage. Out of desperation I tried to flash every single part of the stock image via fastboot, and re-do the procedure with cfroot and all. However after doing all of that I ended up with 12/12 free gigs, which is what I'm left with right now. I also tried to fix the permissions either with the root explorer app and by flashing the the provided fix, but nothing has happened. No traces of either Titanium backups or whatever files I had before on my storage, it's basically like a new phone with a blank 12 gb storage (keep in mind I have the 32 gb version). I really don't know what to do at this point anymore. Have I by any mean flashed the partitions of a 16 gb variant or something? Will I ever be able to get my storage back? Any help wuld be much appreciated.
Update: apparently I also flashed userdata so my phone believed to be a 16 gb unit. A data wipe fixed it. Obviously my storage is gone but that's my bad, I'll be more careful before udating next time.
Click to expand...
Click to collapse
Yeah that's a different but common issue.
Thank you, rootSU. This fixed my issue.
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
rizhqrd said:
So I have tried the fixes and all of my files are still in sdcard/0 and not just sdcard... Any help I can't figure this out?
Click to expand...
Click to collapse
Move them manually.
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
tomp100 said:
Tried the first solution as it seems to be my issue, but it doesn't seem to work. Any ideas?
Click to expand...
Click to collapse
Please explain your issue.
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
~ # restorecon -FR /data/media/0/
restorecon: invalid option -- F
Click to expand...
Click to collapse
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
-F
Force reset of context to match file_context for customizable files, and the default file context, changing the user, role, range portion as well as the type.
Click to expand...
Click to collapse
RVDigital said:
Hey thanks for this post. I've been through this issue like 3 times and keep forgetting about restorecon.
On that note, I was getting the following output:
The fix appears to work without the "F" flag. Do you know why this is not a valid flag?
According to a general rundown of restorecon, the "F" flag does the following:
Click to expand...
Click to collapse
Not sure but glancing at the Dev preview thread, some had success with this:
restorecon -r /data/media/0/*
Tried both, all that happened is that /sdcard is now blank. /data/media/0 still lists all of the files, but /sdcard itself is empty or unlinked or something. I unfortunately don't know which of the two steps did it.
Quick question, I'm currently on slimkat and plan on clean flashing tonight via bigxies ROM. With this method of fixing the SD card, I won't lose all my data as far as downloads, pictures, etc.?
rootSU said:
Please explain your issue.
Click to expand...
Click to collapse
Essentially, the phone doesn't think it has an SD card. When i click on SD card in root browser, it is empty. Items that were on the SD card in 4.4.4 are now located in data/media/0/0 , and I am unable to move these items to SD. Also, if I try to dowload sonething off the internet, I get a "no SD card" message.
I can confirm that my issues were caused by importing my backed up /SDCard/ data via an "adb push" while in recovery.
If doing the same while the phone is booted into system, permissions are set appropriately and no further action is required.
Thanks again for this post!
I'm starting this thread to move the topic out of another forum.
I encountered the issue of TWRP not being able to write to the internal storage after downgrading to 4.4.4 and only flashing the boot, system & baseband images from the KXE package Motorola provides.
It gave the error message errno=13
It gave the same error on 4.4.4 & 5.0
I had double-checked all permissions & symlinks.
To fix the issue I had to re-flash the KXE recovery, reboot the bootloader & then reflash TWRP 2.8.6.0, then all was well with both 4.4.4 & 5.0
adm1jtg said:
Not sure if this solves the error 13 or not but I can confirm using your process exactly OTG is still broken on 2860 and still works in 2850 so separate issue I would guess but since I need OTG for my backups and restores I will keep using the modded 2850 for now. Can you confirm on your setup if OTG works or not from within twrp. On mine the drive light doesn't even come on, I cannot mount it it just vibrates and I cannot backup to it. All the correct options are there but it cant access the drive at all..
Click to expand...
Click to collapse
@adm1jtg Can you backup to the internal storage?
defcondev said:
@adm1jtg Can you backup to the internal storage?
Click to expand...
Click to collapse
I had other weird issues. Initially mine would backup internally just fine but those files could not be viewed from rom side aka root explorer and such couldn't see files. Only twrp could see the backup files. I then formatted the sdcard and got the error #13 error.
To be honest I FINALLY got my phone setup and backed up the way i want it. The newly re-released 2850 works in all aspects I have tested, aka no error 13, can see files backed up internally on rom side, can see and use otg thumb drive for both backups and restore. Since 2850 works for all I need I really am not overly motivated to test much with 2860 just to be honest with you.
Since I confirmed that OTG is still broken in 2860 that makes using 2860 a deal breaker for me.
adm1jtg said:
I had other weird issues. Initially mine would backup internally just fine but those files could not be viewed from rom side aka root explorer and such couldn't see files. Only twrp could see the backup files. I then formatted the sdcard and got the error #13 error.
To be honest I FINALLY got my phone setup and backed up the way i want it. The newly re-released 2850 works in all aspects I have tested, aka no error 13, can see files backed up internally on rom side, can see and use otg thumb drive for both backups and restore. Since 2850 works for all I need I really am not overly motivated to test much with 2860 just to be honest with you.
Since I confirmed that OTG is still broken in 2860 that makes using 2860 a deal breaker for me.
Click to expand...
Click to collapse
I had that issue as well (not being able to view the TWRP folder);
The folder wasn't showing up in storage/sdcard but was showing up in data/media/0
To fix this there are a couple things you need to do;
1. Using a terminal emulator, execute the following command
su
restorecon -FR /data/media/0/*
2. Using a root-enable file browser, go to /data/media/0/ and change both the Owner & Group of the TWRP folder to "media_rw" (without quotes) and make sure permissions are set to drwxrwxr-x
defcondev said:
I had that issue as well (not being able to view the TWRP folder);
The folder wasn't showing up in storage/sdcard but was showing up in data/media/0
To fix this there are a couple things you need to do;
1. Using a terminal emulator, execute the following command
su
restorecon -FR /data/media/0/*
2. Using a root-enable file browser, go to /data/media/0/ and change both the Owner & Group of the TWRP folder to "media_rw" (without quotes) and make sure permissions are set to drwxrwxr-x
Click to expand...
Click to collapse
Different scenario as i had that happen to me on my 2013 where it went into a 0 folder. This was not the case on the 2014 it LITERALLY didnt exist anywhere, the twrp folder existed with NOTHING under it. But in twrp all files and file structure were visible and working. Mass storage did show the space being taken up of course.
Just to clarify all this mess and all these issues are cause I was going back and forth between lp and kk. It was not REALLY an issue with twrp per say EXCEPT the otg not working... that IS specifically a twrp issue near as i can tell