When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!
Your not actually changing direcotry into the correct directory. so when you call the fastboot command it's looking in the current directory of "c:\Users\Marc" instead.
cd \Program Files(x86)\Android\android-skd\platformtools
adb reboot bootloader
fastboot flash recovory recovory.img
Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App
Thanks guys, Ill try again.
ghoticov said:
When I rooted, I used the one click method and worked like a charm. Now, I would like to learn how to flash the files via adb. I am a novice user of adb but have used it.
Right now, I am trying to flash the recovery.img file. Here is what I am getting:
I have the recovery.img file in my /platform-tools folder. When I go to devices, I see my xoom listed and I do screen shots all the time using the ddms.bat file.
Can anyone tell my why my xoom will not let me flash files? I tried this a few weeks ago with the first Tiamat SDCard enabled kernal and it said the same thing, it wouldn't let me flash the file.
Thanks!
Click to expand...
Click to collapse
*FACEPALM*
jase33 said:
Did you open the command line from the same folder you have the file you want to use? If not, open the folder you have recovery.img and the other files you will be using are in and hold the shift key on the keyboard and right click on the mouse. Then left click on "open command window here". Then run your adb commands.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Does this work using Vista? I do not see the option to "open command window here".
Duh, nevermind... I figured it all out. I was putting a \ after platform-tools so it wasn't actually opening the folder where the recovery.img file was. Told you I was a novice. But I am getting it!
This is why one-clicks are the root of evil. If you would have done it manually from the start, you would have already known what to do here . Also since you posted this in development, i'm looking forward to the release, although i'm unsure what you are releasing at this point...
Ok people... Let's be mature here and not flame other users. This is supposed to be a community, not a war zone. If something is posted in the wrong section, or there's a post that breaks forum rules, drop me a pm or report the post. Thanks!
And this belongs in q and a... Since this is a question. Thread moved.
Please follow forum rules and post in the correct section.
damn, I must have missed some good flaming post! Lol
dont feel too bad
hehe I was doing the same thing for a 1/2 hour before I realized that the recovery.img wasn't even in the same folder...got that sorted out tho..
Related
I can't be the only one who likes Halo and can't wait for Reach to come out.
Here's a couple of splash screens I created with that in mind.
They are similar, but the second has one of my favorite quotes from Halo 3 and any one who has read the books knows what it means.
Let me know what you think. (Be gentle though, these are my first ones)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App
The reason I used that quote was because of the references in the halo: the fall of reach (the book). But if anyone wants a specific quote let me know and I'd be happy to include it.
Sent from my Fresh'd out Evo 4g
using XDA App
blkswanpres said:
They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Here ya go.
Hi, was hoping you could help me with this. I followed instructions on how to flash this and the actual sending of it worked but when it tried to write it, it said FAILED (remote: not allowed). Any ideas on what that would mean? Thanks!
You need to have ADB enabled. Put the evosplash1.rgb into your sdk/tools folder. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
fastboot flash splash1 evosplash1.rgb565
fastboot reboot
FattySparks said:
You need to have ADB enabled. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
adb remount
fastboot flash splash1 evosplash1.rgb565
fastboot reboot
Click to expand...
Click to collapse
First, thank you for replying to my post! You are the first one to state the "adb remount" part. I did that but it is saying device not found now. My phone does show the red fastboot usb so do you any further suggestions because it still failed on the writing part. The sending part went fine but I guess it is failing since it cannot find my phone. Might I have the sdk set up incorrectly?
One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.
eaglenest608 said:
One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.
Click to expand...
Click to collapse
when you're in fastboot it shouldn't show up in adb devices. I also forgot to mention to put the rgb565 file into your sdk/tools folder. Other than that it sounds like your setup properly.
Edit: Also the adb remount code isn't needed. I was so used to using it from messing around with bootscreens, I forgot it isn't needed for fastboot.
Yes, it seems I am setup correctly from what I have read. Maybe I should flash to a different rom and see if that helps me. My wireless tether app is giving me problems as well so not sure what has happened but it may be time to give something else a go. Unless you can think of anything new that is, lol. Thanks a bunch though for you help...really appreciate it.
Well, for those that actually care I have now resolved this issue. It turns out that the HBOOT version that I had did not allow me to perform this flash. I had to actually downgrade it to a different one and it worked perfectly. I wish to thank those that actually took the time to reply to my post...it was greatly appreciated!!
Realize I posted the screen of the new quote, but didn't attach the file... duh
Halo Reach Boot animation
http://forum.xda-developers.com/showthread.php?p=8419483#post8419483
PLEASE
Can you do one that says
"Halo:Reach>MW2"
That would be epic
Sorry for the delay, got married last weekend.
Here ya go.
Ohhh this is Perfect the delay is no problem but seriously thanks alot and congrats on the marriage
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Bertrum said:
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Click to expand...
Click to collapse
http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I liked this guide. First time rooting.
On command prompt, you have to go to the Android\android-sdk\tools folder then execute those fastboot command.
Your command prompt probably says C:\Users\Your User Name.. [I have Windows 7]
Type 'cd..' (without ' ') until your line says C:\>
Then type the following cd Program Files\Android\android-sdk\tools
It could be Program Files (x86) not Program Files.. depends which bit you have. You can type those fastboot command from there.
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Bertrum said:
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Click to expand...
Click to collapse
Did you download ClockWorkMod img and paste it into android-sdk\tools folder? You can do that my opening My Computer folder -> C:\ -> Program Files -> Android -> android-sdk -> tools folder.
Then open command prompt and type like that. I just did the first line for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yours could be Program Files, not Program Files (x86) though. I downloaded 32-bit version accidentally and I didn't wanted to do it over.
After that you use your Nexus S to boot into bootloader [which the instruction says] and continue on.
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Bertrum said:
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Click to expand...
Click to collapse
I'm glad I helped. I had hard time rooting yesterday but it's all good now
I finished everything last night. All unlocked and rooted. Also running CM7 rc2 with the n14 kernel.
Its soo fast compared to my old blackberry and my friends galaxy.
Many thanks to the people who worked on the roms and kernels. Your knowledge astounds me.
Sent from my Nexus S using XDA Premium App
Took some time early this morning to create some boot logos.
Sensation types:
SHIFT+CLICK to download
1). adb reboot bootloader
2). fastboot flash splash1 theimagefile.img
3). fastboot reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ARevoSensationPlatform
ARevoSensationWhite -- Right click, save link as...
aPinkSensation
aSpecSensation
bevelSensation
OrangeSensation
enjoy ladies and gentlemen.
----second----
left for future use.
dcrin3 said:
left for future use.
Click to expand...
Click to collapse
Looks good; did you simply change the BMP's to the IMG extension or did you actually have to format it?
no, the images are formatted with nbimg already.
nice job m8 !
I was asking to find out the steps to make them....but NBimg looks like the winner. Thanks!
Name the file whatever .img I use custom.img
Put it on your sdcard
Open terminal emulator
Su
dd if=/mnt/sdcard/custom.img of=/dev/block/mmcblk0p14
Sorry just this way is easier lol... At least to me
hks18psigst said:
Name the file whatever .img I use custom.img
Put it on your sdcard
Open terminal emulator
Su
dd if=/mnt/sdcard/custom.img of=/dev/block/mmcblk0p14
Sorry just this way is easier lol... At least to me
Click to expand...
Click to collapse
SCORE!!! I have tried the fastboot way & the bootloader flash way. Neither would work for me but this did the job first time. Thanks
dont work for me, image is too flow....
thanks.......
wallah said:
dont work for me, image is too flow....
thanks.......
Click to expand...
Click to collapse
what do you mean "too flow"?
Sorry, not flow, but blur...
hks18psigst said:
Name the file whatever .img I use custom.img
Put it on your sdcard
Open terminal emulator
Su
dd if=/mnt/sdcard/custom.img of=/dev/block/mmcblk0p14
Sorry just this way is easier lol... At least to me
Click to expand...
Click to collapse
i tried fastboot and terminal emulator with the code you put and "cannot open for read: No such file or directory"
any suggestionds?
go here http://forum.xda-developers.com/showthread.php?t=956434
and do with that, its work for me
Thx got it to flash
Sent from my HTC Sensation using XDA App
can I have the 1st and last image without the wording?
I made one too this morning.
In the rar is the .im file ready to use.
Can somebody make this one BOOT-SPLASH ready ?
here you go
is in the rar file
Here's what's currently living in my splash1
the silver one is gr8t thanks dawg
Right, I'm sure there is similar here, but I had loads of difficulty finding it, so I thought I'd create my own version.
I'm a complete noob at this, so I'll make it easier on you, and put it as plainly as possible. EVERY step is listed as if you're in the same [or similar] situation.
I only recently tried to get CM10 onto my phone, and on first try, I soft-bricked it. I unlocked the Bootloader, Rooted, Installed TWRP and a version of CWM when it didn't work, and CM10 seemed to work fine, but upon booting for the first time, and leaving it for about 15 minutes, I realised something went wrong. Tried going back to the most recent RUU [the EU OTA version], and that didn't work [after relocking the bootloader, yes]. Started freaking out a small bit, as it stopped letting me mount the storage in Recovery, even though ADB could still see the phone.
Asked a friend to help, and we found this over on the One X sub-forum.
BEING AWARE THIS IS RELATIVE TO hasoon2000's All-In-One Toolkit
[nice work btw! Might wanna look into this btw - it may be a small bug with your software. No offense ]
Turned out it was the boot.img that installed incorrectly, so making sure the .zip MD5 is correct is first step.
If that's not the issue, the 2nd step is to just open the .zip and take the boot.img out of the root of the container, and pushing that to the phone using ADB [the one that come's with the AIO is perfect]. If you're not sure how to get into ADB, and get it to stay open, here's what you do:
1. Copy the directory of "adb.exe" within your AIO's "data" folder [for example, mine is D:\Administrator.Sheol\HTC\All-In-One\Data\]
Click to expand...
Click to collapse
2. Open Command Prompt [in Vista onwards, type "cmd" into the Start menu Search Bar, in XP, open the "run" dialog in type cmd. Alternatively, find it in Start > Accessories, in all recent versions of Windows]
Click to expand...
Click to collapse
3. Type the following into Command Prompt:
cd D:\Administrator.Sheol\HTC\All-In-One\Data\
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remembering your directory WILL be different, so adjust accordingly!
Click to expand...
Click to collapse
4. It'll list all ADB's command's. Don't worry, it's meant to. If you want to, skim through them to familiarise yourself with it. At this point you may want to maximise the window, to fill the screen height [makes every thing much easier]
Click to expand...
Click to collapse
5. Follow this thread to the tee > [Tutorial] How to flash a new boot.img via Fastboot
Click to expand...
Click to collapse
Doing exactly this, worked a charm, and now I have a flawless CM10 HTC One S! After the GApps install of course [which can be done in your Recovery after downloading it/pushing it to your phone, by using the "Install from .zip" option]
Hi..I have Android L installed on my N5 and want to root it..so I have been following THIS guide, to install custom recovery and then I plan on rooting it using THIS thread..
While following the first guide to install TWRP..I am getting the following error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone please help me with this error..I tried the TAB to search for the recovery.img..but it did not work
if I hit Tab after 'fastboot flash' then I am not getting first 'recovery' option.
Not sure if this will help..here are the contents of the slimmed down android sdk I downloaded from first guide:
rockstar283 said:
Hi..I have Android L installed on my N5 and want to root it..so I have been following THIS guide, to install custom recovery and then I plan on rooting it using THIS thread..
While following the first guide to install TWRP..I am getting the following error
Can anyone please help me with this error..I tried the TAB to search for the recovery.img..but it did not work
if I hit Tab after 'fastboot flash' then I am not getting first 'recovery' option.
Not sure if this will help..here are the contents of the slimmed down android sdk I downloaded from first guide:
Click to expand...
Click to collapse
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.
GTI6speed said:
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.
Click to expand...
Click to collapse
was having the same problem and this actually fixed it, thank you sir
All, please have a read of my "adb and fastboot. What is it?" thread. It can be reached via the sticky roll up link in my signature.
You shouldn't need to put recover where you put it. My thread explains how to use it properly.
Sent from my Nexus 5 using Tapatalk
GTI6speed said:
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.
Click to expand...
Click to collapse
Thanks a lot mate..that did the trick..DUMB mistake