For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
Related
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
Notice this could hose,break,trash or brick your phone. You are warned.
Update
Thanks to both CVPCS and Dragonzkiller and the DX2-Dev-Team. And of course thanks to koush. And Tenfar too did he did find the /preinstall hack? Did Dragonzkiller fixed the graphics or what? IDNK, it is fixed(/sbin/recovery in DK, cvpcs is broken). Hence the hybrid zip.
The UL zip works some what from /preinstall see my thread. http://forum.xda-developers.com/showpost.php?p=20634404&postcount=1 It may do the same if flashed via Tenfars,our bootstrap, just flash it as you would any zip and it will take over.
It backs up and will restore, from adv restore, /cache and(if set in recovery.fstab) sd-ext. A full restore bombs:
Checking MD5 sums...
cache.ext3.tar: OK
data.ext3.tar: OK
system.ext3.tar: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-01-02.05.08.01//system.ext3.tar
Restoring system...
E:format_volume failed to unmount "/system"
Error while formatting /system!
Other features may work. I find that zipping from win7 winrar fails but Root Explorer zipping results work.
/sbin/recovery is distorted (main screen):
https://github.com/cvpcs/DroidX2Bootstrap/tree/master/assets
Distortion fixed;
https://github.com/DX2-Dev-Team/DX2-CWMR/tree/master/assets
Edit What is the "/preinstall cwr hack"?
TO PUT IN PLAIN TERMS : ALL YOU NEED FOR ANY CHARGE ENABLED RECOVERY:
THE FILES: "hijack" AND (THE HACKED) "charge_only_mode" IN /system/bin
AND ".revovery_mode" IS IN /data
YOU DO NOT NEED ANYTHING ELSE BUT TO LOAD /preinstall
WITH YOUR FAV RECOVERY NAMED: "update-recovery.zip", ALONG WITH IT'S BINARY (SAME AS INSIDE THE ZIP/meta-inf....) CALLED: "update-binary" AND "hijack" (SAME AS ABOVE). Thats it! 6 files. With permissions- See above link.
Older post
5.0.2.0 http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip
Not everything works: when flashing between recoveries they need to be on internal sd, and, of course, backup and restore may work but its for ul bootloaders only.
DO NOT FLASH FROM ROM MANAGER. IT WILL BE SBF time.
Flash from tenfars and keep a copy of both on int sd (tenfars update-recovery.zip and the DL) to go back and forth. Do not backup and restore with this.
Just checked out the updater script and it looks like it should work, barring no needed changes on the scripts in sbin that it copies. I wonder if ADB works in it on this one. This could be a huge bonus for what were trying to do since BSR is kinda old and crappy
No adb in adv menu.
skwoodwiva said:
No adb in adv menu.
Click to expand...
Click to collapse
ADB shouldnt be in a menu. Should just be enabled by default. Course it only would work if it was plugged into a computer at the time you dropped into CWR. It doesnt support USB state changing.
So if the cwr in charge mode triggered, as is the preinstall hack, then no adb?
Log from cwr
init.svc.battd running
.usbd running
.touch stopped
.atvc stopped
.adb running
Extended commands not found.
See if you can run any adb commands like:
adb devices
adb pull /system/build.prop
etc...
It fails to mount sdcard. When recovering or manual mount.
I'm done messing this one.
I was able to overwrite the one in /data/data/tenfar folder but not in /preinstall folder anything special I need to try? Still went into BSR when I rebooted to recovery.
Sent from my DROID X2 using XDA App
I am learing as I go, but the point I realized is when you go to adv menu,in cwr,and reboot recov the current cwr gets loaded to /preinstall. So paste to data/data...files run sr then do reboot recov. Then paste to preinstall.
Cool ill give that a shot thanks!!!
Sent from my DROID X2 using XDA App
If I had the knowhow I would hack the garphics from 5010atrix to 5025x2!! .
But why would the newest Dx2 be any good and NOT a failure and be so messed for all this time? Unless one failure hides the other.
It probably can't mount SD due to a wrong mountpoint in one of the scripts. Should be easy to fix.
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip
newer atrix 5020 all works but restore fails as boot img, of course, won't load.
skwoodwiva said:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip
newer atrix 5020 all works but restore fails as boot img, of course, won't load.
Click to expand...
Click to collapse
how hards that going to be to fix?
Ha ha ha ha!
You got me!
But it easy to flash between these cwrs even back to tenfars. Want to find a way to recwr after a wipe or flash.
The skewed graphics problem is from within the recovery (binary) in /sbin of the
zip: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.5-daytona.zip .
I pasted the file from the above into this http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip and got same graphics skewing.
balltongue said:
See if you can run any adb commands like:
adb devices
adb pull /system/build.prop
etc...
Click to expand...
Click to collapse
Is this from android/sdk in win7?
Can you give me a prep? I am just a NooB.
Within your sdk folder look for platform tools, adb is within this folder. Navigate to platform tools directory using cmd then enter the commands.
Sent from my DROID X2 using xda premium
skwoodwiva said:
Is this from android/sdk in win7?
Can you give me a prep? I am just a NooB.
Click to expand...
Click to collapse
I pm'd you with some info about setting up sdk.
My prime is stuck in the splash screen and I can't get it to go further than that. I've been reading and been told I can push the ROMs zip file with the adb push command. The zip I downloaded on my computer is in my downloads folder. What would I exactly need to put in the command window to push the zip to the internal memory of my prime?
Sent from my Galaxy Nexus using xda premium
Nilsonf said:
My prime is stuck in the splash screen and I can't get it to go further than that. I've been reading and been told I can push the ROMs zip file with the adb push command. The zip I downloaded on my computer is in my downloads folder. What would I exactly need to put in the command window to push the zip to the internal memory of my prime?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Number 1, stick your ROM into the same folder that adb is in.
Number 2, read up about command line and terminal. (Trust me, you should do this)
Number 3, with your new found knowledge, push that file onto your internal storage. Example "adb push /ROM.zip /sdcard" !!!!!!
It's as simple as that sometimes.
The thing I don't get is what am I supposed to put on the adb push /ROM.zip /sdcard part
Sent from my Galaxy Nexus using xda premium
adb
Run adb devices, this will let you know if your drivers are working correctly, you should get
Recovery and your devices serial number, then if your zip is named virtuous.zip the command line is,
adb push virtuous.zip /sdcard/
You put the name of the zip file in there to push, /sdcard/ puts it on your root directory.
dklue said:
Run adb devices, this will let you know if your drivers are working correctly, you should get
Recovery and your devices serial number, then if your from zip is named virtuous.zip the command line is,
ad push virtuous.zip /sdcard/
You put the name of the zip file in there to push, /sdcard/ puts it on your root directory.
Click to expand...
Click to collapse
I've been doing that but it doesn't work
Sent from my Galaxy Nexus using xda premium
adb
Can you put it into cwm recovery ? When off hold volume down and the power button,
When little white letters come up, hit volume up, it should be in cwm when your adb pushing files, you can also try continuing to hold down on volume and then you get the three choices,
Android, USB, wipe data, it may push in the USB choice, read in the development section how
to unbrick your transformer prime, hopefully its a soft brick.
dklue said:
Can you put it into cwm recovery ? When off hold volume down and the power button,
When little white letters come up, hit volume up, it should be in cwm when your adb pushing files, you can also try continuing to hold down on volume and then you get the three choices,
Android, USB, wipe data, it may push in the USB choice, read in the development section how
to unbrick your transformer prime, hopefully its a soft brick.
Click to expand...
Click to collapse
Yeah when I try to push the file its in CWM and I type adb devices it recognizes it in recovery and the serial. I put adb push Primalicious_9.4.2.21._Final.zip /sdcard/ enter and it says no such file. Is it supposed to be in a specific folder or am I doing something wrong? I already unbricked it I just need to load the ROM
Sent from my Galaxy Nexus using xda premium
adb
The rom zip file should be in the directory where your adb.exe is. So if its in say
Program files/android/tools that's where you need to put the zip, otherwise it won't know
Where it is.
dklue said:
The rom zip file should be in the directory where your adb.exe is. So if its in say
Program files/android/tools that's where you need to put the zip, otherwise it won't know
Where it is.
Click to expand...
Click to collapse
Is this right?
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
adb
Yes that's right, you may want to rename it prime.zip, cause it may be .zip.zip or something,
or it may be a zip inside a zip.
dklue said:
Yes that's right, you may want to rename it prime.zip, cause it may be .zip.zip or something,
or it may be a zip inside a zip.
Click to expand...
Click to collapse
So rename the ROM prime.zip? And try that?
Sent from my Galaxy Nexus using xda premium
adb
You need to put the full file name,
adb push primalicious.zip /sdcard/
That's just the example, put the correct name in and include .zip.
I changed the name to prime.zip so I tried adb push prime.zip /sdcard/ and adb push prime.zip.zip /sdcard/ and it says no files found
Sent from my Galaxy Nexus using xda premium
adb
Do you have a backup to restore in cwm ? Or try to unmount /staging and mount /Data
In cwm and try
adb push prime.zip /data/local/
Otherwise I'm not sure why its not recognizing that file, I bricked my prime and someone in irc channel sent me a blob file, and he told me to push it to /data/local/
And it worked, I had to use win xp cause I couldn't get it to work on win 7, but your getting the correct response from adb devices, so I'm not sure,
---------- Post added at 09:22 PM ---------- Previous post was at 09:11 PM ----------
http://android.dkszone.net/copy-transfer-files-android-sd-card-adb-windows
dklue said:
Do you have a backup to restore in cwm ? Or try to unmount /staging and mount /Data
In cwm and try
adb push prime.zip /data/local/
Otherwise I'm not sure why its not recognizing that file, I bricked my prime and someone in irc channel sent me a blob file, and he told me to push it to /data/local/
And it worked, I had to use win xp cause I couldn't get it to work on win 7, but your getting the correct response from adb devices, so I'm not sure,
Click to expand...
Click to collapse
Ok thank you for your help. I will try to do that tomorrow cause I'm tired of messing with it for tonight lol. Hopefully I can get it to work
Sent from my Galaxy Nexus using xda premium
FIX!! - How to adb a zip ROM through CWM!!!
Hello there, for the last few nights I was having the same issue as you. I bricked my tablet, fixed it, and then just got stocked on the recovery with no data on my SDCARD. After searching and searching for hours online I found your post last night. And after reading the comments from "dklue", i googled some more information about something very important that me and you were missing!: "Blob files".
The "Primalicious_9.4.2.21._Final.zip" file or the "AOKP.zip" file will not work just like that because they are not in the format to be "Pushed" using the push command (At least thats what i kinda realized lol) anyhow, so i went online and searched for a ROM on Blob format and luckily i found the following!:
[ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
djedoortega said:
Hello there, for the last few nights I was having the same issue as you. I bricked my tablet, fixed it, and then just got stocked on the recovery with no data on my SDCARD. After searching and searching for hours online I found your post last night. And after reading the comments from Nilsonf, i googled some more information about something very important that me and you were missing!: "Blob files".
The "Primalicious_9.4.2.21._Final.zip" file or the "AOKP.zip" file will not work just like that because they are not in the format to be "Pushed" using the push command (At least thats what i kinda realized lol) anyhow, so i went online and searched for a ROM on Blob format and luckily i found the following!:
[ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "Nilsonf" gave me the BLOB concept idea! heheheh i guess i learned something new now..
Click to expand...
Click to collapse
Thanks man. I'll have to try that sometime later on today. I will report back with the end results
Sent from my Galaxy Nexus using xda premium
I'm stuck on number 3 of part 2. It's been doing nothing for about 20 minutes now. Should I keep waiting?
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Reserved
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
cland216 said:
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
Click to expand...
Click to collapse
Hell yeah. Glad I could help somebody! I've been wanting to give back to the wonderful XDA community for a while as a long time lurker. Also, I'm hoping to get a newer version of the stock rom and a stock recovery.img so you can go back to 100% factory stock for an OTA. I'm pretty proud of myself (being noobish) figuring this out.
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
klaudio_tv said:
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
Click to expand...
Click to collapse
Are you referring to "extracting" the recovery img? You only need to do it if you're running the stock recovery.
If so, I think I have screwed the command. Make sure you're in adb shell (in recovery on the watch) and then type "cat /proc/mtd" (with the space in front of cat) without the quotes in order to locate the recovery partition.
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
Hopefully this works
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
klaudio_tv said:
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
Click to expand...
Click to collapse
Since the OP helped me, here's my chance to give back..
By no means do I know what hell I'm doing, but I know enough to be dangerous. If you're ready to live dangerously, follow these steps (which worked for me):
1. Go into TWRP on the watch and connect it usb to your computer. Using TWRP file manager, copy the update.zip from CACHE to sdcard\Download.
2. On the computer, browse to Zenwatch internal memory Downloads folder and copy the update.zip file to your computer.
3. Unzip the file on your computer using 7zip.
4. Navigate to \META-INF\com\google\android\ and look for updater-script.
5. Edit updater-script in Notepad++.
6. Delete the lines starting with getprop. This turned out to be lines 2 thru 5.
7. Delete the lines starting with apply_patch_check. This turned out to be lines 10 thru 176
8. Save changes to updater-script then in Windows Explorer highlight all of the files and folders that you unzipped, right-click them and click on 7zip --> Add to update.zip
9. Copy the new update.zip to the Zenwatch internal memory, Downloads folder, overwriting the original update.zip
10. Flash the update.zip file with TWRP.
11. Reboot TWRP to Bootloader.
12. On your computer, goto adb folder where you have fastboot files, and using command prompt type:
fastboot erase cache
fastboot erase misc
fastboot reboot
These steps worked as I was stuck on the June 1, 2016 Android security patch on my Wren Zenwatch. These steps helped me get to the September 1, 2016 security patch.
I managed to update my watch to the September 1 security patch using Cland216's method. But I am unable to update further using the method above. Does anyone have any info on how to update further? Or has any zip files to flash?
If we could get someone to upload the watches stock recovery that would solve all issues.....Why has noone done this for this model yet?
Sent from my OnePlus X using XDA Labs
I'm unable to create a backup file
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
TWRP :
Could not mount /data
When I try to mount /data , I unable to /data
HOLY ****
Dude.. Let me just say...
YOU ARE THE ****ING ABSOLUTE BEST.
I am now going to make a backup, and save it to my computer, google drive, dropbox, icloud, and every other ****in place I can to make sure this never happens again. Thank you!!!!
Nicholas6706 said:
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Click to expand...
Click to collapse
I spoke just a bit too soon, now it is hanging on that animation with the 4 dots. Any suggestions?
NEVERMIND, I AM UP AND RUNNING!! WOOHOOOO
Attached i will have a link to my google drive with programs and zip files for everyone to use will explain further.
Okay I have a few problems going... here is what I have and have tried and the issues I have been having... I have log files and such saved too should you need those.
Synthoms: LGK20 PLUS aka TP260
- I needed a Binary update for SU... (never did get that to work) Somehow afterwards my phone would only reboot into Twrp Recovery on boot loop.
-I installed an Update SU file ( also didn't work) then the phone started booting into only fastboot.... ( I had a brief issue of it not connecting on ADB but I hade to just end task adb in the task menu (Crtl Alt Del in case somebody has same problem) Afterwards connected no problem.
-I have wiped datas and cache and all sorts of instuctions to no avail.. lol
_phone now boot immediately to fastboot but I am able to get to twrp recovery just fine
Whats Weird:
-I can see the device on the computer get onto the sd card add files and zip files and the computer recognizes it n o problem at all... but LG MOBILE SUPPORT LGUP LG Bridge and LG Flash Tool.... all do not recognize my phone.
-But no matter where I partition anything and no matter what recovery img or zip file I install... it just only wants to open into fastboot.... I'm sure it is a very simple operation to fix... maybe one of you have a restore file can put on the SD with mine that have done me no good? Any help would be appreciated hardcore lol and I appreciate the learning experience a per i have learned a lot..
Heres what I have collected in my attempts
A: I have a Twrp.img and Recovery.img (not sure if they are a recovery or boot partition)
B: I have ADB it connects to my device fine and I can even flash onto the phone but seems to not be helping lol
C: : LG Bridge and LG UP do not see that my phone is connected (all my drivers are updated)
D: I have a stock KTZ file for my phone but I have no programs to flash it except adb (the others will not recognize my phone except ADB
E: I am very sure Xposed may have something to do with this... I downloaded an uninstaller and the zip file will not flash error 555 or something like that.
F: I'm very sure I need a Boot.img?? this I know little about but I have a program to build one if I can figure out how lol.
G: My recoveries did not work :0(
H: None of my SU zips seem to be working (is why I believe Xposed is behind it lol.
I: There are commands you can put into the terminal in TWRP recovery ( I can get there will explain further later) to disable Xposed but they say to create a folder name \data\data\....ect ect... There is no way that the TWRP recovery will let me create folders so I'm at a loss there.....
Chances are there was software on the phone that allows the LG software on the computer to see it.
I'm not seeing the Google drive link, but if you wiped the system & data partitions in TWRP, then you have no OS.
Don't know if TWRP can flash a KTZ file, most 3rd party ROMs are ZIP.
Is it Tmobile or MetroPCS?
I assume you have read Aletron9000's thread https://forum.xda-developers.com/android/help/lg-k20-plus-how-to-flash-original-rom-t3632850/page1
It seems like it has a download mode similar to Samsung phones when using Odin. I have a OnePlus and its straight forward, TWRP (in twrp plugging into pc will bring up the device in file mode so you can copy rom and gapps zip files) and once I got twrp on my mom's galaxy s4 it was same process with LineageOS 14.1 and the phone runs 10x better.
I wish I knew if you could flash the KTZ file in twrp, but I doubt it.. If you can uncompress it in 7zip or winrar, then zip it again that may work. But if your just trying to install a factory image (assuming that's what a KTZ is) the the directions in the link above should get you there. Then for root either flash supersu (apparently Chinese controlled if that matters) or maybe better magisk 16 from twrp (and the newest magisk manager apk from within the Android, should still pass safety check, and can install alot of modules that I previously used xposed for.
Only trust the magisk on xda-developers
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my A0001 using Tapatalk
TP260 SOFT BRICK: Recovery File?
I am on a TMOBILE phone... I"M sure that's exactly what my problem is... I did read that post and have LGUP (will also be in my drive link) BUT it does me no good because it will not show up on the program for me to flash anything to it...
If I could get somebody to send me a recovery file I would be able to put it into my SD card then load it up will solve my entire issue lol.
I did consider trying magicks honestly but I do not know enough about it to switch over like that... Once I get my phone back I will research into it and let you guys now how my adventure turns out. lol.... I'm a research first kind of person hahaha....
FILES
Soon I will type up instuctions for each KIT I put together. That way all the instructions will be able to be found in one place which will help out a lot of people looking for LG UP or Recovery.img or Twrp.img plus a lot of other stuff including SU zip file ect,,,
https://drive.google.com/open?id=10OXHQtyZBCap7PaqiGZEEErmo_th8xFp
The KTZ file would not upload but if You want I will send it no problem at all Just ask. I will be adding a couple other things on there too probably.
I believe my best bet would be to take that KTZ file (bugger wouldn't load onto my DRIVE account lol) but I thin I will take that and convert it to a zip file and maybe give that a shot... But when I flash something like that does it go under the BOOT or RECOVERY partition? I undertand what a partigtion is but I'm not sure of the difference between the BOOT and RECOVERY idea .... is recovery out ROM and BOOT our OS system?