i used this method to boot:http://forum.xda-developers.com/showthread.php?t=920347
first it worked but i powered my nc off and since it didn't boot even if a kept the n button pressed,when i plug it on my computer adb dont detect it and the light is orange in charge and on computer
plz help me
thx
cwr
i boot from cwr and used this method:http://forum.xda-developers.com/showthread.php?t=931720
but still doesn't boot
need help
please someone help me i don't know what to do
Does your NC totally not boot at all? If you followed instruction in this thread - http://forum.xda-developers.com/showthread.php?t=931720 basically you are booting from SD. In this case, it has nothing to do what's on your internal flash. Check whether your SD card is created correctly.
it boots
it only boots from CWR
i had the same problem you have. i booted into CWM using the 1 gig sdimage, put the stock boot.img and system.img (from here - http://forum.xda-developers.com/showthread.php?t=919353) and did the dd commands from adb as shown there and my system booted normally.
i had a problem with the stock B&N usb cable where it didn't detect through adb at all. i had to use a different usb cable and it worked good.
i'll try
thx i'll try it tonight,it 1 pm in france^^,tell you if it worked
i don't have any other cable,i ll try to see at virgin tomorrow ,if you have an easier way let me know
the only other way i can think of doing that is to use nookie froyo and wireless adb. the problem with this method was when i tried doing that, i had no market, so i couldn't get wireless adb. i didn't feel like doing a workaround to getting that apk on there. problem with this method is i didn't know if the partitions would look the same or even show off the nook as i was working off the sdcard for froyo, so i wouldn't be able to say if this would actually work.
using the stock B&N cable, i noticed that the device would show in adb, but not online. so reading around i found out if u used a different usb cable it might work, so i did and it did work lol.
Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App
samuelhalff said:
Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
i looked at sam's method before as well, but didn't try it since i had luck with my usb cable connection for ADB usage. just dd-ing system and boot seemed to work for me and allowed me to keep it how i had it before (with all my previous apps installed). my partitions are probably still shorter though. flashing the zip looks like it'll restore everything to stock.
i bought a new cable,still don't work with adb ,windows detect it but it says it's two different devices and i cant change the driver,sooner nc booted under nookie froyo i don't know how,i'll try to boot again with 2.2 and work with adb from here
were u able to adb in the first place? i used this link http://forum.xda-developers.com/showthread.php?t=882751 to get it working. i also went through the nookdev site to get adb working. i was assuming it was my cable at least since it was tweaking (connecting/disconnecting) with the stock B&N usb cable.
still no adb even over nookie froyo,i try with your method
i have adb usb ,now i don't know how to do cause i only have a 2gb card so i only can put boot but not system on it,i don't know how to enter the command ,is it in adb shell?
i went through CWM and mounted system, data and sdcard. u use adb shell to get into the shell in the nook. then adb'd and
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
did that. i guess u can put one file and then another file after the first file is dd'd. i used adb to push those img files to the sdcard.
i try it,could you make me a kind of how to with steps and stuff plz?
petithor said:
i try it,could you make me a kind of how to with steps and stuff plz?
Click to expand...
Click to collapse
in your situation this is what i would do.
boot into cwm
mount system, boot and sdcard through the menus
without entering the shell (adb shell) type in: adb push <boot.img file location> /sdcard
now enter the nook's shell by type adb shell then enter
so you're in the nook's shell, and type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1"
delete the boot.img file so you have enough space on for the system image by typing "rm boot.img" (make sure you're in the root of sdcard)
type exit to exit the nook's shell
now you're going to push the system.img to the sdcard: adb push <system.img file location> /sdcard
enter into the nook's shell again (adb shell)
type in "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
once that is done reboot and everything should work just like before you ran that other script.
this is pretty much what i did. i'm on windows 7 x64 so i just dragged and dropped the files into the command prompt to get the file locations.
again: http://forum.xda-developers.com/showthread.php?t=919353 for more reference of what i was doing.
it worked thx very much ,you are a god besides the humans
Related
push a ROM onto my sdcard through adb?
my win xp is so old it wont read the root of my sdcard unless its only fat32...
so i was wondering if i could do it that way...
ive looked through threads but hadnt found a definite answer seeing as im new to all this
any help would be appreciated!
I am not sure you are understanding the process or I am not understanding the question.
But lets just roll with it...
You can do:
adb push c:\romNam.zip /sdcard
Click to expand...
Click to collapse
This will put the romName.zip file on the root of your sdcard (fat32 partition). From there you can reboot into recovery mode (turn off phone, then hold down the HOME button and then hit the POWER button). If you have the CM 1.4 recovery image installed then you can install any zip file and you would just point to the romName.zip file. If you have the CM 1.3 recovery image you should rename the romName.zip file to update.zip and then apply that update from the menu in CM 1.3.
If you do not have the CM recovery image installed, well, then you need to back and read some more.
i think you are on the right track for what im asking...
im using cm 1.4 recovery
lets say i dl drizzys 1.5.5
do i rename it update?update.zip?or leave it as is the way i downloaded it?
i tried putting it on my c drive and naming it update and it didnt work
or course i was using someone elses thread to go by so maybe i did it wrong
Do you have adb set up so it can connect to your phone?
If you have CM recovery 1.4 you do not have to rename it to update.zip but go ahead and do that for this test.
When you say
i tried putting it on my c drive and naming it update and it didnt work
Click to expand...
Click to collapse
what do you mean?
The renaming didn't work, or the adb push didn't work
renaming it update and trying to push it through adb didnt work...
im downloading another ROM and im gonna try again and see if it might work this time...
Right. But what I am asking is, what "didnt work." Was the file not there on the sdcard after you pushed? Did the CM recovery image fail to apply the update?
the file wasnt on the sd and cm didnt see it to install...
i may have named it wrong...or missed the space between zip and /
i will try again and see if thats what was wrong...
Okay.
When you set up adb did you follow this thread?
If you are not able to mount your sdcard in windows that may or may not be a showstopper. How do you have your sdcard formatted? All fat32 or did you split it up into fat32, ext3, linux-swap?
If you are going to adb push files to your sdcard you should NOT mount the sdcard.
yes...i followed that thread
and i repartitioned my 4gb sdcard as such:
fat32 0 1405
ext3 1405 1905
linux-swap 1905 2001
and i did not mount my phone...i at least saw not to do that in very bold letters so i took it to heart...lol!
Okay, cool.
What does the CM 1.4 tell you when you try to apply the update.zip?
After you adb push the file, go into the device via adb shell.
CD to the /sdcard and do an "ls" and tell me what you see.
If you do not see anything but the adb push returned no errors, your sdcard may be fubar (don't freak yet, there are fixes for it and we will get there if we need to).
If you do see the zip file then reboot into recovery again. But this time do not try to apply an update, instead drop to a console and CD into the /sdcard again and do another "ls" and let me know what you see.
i just tried doing this:
cd c:\android-sdk-windows-1.6_r1\tools>adb shell
/ # adb push c:\KiNgxKxROM_Beta1_RedRosieThemev1_signed.zip /sdcard
/sbin/sh: adb: not found
then i tried:
/ # adb push c:\KiNgxKxROM_Beta1_RedRosieThemev1_signed /sdcard
/sbin/sh: adb: not found
then:
/ # adb push c:\update /sdcard
/sbin/sh: adb: not found
nothing
and where do i look in the forums...or how exactly do i cd to the sdcard?
aha!
I see the issue.
You do not need to adb shell then do adb push
it shoul be like:
C:c:\android-sdk-windows-1.6_r1\tools> adb push c:\KiNgxKxROM_Beta1_RedRosieThemev1_signed.zip /sdcard
Click to expand...
Click to collapse
adb push is done from your local dos window not from within the adb shell.
Try that out and let me know.
wow!
that did it! thank you sooooo much!
thats just one more step i can eliminate now!
no Problem. Welcome to the world of roms.
care to walk me through how to use switchrom? lol!
all these hero builds seem to crash on me after awhile and i kinda wanna have several to switch to if/when they fail...
I found this after searching around for ages on a way to upgrade the recovery on my Wildfire/Buzz, all the friggin fastboot methods weren't working. This worked straight away, no errors, no problems.
Flash a New Recovery Image
1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for)
2. Rename the filename of the recovery image EXACTLY as it is written to recovery.img
3. Put the recovery image file on the SD card (not in any folders)
4. Download Android Terminal Emulator from the Market (there are a few different terminals in the Market some have an onscreen keyboard and some don’t experiment till you get one, also hold down Menu in some of them to bring up the onscreen keyboard if you don’t see it)
5. Open the Terminal program and type the following (with hitting enter at the end of each line):
su (press enter)
(at this stage it will ask you for superuser permission to access your core system. Allow the access)
su (press enter)
flash_image recovery /sdcard/recovery.img
6. Phone should pause for a second and then show you a new blank line. Turn it off and back on by holding down Home and Power to ensure it flashed correctly. Done.
Error
flash_image: not found
Sdcard is fat (not fat32). Any idea.
Sent from my HTC Wildfire using XDA App
EDIT - Sorry, Wrong method, here's the correct one:
First, make sure you have the latest Android SDK, then:
Connect the device to your computer
Copy recovery.img to the root of your SD card
Open term on your computer and run: adb root adb remount
Flashing the custom recovery adb shell flash_image recovery /sdcard/recovery.img
Reboot into recovery to make sure the process was successful.
Sec:
http://wiki.cyanogenmod.com/wiki/RE-recovery-img
3xeno, your method is the same as yusuo's.
he directly use console on android to send command "flash_image recovery /sdcard/recovery.img" after become root ("su")
pro: no need for PC, con: hard typing on the device
you ask adb to execute on the device the command "flash_image recovery /sdcard/recovery.img".
pro: single command with a real keyboard; con: need for PC and cable
fastboot works only with s-off,if you don t have s-off it will not work .-. (or if you don t have the right files)
anyway this metod didn t work for me
fastboot is the best and more simple than this,anyway is there a metod to flash recovery from the phone?
ilgimmy said:
3xeno, your method is the same as yusuo's.
he directly use console on android to send command "flash_image recovery /sdcard/recovery.img" after become root ("su")
pro: no need for PC, con: hard typing on the device
you ask adb to execute on the device the command "flash_image recovery /sdcard/recovery.img".
pro: single command with a real keyboard; con: need for PC and cable
Click to expand...
Click to collapse
I know, but the method on the handset itself didn't work for him. Hence, just suggested the alternative of the same technique as in the OP
My phone has alpharevx s-off. I thought there was no need of pc and everything can be done from phone itself. But still it didn't work for me. Same error.
If there was a need of pc terminal, maybe the 1st post needs to be clear.
Sent from my HTC Wildfire using XDA App
After a bit more reading, it seems "flash_image" must be present in /system/bin for it to work.
More details here:
http://forum.xda-developers.com/showthread.php?t=1146566
Std Disclaimer - I have not tested any of these, so I don't know if they will work or not.
3xeno said:
After a bit more reading, it seems "flash_image" must be present in /system/bin for it to work.
More details here:
http://forum.xda-developers.com/showthread.php?t=1146566
Std Disclaimer - I have not tested any of these, so I don't know if they will work or not.
Click to expand...
Click to collapse
Yes. Now I can confirm that it works when there is "flash_image" (a file with no extension) is present in the path /system/bin/. Also the permissions of flash_image needs to be executable. Just flashed the recovery partition .
Download flash_image from the link given by 3xeno. The OP needs to be updated.
Sent from my HTC Wildfire using XDA App
i use this command since age... it's the only method that works on my buzz
can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
but my phone cant connect with PC, atlthough i installed google usb driver.
i might be wrong but cant you just flash a original ruu, than root and reinstall recovery
#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.
hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip
You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk
And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.
I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do
Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...
I've a rooted Nexus 6 running Lollipop 5.1. I edited /system/build.prop in an attempt to get Miracast working. I added the following line:
persist.debug.wfd.enable=1
However, now my phone won't boot. It's stuck at the "Google" screen. I think the permissions on build.prop are wrong but when I try to connect with adb via USB, my computers don't recognize the device. I press volume down + power and then plug the phone in. Nothing comes up when I issue ./adb devices. I've tried on both a Windows 7 desktop and a Macbook.
Am I missing something with adb and my connection procedure? Am I just hosed? Is there any way to get this device running again, even if it means a factory reset?
EvaUnit02 said:
I've a rooted Nexus 6 running Lollipop 5.1. I edited /system/build.prop in an attempt to get Miracast working. I added the following line:
persist.debug.wfd.enable=1
However, now my phone won't boot. It's stuck at the "Google" screen. I think the permissions on build.prop are wrong but when I try to connect with adb via USB, my computers don't recognize the device. I press volume down + power and then plug the phone in. Nothing comes up when I issue ./adb devices. I've tried on both a Windows 7 desktop and a Macbook.
Am I missing something with adb and my connection procedure? Am I just hosed? Is there any way to get this device running again, even if it means a factory reset?
Click to expand...
Click to collapse
Do you have a custom recovery? If so, you can adb push a stock build.prop to /system after mounting /system in recovery (think it's adb shell mount /system). Your other option is to use fastboot and flash system.img. It would be best to use whatever 5.1 build you are on. I would think you'd be able to boot fine after just flashing system.img, but you could also erase cache and userdata if it doesn't. Whatever you do, don't lock your bootloader, at least until you know you can boot up normally.
mwalt2 said:
Do you have a custom recovery? If so, you can adb push a stock build.prop to /system after mounting /system in recovery (think it's adb shell mount /system). Your other option is to use fastboot and flash system.img. It would be best to use whatever 5.1 build you are on. I would think you'd be able to boot fine after just flashing system.img, but you could also erase cache and userdata if it doesn't. Whatever you do, don't lock your bootloader, at least until you know you can boot up normally.
Click to expand...
Click to collapse
It's stock recovery. I'll give fastboot a try.
Worked like a charm. I don't know why I didn't think of it last night. I was so fixated on that file, heh. Thanks a bunch, man!