Related
Uhm, I have a XYBOARD 10.1 inch (WIFI ONLY) And I edited something in Build.PROP. I then restarted at to my surprise it goes completely black after it shows the Motorola DUAL CORE screen. I can get into the recovery. I even Factory Resetted thinking that might help but, Nothing. Is there anything I can do to restore it? Because I'd rather not have an expensive XYBOARD paper weight.
BUMP? I really need help.
if you can get to recovery, you should be able to push stock OS via ADB.. there is a guide in the Xoom development section.
pinoiryder said:
if you can get to recovery, you should be able to push stock OS via ADB.. there is a guide in the Xoom development section.
Click to expand...
Click to collapse
And this is for XYBOARD? Anyway, I can't find the topic...
is there not maybe a way you can pull the build.prop file via adb edit change what you editied, then push it bk via adb???
just outta curiosity, what did you change in the build.prop, also remember, ALWAYS MAKE A BACKUP FIRST!!!! lol
[email protected] said:
is there not maybe a way you can pull the build.prop file via adb edit change what you editied, then push it bk via adb???
just outta curiosity, what did you change in the build.prop, also remember, ALWAYS MAKE A BACKUP FIRST!!!! lol
Click to expand...
Click to collapse
...
How do you make a BackUp on a XYBOARD?
Anyway, Can someone just link me to the needed programs and topic?
ok well since you know, you cant make backups on an XYBOARD then why muck about with it????
[email protected] said:
ok well since you know, you cant make backups on an XYBOARD then why muck about with it????
Click to expand...
Click to collapse
If one doesn't muck around with things, Nothing will ever be discovered.
But I should of waited until someone better at things like this paved the way.
*Beats self with XYBOARD*
SUperFatCatNine said:
If one doesn't muck around with things, Nothing will ever be discovered.
But I should of waited until someone better at things like this paved the way.
*Beats self with XYBOARD*
Click to expand...
Click to collapse
Lol can you not download the original image from motorola and flash it somehow ?? There must be a way surely
Sent from my Xoom using XDA Premium App
Does anyone have the stock build.prop for XYBOARD 10.1 Wifi only?
Also, How do you push it on using ADB?
I think there is no way to solve the problem. Send it to Motorola and will fix it for you.
Sent from my XOOM 2 ME using Tapatalk 2
As the XOOM2/Xyboard has a locked bootloader and no bootstrap for a recovery so your stuck right now until Motorola decides to care about the Android community. Also adb is not possible from what I heard when it can't boot. If you want some help then contact the not many Xyboard devs here "Bricks" as they are always happy to help bricked people.
luke.arran said:
As the XOOM2/Xyboard has a locked bootloader and no bootstrap for a recovery so your stuck right now until Motorola decides to care about the Android community. Also adb is not possible from what I heard when it can't boot. If you want some help then contact the not many Xyboard devs here "Bricks" as they are always happy to help bricked people.
Click to expand...
Click to collapse
It's More of a soft brick. I can get into recovery.
(It's Still Makes a Nice Frisbee or Paper Weight. xD)
SUperFatCatNine said:
It's More of a soft brick. I can get into recovery.
(It's Still Makes a Nice Frisbee or Paper Weight. xD)
Click to expand...
Click to collapse
I'm in the same situation as you as of today (But I have the Verizon Droid Xyboard 10.1). Messed around with the Build.prop and now its not working. I have a copy of the original Build.prop but don't know how I can push it to my tablet.
Adb is not working but fastboot is.
I don't think my original build.prop would be any help to you since I have the 4G version but if you want it let me know and I will send it to you!
Looks like I may have to send it to Motorola :-(
OK guys, no worries... I think I know the solution.
1 - enter in recovery
2 - open cmd on your PC
3 - go to adb and fastboot folder via cmd
4 - type:
Code:
adb devices
adb shell
su
cd /system
rm build.prop
exit
5 - copy original build.prop to this folder (adb one)
6 - type:
Code:
adb push build.prop /system/build.prop
adb reboot
exit
Hope that helps you guys it already helped me (I have the Origina Xoom)
Sent from my MZ601 using XDA Premium HD app
Just one more little thing, I presume you guys have su, as you changed build.prop and recovery (because to install super user recovery is needed!) If you guys don't have them, I'm sorry but don't know a solution...
Sent from my MZ601 using XDA Premium HD app
XxLordxX said:
OK guys, no worries... I think I know the solution.
1 - enter in recovery
2 - open cmd on your PC
3 - go to adb and fastboot folder via cmd
4 - type:
Code:
adb devices
adb shell
su
cd /system
rm build.prop
exit
5 - copy original build.prop to this folder (adb one)
6 - type:
Code:
adb push build.prop /system/build.prop
adb reboot
exit
Hope that helps you guys it already helped me (I have the Origina Xoom)
Sent from my MZ601 using XDA Premium HD app
Click to expand...
Click to collapse
And where might I find CMD?
It's a Windows thing... just search a little on it... try using the menu option to show up everything and search for cmd... Which OS are you using?
Sent from my MZ601 using XDA Premium HD app
I found less detailed guide on rootzwiki created by birdman, but i decided to repost it here in more detail.
* Disclaimer: I do not take any responsibility for anything you do to your phone, whether be brick, break, or somehow mess it up.
Requirements
1. You must have the sdk installed and you are able to access, and use adb and fastboot.
2. You must have debugging enabled on your Nexus 7.
3. Download Su here (Chainfire's thread for supersu) (Thanks Eric_Eric_Eric)
4. Download CWM here. Scroll down to Nexus 7 and choose whether touch or regular.
Pre-Steps
To make this easier, you should put the su zip on the sdcard for later.
1. In terminal, cd to the directory you have your sdk in. Then cd into platform-tools.
2. Type adb push path-to-zip/JB-SuperSU.zip /sdcard
Unlocking Your Nexus 7
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* -
fastboot oem unlock *You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Flash Clockwork Mod Recovery
(You're still inside the bootloader)
4. Flash CWM -
fastboot flash recovery path-to-img/CWM-grouper-recovery.img5. Make CWM Permanent -
1. Boot into recovery2. Go to Mounts and Storage3. Mount /System4. Type in Terminal*adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
If your having trouble gaining shell, try "adb kill-server" then "abd start-server". Couple of my friends had this problem, and this should hopefully fix it.
* For some people, it has been reported that you don't have to replace recovery-from-boot.bak. The flash is enough to make the recovery stick.
Flash Su
1. Go back by pressing power button2. Install the zip in the sdcard
Reboot and your device is now rooted!!
For anybody having trouble trying to use fastboot and come up with a no-permissions error or adb ????????? problem, I created a guide to fix the problem here: [GUIDE]Fix Fastboot and USB
Any ugly splash screens indicating it has been unlocked?
No SD Card!
Not to be a jackass or anything, but this tablet has no SD Card slot...might that require slightly different steps than what you outlined?
jorge_culv said:
Not to be a jackass or anything, but this tablet has no SD Card slot...might that require slightly different steps than what you outlined?
Click to expand...
Click to collapse
I'm sure he meant internal storage.
Is there a way to do this without adb? I'm sort of new to adb....any help would be greatly appreciated. Ty
Sent from my SAMSUNG-SGH-T989 using xda premium
jorge_culv said:
Not to be a jackass or anything, but this tablet has no SD Card slot...might that require slightly different steps than what you outlined?
Click to expand...
Click to collapse
What he wrote about pushing SU to /sdcard is correct. I have a Transformer Prime and ASUS called the internal storage /sdcard, which is a little counter intuitive. I presume the same situation exists with the Nexus 7.
paddycr said:
What he wrote about pushing SU to /sdcard is correct. I have a Transformer Prime and ASUS called the internal storage /sdcard, which is a little counter intuitive. I presume the same situation exists with the Nexus 7.
Click to expand...
Click to collapse
This is correct. There is no emmc internal storage. Its just called sdcard
Sent from my Galaxy Nexus using xda app-developers app
movieaddict said:
Is there a way to do this without adb? I'm sort of new to adb....any help would be greatly appreciated. Ty
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Umm, this no way to do this without adb. I'm working on a one click script which i will be posting later. I am currently in IO Sessions and should have it in the next couple of days.
But an answer, again, no, there isn't. You need to download the sdk, and install the tools. then just cd to platform-tools, and use adb like i said. If your in windows, use adb.exe then the arguments, but if your in linux, just use ./adb. Same thing with fastboot.
khaytsus said:
Any ugly splash screens indicating it has been unlocked?
Click to expand...
Click to collapse
Ya, there is, its the Google logo with the unlocked sign at the bottom, just like the galaxy nexus.
FadedLite said:
Umm, this no way to do this without adb. I'm working on a one click script which i will be posting later. I am currently in IO Sessions and should have it in the next couple of days.
But an answer, again, no, there isn't. You need to download the sdk, and install the tools. then just cd to platform-tools, and use adb like i said. If your in windows, use adb.exe then the arguments, but if your in linux, just use ./adb. Same thing with fastboot.
Click to expand...
Click to collapse
TY very much faded, looking forward to ur one click script!
what exactly does he fastboot OEM unlock do? just curious
Sent from my Amazon Kindle Fire using xda premium
smirkis said:
what exactly does he fastboot OEM unlock do? just curious
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
It tells fastboot to oem unlock the device.
Sent from my GT-P3113 using xda app-developers app
FadedLite said:
This is correct. There is no emmc internal storage. Its just called sdcard
Click to expand...
Click to collapse
I stand corrected, thanks and +1 for setting me straight!
stickmount?
Can someone rooted please test if stickmount works.
Thanks
Guide* and just wait there will be a one click root for this device
Sent from my HTC Vision using xda app-developers app
mintaeroboy said:
Guide* and just wait there will be a one click root for this device
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Ya, that's me trying to write it while trying to take notes during a seminar at IO haha
But ya, I'm working on it right now.
I'm new to the tablet, so this maybe a silly question, but is it possible to use 4ext for recovery instead of CWM? I like the 4ext a lot more for my HTC Glacier.
what would unlocking do? isnt that for phones so you can put other simcards??
r0mmel said:
what would unlocking do? isnt that for phones so you can put other simcards??
Click to expand...
Click to collapse
It is technically "unlocking the boot loader" but unlocking was short and sweet for the title.
Sent from my Galaxy Nexus using xda app-developers app
[GUIDE]
Sent from my Xoom using xda premium
Hey Guys,
I wanted to prepare my TF101G for being sold. So I deleted all the files on the internal storage. Then I went to the recovery and performed a factory reset.
So far so good.
I then unfortunately thought it might be a good idea to format the /system as well. I know it wasn't a good idea.
I tried now various solutions but nothing worked.
What I tried so far:
-pushing a update.zip via ADB. Doesn't work because ADB doesn't see my TF.
-various scripts like wheelie and others. I installed the drivers successfully but when I want to run one of those scripts the connection brakes up and I have to boot into APX mode again.
My TF101G is a BAO which was running Megatron 1.1.6 before the wipe.
The current bootloader is 9.2.2.4
The recovery which still works is I think the touch version from this thread.
http://forum.xda-developers.com/showthread.php?t=1213723
It can't access the SD card.
I hope someone can help me to get my transformer back to life.
I still have a backup on my SD card which I saved in case that the new owner doesn't wants it after a 1 week trial.
formatting system should have no effect on wheelie/NVFlash. Maybe try it on another computer
I tried on the same computer but under Ubuntu instead of windows.
The output is:
Code:
[email protected]:/home/XXX/android/wheelie# ./wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x428008244002117
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
oops didnt see the G for some reason
Wheelie doesn't work on the Tf101G... i think you should get doom in here he would be of more assistance than i can be
Well you have recovery, so go into that and adb push a working stock-based rom (I recommend arhd) then once that's working again you can try the downgrade again.
Thing O Doom said:
Well you have recovery, so go into that and adb push a working stock-based rom (I recommend arhd) then once that's working again you can try the downgrade again.
Click to expand...
Click to collapse
thought of that but he said
"pushing a update.zip via ADB. Doesn't work because ADB doesn't see my TF."
Hmm that recovery supports it, afaik. ADB is just about the only chance here with no NvFlash
I'm a bit confused ATM.
The TF is showing in the device manager but I don't get any feedback via adb.
adb is working though just tried it with my phone.
It shows as Asus Transformer ADB Interface.
Does it say offline?
Thing O Doom said:
Does it say offline?
Click to expand...
Click to collapse
Where?
adb devices
It doesn't show anything. Just empty space.
That means ADB drivers aren't set up properly, OR the tf isn't sending an adb signal... :/ This is in recovery?
This is a tough one... almost no way to get a .zip on there without NvFlash...
Nebucatnetzer said:
It doesn't show anything. Just empty space.
Click to expand...
Click to collapse
Did you try adb in ubuntu?
sent while running with scissors
gee one said:
Did you try adb in ubuntu?
sent while running with scissors
Click to expand...
Click to collapse
He mentions above that it works with his other android devices I believe, so I don't think it's a windows issue. Never can hurt to fire up linux though
I noticed that ASUS would change the USB device IDs every so often, so the windows drivers could be out of date by the type a new firmware is pushed out.
gee one said:
I noticed that ASUS would change the USB device IDs every so often, so the windows drivers could be out of date by the type a new firmware is pushed out.
Click to expand...
Click to collapse
Why in the world would they do that..? Nevermind, it's ASUS!
OP definitely try a linux box though, not needing drivers is one less kink to work out.
DSL or Puppy linux in a VM box worst fine
I tried to do on Linux yesterday but I had some trouble getting it running. No idea why though it worked before. I'll try again today in the evening.
Sent from my Galaxy Nexus using xda premium
Thing O Doom said:
That means ADB drivers aren't set up properly, OR the tf isn't sending an adb signal... :/ This is in recovery?
This is a tough one... almost no way to get a .zip on there without NvFlash...
Click to expand...
Click to collapse
Yes in the recovery.
Sent from my Galaxy Nexus using xda premium
Nebucatnetzer said:
I tried to do on Linux yesterday but I had some trouble getting it running. No idea why though it worked before. I'll try again today in the evening.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Great I had to fix adb first. The excluded some things with Ubuntu 12.04....
http://www.hackersgarage.com/adb-no-such-file-or-directory.html
And ladies and gentlemen we got contact!
Hey guys, I'm new to the Sammy's (this is my first of many!) as I came from the Atrix2 forum (where I am still active).
But I can tell you after being on a locked down Moto phone, it's nice to be running official CM again. :victory:
Anyways I almost always modify some of my own APK's and the one I am after here is the Mms.apk. Normally I would just pull it via ADB and mod it afterwards. However, whenever I pull the APK, ADB says that it completed it, but the file never shows. ADB shows the phone as being attached, so this has left me scratching my head.... I never had these issues back with the A2, so I am thinking this is just some Sammy quirk that I am unaware of. I'm thinking maybe it's a driver issue? But I was able to update to the official ICS version with kies, so I'm assuming my drivers are ok? Here's what ADB is telling me:
Code:
C:\ADB>adb devices
List of devices attached
2c4d3bdb device
C:\ADB>adb pull system/app/Mms.apk C:\ADB
2994 KB/s (2152449 bytes in 0.702s)
Also tried running it interactively with root permissions and still no dice.
Thanks in advance guys.
Bump. Anyone?
Sent from my SAMSUNG-SGH-I727 using xda premium
If it's showing the phone under devices it's not a driver issue.
Have you tried running the command without the C:\ADB at the end? I've never used that and have not had any problems pulling or pushing.
Worse case just unzip the ROM and copy it over to your desktop.
hechoen said:
If it's showing the phone under devices it's not a driver issue.
Have you tried running the command without the C:\ADB at the end? I've never used that and have not had any problems pulling or pushing.
Worse case just unzip the ROM and copy it over to your desktop.
Click to expand...
Click to collapse
Well daggum sir. That was it. :good:
Although it is kinda strange as I have always been able to specify the path I wanted to pull it to before. Odd....
Thank you kind sir. :highfive:
Fall of Enosis said:
Well daggum sir. That was it. :good:
Although it is kinda strange as I have always been able to specify the path I wanted to pull it to before. Odd....
Thank you kind sir. :highfive:
Click to expand...
Click to collapse
You were trying to pull it to the same path. If you wanna pull somewhere else it needs a > i think.
Code:
C:\Users\Me>adb pull system/app/whatever.apk > C:\Users\Me\Downloads
That would drop it in my DL folder.
I always just cd to the directory I want to push or pull from before pushing or pulling. But I'm cheezy like that
Sent from my SGH-I727 using Tapatalk 2
cdshepherd said:
I always just cd to the directory I want to push or pull from before pushing or pulling. But I'm cheezy like that
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Me too
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hi everyone,
Long story short, my device wont boot. Ive got TWRP. I have the backup on my computer, but when i plug my phone in, i cant move the backup to my TWRP Backup directory because there is no way of getting to the internal storage. Im a noob with adb and i have no clue how to use it so can someone help with that. Thanks! :crying:
adb shell
mount /data
exit
adb push c:\users\provickers\desktop\backupfile /data/media/0/whereverTWRPbackupsGO
Sent from my Nexus 5 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
sent from my HAMMERHEAD
CRIME INC. said:
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
sent from my HAMMERHEAD
Click to expand...
Click to collapse
Not really an option...
rootSU said:
adb shell
mount /data
exit
adb push c:\users\provickers\desktop\backupfile /data/media/0/whereverTWRPbackupsGO
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that means nothing to me. can you write that in super duper nooby language please
Just read the adb stickie in q&a then
Sent from my Nexus 5 using Tapatalk
rootSU said:
Just read the adb stickie in q&a then
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I do adb shell
then mount /data
and it says: mounting /dev/block/mmcblk0p28 on /data failed: device or resource busy
Im currently in the home screen of TWRP
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
rootSU said:
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
alright thanks alot, hopefully it works!
rootSU said:
Maybe its already mounted by twrp in the mounts menu. If it is, skip that step. If not, mount in that menu
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can u tell me where the twrp backups directory is? Coz obviously i cant get into my phone
I don't use twrp myself so im not sure where it is. If you use the ls command..... (thats LS in lowercase)
Eg....
ls /data/media/0
That will list all the directories on sdcard. I assume there will be a folder called twrp there. Within there not sure. But you can use ls to keep drilling down.
ls /data/media/0/twrp
I think there's a backup folder with dated folsers within it.
Take a twrp backup now and see....
Sent from my Nexus 5 using Tapatalk
Yes, the path's correct... TWRP makes a backup in /data/media/0/TWRP/3282387328 (random string)...
So, you will need to push the backup folder to /data/media/0/TWRP/... Now it will show up in the restore option.
vin4yak said:
Yes, the path's correct... TWRP makes a backup in /data/media/0/TWRP/3282387328 (random string)...
So, you will need to push the backup folder to /data/media/0/TWRP/... Now it will show up in the restore option.
Click to expand...
Click to collapse
Presuming he has the content of the random string folder, but not the folder itself, can he create a random string folder manually? Or must he take a backup and use that folder?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Presuming he has the content of the random string folder, but not the folder itself, can he create a random string folder manually? Or must he take a backup and use that folder?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Like you, I've stuck with Philz for a long long time now.. Can't say for sure about twrp. I guess there's no harm in trying to make a folder and check.
However, sometimes while doing that, I faced a md5 mismatch error in twrp. But that's on a HTC One X.. No idea whether twrp has changed this since then.
rootSU said:
I don't use twrp myself so im not sure where it is. If you use the ls command..... (thats LS in lowercase)
Eg....
ls /data/media/0
That will list all the directories on sdcard. I assume there will be a folder called twrp there. Within there not sure. But you can use ls to keep drilling down.
ls /data/media/0/twrp
I think there's a backup folder with dated folsers within it.
Take a twrp backup now and see....
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I get "Permissions Denied". This is probably why nothing is working! What can i do?
ProVickers said:
Can u tell me where the twrp backups directory is? Coz obviously i cant get into my phone
Click to expand...
Click to collapse
/sdcard/TWRP/BACKUPS/your device serial number
Find the serial number in settings, about phone, status
Sent from my Nexus 5
Can't get to settings without booting phone.
OP can we keep this to one thread please? Its going to get confusing
Sent from my Nexus 5 using Tapatalk
i dont know why people dont do this, maybe they are worried of the little bit of space it takes in their storage, but i ALWAYS, since feb of 2009, keep a copy of my current rom and kernel in my storage. if i ever mess up doing anything, i always have my rom/kernel to flash again. no relying on computers(as im rarely around them). also, i always have one nandroid backup in my storage, just in case. it might not always be the most recent, but its there just in case.
@ProVickers
I'm not 100% sure of this but adb in TWRP doesn't work everywhere... You need to go to Advanced-Sideload.. then swipe right and then fire the adb push command..
rootSU said:
Can't get to settings without booting phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
He can get the serial number from the bootloader, right?
simms22 said:
i dont know why people dont do this, maybe they are worried of the little bit of space it takes in their storage, but i ALWAYS, since feb of 2009, keep a copy of my current rom and kernel in my storage. if i ever mess up doing anything, i always have my rom/kernel to flash again. no relying on computers(as im rarely around them). also, i always have one nandroid backup in my storage, just in case. it might not always be the most recent, but its there just in case.
Click to expand...
Click to collapse
Agreed.
Although i always have my rom, kernel and titanium backup. My nandoids move to my NAS as i don't have the space. However, I never modify anything that may require a restore when I'm away from home
Sent from my Nexus 5 using Tapatalk