im running clockworkmod v6.0.0.6 and unfortunately i was stupid enough not to backup the music/picture folders on this and installed kitkat update OTA. Now its stuck on the boot animation...
HOW DO I BACKUP THE FILES USING ADB FASTBOOT? I cant seem to be able to plug the device in and be able to look at any of the files! I have windows mac linux. PLEASE HELP i need to at least be able to backup..
EDIT: i got the ./adb working! so now i can pull the files off the device..
Now how do i fix the boot animation issue? it would be nice to get the kitkat working...
Related
I tried looking around the forums to see if someone has had this problem before. Couldn't find something similar.
I had stock 4.0.3 installed and I saw today that 4.0.4 was being pushed out. Since 4.0.3 wasn't a stock build I tried to downgrade to 2.3.6 in order to keep everything stock. I rooted the phone, installed the ROM Manager and flashed 2.3.6 through Clockworkmod Recovery. Everything went smoothly but when I powered on the phone force quit messages kept popping up and I can't get past the welcome screen. When I go into Fastboot mode and try to go in Recovery mode it just shows the Android symbol and a warning sign. I tried flashing a recovery .zip file I found online through fastboot but couldn't manage to do it (I'm on Mac OSX)
Can someone please help me? I'm completely desperate and wouldn't care about erasing everything (I think I already did, actually).
Thanks in advance.
flash a recovery.img
that multiple fc happened to me when i installed a i9023 rom on my i9020a.
unzip the recovery.zip and flash the .img file through fastboot and make sure you have the right rom for your model
Thank man, but that's what I tried to do. I got confused and wrote that it was a .zip up there. I'm really confused and couldn't flash the .img. Could you walk me through it? or point me to a thread that shows me how to do it?
im not sure how a mac is set up, i can walk you through flashing it on windows through command prompt ...
Please do that. I guess I can try to work it out.
Thanks
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
memorize that lol it saved me.
you can skip the root part, but it explains how to set up the pc so it'll read the nexus with the correct drivers and whatnot, and what commands to run to flash the recovery. then when youre in the recovery, mount as usb, copy over 2.3.6 (the right one!) and install from zip.
I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!
Can you get into boot loader mode?
Have you tried to use Odin?
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Sent from my Nexus S 4G using XDA Premium App
colettamiguel said:
I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!
Click to expand...
Click to collapse
Did you unlock your bootloader?
Code:
fastboot oem unlock
Hi,
I wanted to install MultiRom on my nexus 7, so I tried
I first flashed the required zip folder, was working fine.
Then I went to flash the recovery.img
It was stuck on waiting for device, but I saw that I needed to upgrade my bootloader.
When I tried fastboot flash bootloader bootloader.img, It was stuck on waiting for device.
So, I tried the flash-able zip.
I didn't put it on internal storage, so I adb pushed it.
But, it said "error: device not found"
I tried adb devices, but same thing.
I made a backup before all this, so I'm also wondering:
Will restoring not restore my apps/setting, etc?
Also, I'm using fastboot 3.41, TWRP 2.6.0.0
*EDIT*
Okay, rebooting my computer helped...
I am an idiot sometimes :c
Also, I have the latest CM10 nightly.
Is that the problem? (Prob isn't because it will detect it while normal)
Ok think my A500 is toast? Maybe someone can help me? Please!! boots to skrilak v8 and stays there.
Had omnirom kitkat running and all of a sudden stopped working. It will not boot or recover at all. I have skrilax v8 and twrp 2.1.3 Fails to mount /data /system /sdcard etc When booting to secondary image it fails (secondary image apk kernel error.I know i had root and su installed, stupid me didnt create a backup.
I can read the files in adb no problem, Has adb and fastboot mode on pc. Gets stuck on stage 2 and bct dump fails in a500apx program. ETC i have tried all for the last week and still no avail. I tried timmydeans too
I have my cpuid and skd #'s my problem is adb reports device as $roserial.no not the actual cpuid device? maybe i am doing something wrong?
Is there a way to partition this? is there a way to check partitions? i am pretty computer savy just cant figure out for the life of me why it wont start up.
I think you'd better try to check this: http://forum.xda-developers.com/showthread.php?t=1585907 and/or this: http://forum.xda-developers.com/showthread.php?t=2755126 to unbrick your tablet and begin your unlocking process again.
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
sirmot said:
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
Click to expand...
Click to collapse
UPDATE: I got the gapps to install successfully. I installed Wifi File Explorer through NRToolkit in order to transfer files to my phone. And transferred the same exact file to my phone. I tried flashing the file and it worked... I'm guessing the wired transfer corrupted the file somehow. Thank you NRT for that option to install apks.
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
XxLordxX said:
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
Click to expand...
Click to collapse
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
sirmot said:
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
Click to expand...
Click to collapse
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
XxLordxX said:
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Click to expand...
Click to collapse
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
sirmot said:
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
Click to expand...
Click to collapse
Hi,
If you're stuck in fastboot you can flash a recovery or use the "fastboot boot" to boot in recovery and then use adb push from there .
~Lord
Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks
luizffgarcia said:
Guys, i just bought an used Nexus 4 and after flashing the cwm recovery and trying to boot in the recovery mode i get a few errors stating:
cant mount cache/recovery
cant open cache/recovery
I notice there are a few topics about this and the solution is to adb push or something, but the adb push command wont work in recovery for me, says device not found and i know my drivers are correct since i can fastboot and do stuff.
I actually got the device running perfectly flashing Chroma via sideload, but cwm wont work! I cant access anything from inside cwm... I also tried twrp and no luck.
I also tried a full original image flash, no luck
Can you please help me with this?
Thanks
Click to expand...
Click to collapse
when you flashed the factory image it should have brought you back erasing and replacing everything. In fastboot did you flash the bootloader, radio, system partitions (.IMG), recovery partition, and so on.? If not try this steps guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312/page194 its pretty detailed but it helped me after I wiped everything off my phone trying to learn. If that's a bit too much then try searching for wugfresh nexus toolkit. Both will wipe everything from your nexus then replace it and should get everything going