Related
To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot.
4.Remember that you need to be rooted
awesome I am using it now
The Rubenator said:
To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot
Click to expand...
Click to collapse
What does "fastboot flash splash1 evosplash1.rgb565 mean?"
From a terminal window? Or what? Regular adb push? While the phone is on the fastboot screen?
Run Command, put your phone into bootloader once in there push the file from a terminal window while the phone is on the fastboot screen just like the way I post it.
The Rubenator said:
Run Command, put your phone into bootloader once in there push the file from a terminal window while the phone is on the fastboot screen just like the way I post it.
Click to expand...
Click to collapse
so do you put the zip on the root of your sd card before pushing?
too bad you have to be rooted for this..
BAleR said:
so do you put the zip on the root of your sd card before pushing?
Click to expand...
Click to collapse
No, you put the evosplash1.rgb565 file on the tools folder of your SDK folder
Nice boot screen!
Instructions for users on a mac:
Boot phone into fastboot
Download Green Android Splash.zip and unzip the files into your android sdk tools folder
Load up terminal
CD into the android sdk tools folder
Enter the command: ./fastboot-mac fastboot flash splash1 evosplash1.rgb565
Then once it's completed enter the command: ./fastboot-mac reboot
Your Evo should reboot with the new boot screen.
Did it and still have my previous splash screen.
bunch great splasheds posted today D:
effluent said:
Did it and still have my previous splash screen.
Click to expand...
Click to collapse
Are you rooted effluent?
I am having a bit of a problem flashing this as well... I have unzipped the file, and copied the evosplash1_rgb565 file into the sdk/tools folder on my computer. I reboot the phone into fastboot (Vol down/power, when in HBOOT, verify cursor on fastboot, press power) Phone enters fastboot and shows "FASTBOOT USB" in red letters. I go into my cmd: and type the "fastboot flash splash1 evosplash1.rgb565". I get "error: cannot load 'evosplash1rgb.565'
To verify that I was connected to the phone in fastboot, I have done 2 things. First, I entered "fastboot devices" the cmd: returned HTxxxxxxxx (device name) followed by fastboot. I also typed "fastboot reboot" which rebooted the phone.
Please tell me where I am going wrong.
Thanks, and great work on the recent splash screens you are putting up.
Anybody???? I tried leaving as much detail as possible, to try to rule out "Did you try ______?" replies. I just want to be able to change my boot screen, and the given instructions didn't work for me... Does ANYBODY have any insight into what I did wrong, or what I could do differently to change the bootscreen?
BTW, yes, I am fully Rooted via toasts method, and running Damage Control 3.2.3
1-Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb. If you type the command.
Code: fastboot devices
2-it should show you your phone. Next type the following command
Code: fastboot flash splash1 splash.rwa565
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image.
Sorry if you having any issues, I just took a look at the files and everything seen to be working perfect.
The Rubenator said:
To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot
Click to expand...
Click to collapse
The Rubenator said:
1-Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb. If you type the command.
Code: fastboot devices
2-it should show you your phone. Next type the following command
Code: fastboot flash splash1 splash.rwa565
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image.
Sorry if you having any issues, I just took a look at the files and everything seen to be working perfect.
Click to expand...
Click to collapse
Ok, thanks for chiming in with a fix.... In your first post, you said to use: fastboot flash splash1 evosplash1.rgb565
Now it is: fastboot flash splash1 splash.rwa565 ?
Just verifying, would I need to rename the file (bootscreen image), since in the download, it is evosplash1.rgb565 ?
1-Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb, or do it using "Quick Boot.apk" drop the file into your sdcard and install from there as a normal apk file.
once you run "Quick Boot select "Bootloader"
Remember that you need to put evosplash1.rgb565 into the android-sdk/tools folder.
If you type the command
Code: fastboot devices
2-it should show you your phone. Next type the following command
Code: fastboot flash splash1 splash.rwa565
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image.
I want to give thanks to "RikusHaven" for the help.
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"
Ummmmm...... You said that last time..... Also, you obviously did NOT read my original question, because you keep feeling the need to tell me how to get into fastboot. I said in my first question, in detail, how I was getting into fastboot, what I was typing, etc. You obviously ALSO didn't read my 2nd question, which asked if I need to rename the image, since in the first post you call it evosplash1.rgb565 and now you call it splash.rwa565. Any time I have ever had to move, copy, delete, etc... a file, I had to tell the computer WHAT file it is I want it to work with. By having a file named one thing, and telling the computer to work with another file, it doesn't make sense to me that the computer will miraculously know what to do. IF a rename is not needed, a simple "No, fastboot will find the file on its own" or something similar would have been enough, but to retype all the steps that I had already said I had taken, and still not providing a definitive answer to the question, shows that you aren't reading what the problems people are having. I tried to be as descriptive as I could, in posting my problem, rather than just saying "It don't work", and It is still taking multiple questions to try to find an answer.
If there is any doubt as to what steps I took, PLEASE scroll up and read Post #12. It tells in detail, What steps I took, What I typed, What error message I received, AND what I did to verify that I was in Fastboot.
thenewguy821 said:
Ummmmm...... You said that last time..... Also, you obviously did NOT read my original question, because you keep feeling the need to tell me how to get into fastboot. I said in my first question, in detail, how I was getting into fastboot, what I was typing, etc. You obviously ALSO didn't read my 2nd question, which asked if I need to rename the image, since in the first post you call it evosplash1.rgb565 and now you call it splash.rwa565. Any time I have ever had to move, copy, delete, etc... a file, I had to tell the computer WHAT file it is I want it to work with. By having a file named one thing, and telling the computer to work with another file, it doesn't make sense to me that the computer will miraculously know what to do. IF a rename is not needed, a simple "No, fastboot will find the file on its own" or something similar would have been enough, but to retype all the steps that I had already said I had taken, and still not providing a definitive answer to the question, shows that you aren't reading what the problems people are having. I tried to be as descriptive as I could, in posting my problem, rather than just saying "It don't work", and It is still taking multiple questions to try to find an answer.
If there is any doubt as to what steps I took, PLEASE scroll up and read Post #12. It tells in detail, What steps I took, What I typed, What error message I received, AND what I did to verify that I was in Fastboot.
Click to expand...
Click to collapse
youll need to replace evosplash1.rgb565 with whatever the correct file name you are flashing is.
I'm having issues as well. I've done this before without problems, but now i get waiting for device. My phone is on the fastboot usr screen. (power off, hold vol down then power on, then power again to get to fastboot screen)
I like that blue one. Good stuff bro.
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
New Jer-Z said:
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
Click to expand...
Click to collapse
You skipped right over the "can't seem to able to flash a recovery."
Please explain in detail the instructions you followed AFTER unlocking via HTCdev.com. This includes files you downloaded, where you put them, how you attempted to flash, etc.
These details will be very helpful. Don't worry, sounds like you're not in any serious trouble at all. Just don't go flashing anything you see.
Also, please post this to the Q&A forum or General next time. This development forum is intended for development posts ONLY (ie. ROMs, Kernels, Radio's, etc). Just a heads up. Welcome to the forums
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Moved To Q&A
Please post all questions in the Q&A section
New Jer-Z said:
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Click to expand...
Click to collapse
Ahhh, not to stir up the pot here, but you're getting vague again with what's going on. You say "when I try to reboot into recovery, I don't get very far". What do you mean by this? Details are extremely important in helping you. Sounds like you're saying that recovery was successfully pushed, but then I didn't get any details as to what's going on when you attempt to load recovery. Also, which recovery file did you use? Use this one
I'm not trying to get on to your case here, but you've got to be really specific when you say stuff doesn't work, because that doesn't help us diagnose your issue. When your recovery is done flashing, you should be able to access the bootloader by holding Pwr + Vol-Down for like 5 secs, then choose recovery (that or fastboot>recovery....I cant recall if recovery is a main menu item). What happens after you choose that? Mine shows the htc splash screen, with a development message in red, and then it boots Clockworkmod.
No, no, lol I totally understand, I guess I am being vague.
I was going to go into details, but I was at work. Interestingly enough, my phone died, and when I plugged it and let it charge for a little bit, the phone booted right into CWM touch - so odd! So I was like, ok, i've achieved root - well, no, cuz I opened ROM Manager and it says SU couldn't be found.
BEFORE, when I would do what you said I should do, it would take me to the HTC splash screen where it was in red text, some disclaimer about some proprietary information crap, then it would skip recovery and just boot into Android -___-
Let's see if I can replicate booting into recovery now. (What method are you using to flash your recoveries?)
EDIT: Well it looks like I can't get back into recovery. Same thing as mentioned above. I can get to the fastboot screen, but if I click recovery, it takes me to that HTC disclaimer screen, the little loading bar loads then - poof - screen goes blank and Android boots up.
I have the same problem -_-! Can someone help please
The recovery image was flashed succesfully from Hasoon2000's toolkit. But when i go to the bootloader and select Recovery, I get the red warning for from HTC about how this is for development purpose only... then the phone's screen goes black, then it boots into the stock ROM.
Cant flash recovery
Hello everyone.
I have a similar problem. I successfully proceeded with the bootloader, but now I can't install the recovery. It simply wont flash.
I was following the xda tutorial that's in this very forum, but i got stuck: In my desktop i downloaded the needed files (or so I believe), and so i have in my desktop a folder called "carpeta" (random name) with these files within: adb.exe, adbwinapi.dll, fastboot and 3 different recovery images i have tried to flash.
I use mac, so i open the command prompt for mac (terminal) and go to the "carpeta" folder and after that, I type "cd fastboot flash recovery xxxxx.img" (the xxx are the names of the recovery images that i have in the folder, one at a time) but it simply wont flash anything. I attach a screenshot to ilustrate what happens...
Please help me
http :// img710.imageshack.us/img710/6026/capturadepantalla201205.png
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
I'll give it a shot later tonight on my lunch break.
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
alexjuanes said:
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
Click to expand...
Click to collapse
Make sure that you navigate to the proper folder using the "cd" command.(for example" cd C:\Fastboot ", if your adb and recovery are in that location)
Make sure that the Clockwork Mod recovery file is in the same folder as the adb and make sure that you type the file name correctly
I used these file and put the recovery image inside the folder after unzipping
http://www.mediafire.com/?50baad8rykng2j0
Here is the recovery I used :
http://loadbalancing.modaco.com/download.php?file=r2-modaco-recovery-clockwork-touch-ville.img
But your running Mac so I don't know if the method I used will work for you because I'm on Windows
Doesnt work...
I have the bootloader (when i start in bootloader mode my phone says ***tampered*** and also ***unlocked***.
BUT
I've been 2 days trying to flash my recovery on my htc one s from my macbook, and after i use the command prompt to get to the folder where i have adb, fastboot, my recovery .img file,etc... this is what happens:
-----
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$ fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
-bash: fastboot: command not found
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$
-----
ive already updated all that i could in the sdk manager, or whatever its name is...
please some help?
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
This actually worked for me. I am rooted, and am now running a custom ROM.
Thanks so much for all your help!
Hey everyone
i seem to have made a very tiny bit of progress here since now i can type the commands and make it start, but only that... starting.
my command box is stuck in a "waiting for device" message that will start nothing, and my phone is just there, untouched.
i never thought flashing a recovery would give me this much of a long headache...
help anyone? how do i make my pc stop "waiting for device"?
Have you tried a different USB cable/port? I had a similar problem but moving to a different port worked.
Sent from my HTC VLE_U
I have the same problem i did everything as in the guide posted here http://forum.xda-developers.com/showthread.php?t=1583427
But when i flash recovery through fastboot ( fastboot flash recovery recoveryname.img) everything goes ok but when i want to boot into recovery i get stuck on the HTC screen.
Than i wanted to go to recovery trough fastboot ( fastboot boot recovery ) i get message cannot load recovery.
If you need more info for help i can provide you guys with the screenshots.
Thanks in advance Nikola.
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Hi,
my HTC desire S stuck on the htc splash screen
this is what it says on my boot screen when i hold my volume down button and press power button:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.002
RADIO-3305.06.02.03_M
eMMC-boot
Mar 30 2011,17:29,31
i tried to do a factory reset but when i select "FACTORY RESET" it freeze !!
when i get into recovery mode the screen went black and the phone vibrated 7 times and did not start
i installed all needed drivers, so the phone is recognized as "Android ADB interface"
then i tried to use some tools (in fastboot mode) and this is the result :
- adb tools
"adb devices" : List of attached devices is empty => the phone is not recognized by adb
"fastboot devices" : HT13STJ25285 fastboot => the phone is recognized
"fastboot getvar cid" : cid:VODAP120
when i use fastboot command to flash the phone it always says :
< waiting for device >
sending 'radio' (25856 KB)... OKAY
writing 'radio'... INFOsignature checking
FAILED (remote: signature verify fail)
same error message for radio.img and boot.img
- Whenever I try revolutionary, it always gets stuck on waiting for device...
- RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410 (the official ROM)
the RUU detect that the phone has the version 1.47.163.2 and says that it will be upgraded to 1.47.401.4 but it always get stuck on "rebooting to bootloader..."
- i downloaded the file PG88IMG.zip, put it on the sd card and rebooted into bootloader but nothing happened, it show me the bootloader menu and don't detect the file
I also tried to de all steps using HTC drivers witth HTC Sync installed, but always no solution !
Any help is appreciated!
thanks you
Radhouane
According to the internetZ you need a ROM branded by A1 (Vodafone France) (because the red number is the code for it ^^ 1.47.163.2)
Try this one (the blue button)
I recommend you to stay on that ROM afterwards and go S-OFF.
radhouanev12 said:
Hi,
my HTC desire S stuck on the htc splash screen
this is what it says on my boot screen when i hold my volume down button and press power button:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.002
RADIO-3305.06.02.03_M
eMMC-boot
Mar 30 2011,17:29,31
i tried to do a factory reset but when i select "FACTORY RESET" it freeze !!
when i get into recovery mode the screen went black and the phone vibrated 7 times and did not start
i installed all needed drivers, so the phone is recognized as "Android ADB interface"
then i tried to use some tools (in fastboot mode) and this is the result :
- adb tools
"adb devices" : List of attached devices is empty => the phone is not recognized by adb
"fastboot devices" : HT13STJ25285 fastboot => the phone is recognized
"fastboot getvar cid" : cid:VODAP120
when i use fastboot command to flash the phone it always says :
< waiting for device >
sending 'radio' (25856 KB)... OKAY
writing 'radio'... INFOsignature checking
FAILED (remote: signature verify fail)
same error message for radio.img and boot.img
- Whenever I try revolutionary, it always gets stuck on waiting for device...
- RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410 (the official ROM)
the RUU detect that the phone has the version 1.47.163.2 and says that it will be upgraded to 1.47.401.4 but it always get stuck on "rebooting to bootloader..."
- i downloaded the file PG88IMG.zip, put it on the sd card and rebooted into bootloader but nothing happened, it show me the bootloader menu and don't detect the file
I also tried to de all steps using HTC drivers witth HTC Sync installed, but always no solution !
Any help is appreciated!
thanks you
Radhouane
Click to expand...
Click to collapse
You may solve this issue by following the given procedure:
Required
1. one micro sd card (any one, any capacity)
2. battery fully charged or minimum 50 %
Procedure
1. Turn off phone
2. Remove battery for 30 seconds
3. Put back battery.
4. Press Volume down (first) + Power button (last) [boot-loader screen will appear]
5. Go to recovery by using volume down key and press power button.
The recovery logo with red triangle sign will appear on the screen
6. Press Volume Up + Power button several times
You will see the option menu appears with blue color font stating 3 - 4 options
1, Reboot
2. Wipe dalvik cache / format (dont remember exactly what appears)
3. Wipe cache
Select the option 3 first by wiping cache and then select the 2nd option by wiping format (or something written)
and finally select the Reboot option.
Then i hope your phone will start up and run smoothly.
If it works for you Just give me a thanks
arif01 said:
You may solve this issue by following the given procedure:
Required
1. one micro sd card (any one, any capacity)
2. battery fully charged or minimum 50 %
Procedure
1. Turn off phone
2. Remove battery for 30 seconds
3. Put back battery.
4. Press Volume down (first) + Power button (last) [boot-loader screen will appear]
5. Go to recovery by using volume down key and press power button.
The recovery logo with red triangle sign will appear on the screen
6. Press Volume Up + Power button several times
You will see the option menu appears with blue color font stating 3 - 4 options
1, Reboot
2. Wipe dalvik cache / format (dont remember exactly what appears)
3. Wipe cache
Select the option 3 first by wiping cache and then select the 2nd option by wiping format (or something written)
and finally select the Reboot option.
Then i hope your phone will start up and run smoothly.
If it works for you Just give me a thanks
Click to expand...
Click to collapse
Hello Arif, thank you for your reply.
I have already done this manipulation, but when it displays the red triangle, I press the button Vol UP + Power button, then the screen goes black and the phone vibrates 7 times
radhouanev12 said:
Hello Arif, thank you for your reply.
I have already done this manipulation, but when it displays the red triangle, I press the button Vol UP + Power button, then the screen goes black and the phone vibrates 7 times
Click to expand...
Click to collapse
The phone only restarts when you press Vol down at that stage regardless of pressing power button at the same time, please check your volume buttons and ensure that you are pressing Vol up + power button.
arif01 said:
The phone only restarts when you press Vol down at that stage regardless of pressing power button at the same time, please check your volume buttons and ensure that you are pressing Vol up + power button.
Click to expand...
Click to collapse
my volume buttons are working very well and i'am sure that i have pressed volume up and power button, but the phone always vibrate 7 times and the screen goes black
radhouanev12 said:
my volume buttons are working very well and i'am sure that i have pressed volume up and power button, but the phone always vibrate 7 times and the screen goes black
Click to expand...
Click to collapse
Sorry friend than i do not have any other solution
but you can try to S-off and than install recovery from Clockwork
than try to wipe all the caches and make a backup of your current ROM
hope this will help you
Have you tried the RUU from my link?
Jann F said:
Have you tried the RUU from my link?
Click to expand...
Click to collapse
yes jaan F, but it get stuck on "rebooting to bootloader..."
Where are you from, maybe we can S-OFF it via XTC Clip or check the phone with the diag.
First, you’ll need ADB and fastboot, which can be downloaded here. To set up ADB, go to Settings/About Phone/Software Info and tap on build number until you get a toast notification saying “You are now a developer!” You will now have a new category in Settings called Developer Options. Go into developer options and enable USB debugging and OEM Unlock. You won't be able to turn it on if your phone is plugged in to your PC. Once you've turned it on, go to your PC, open Terminal or Command Prompt and type “adb devices”. Then plug in your phone and hit enter. You'll get a prompt on your phone to “Allow connections to this PC?”. Check Always allow and Allow. Now run “adb devices” again. Your device should now appear in Terminal.
If you have a SD card, download the latest zips from here and here onto your SD card. It'll save you a step later on.
Then you'll need to reboot to fastboot by holding down VOL- and plugging in USB while power is off. Alternatively, you can type “adb reboot bootloader” in Terminal or Command Prompt.
Next, you'll need to unlock the bootloader. Bootloader unlocking will factory reset your phone! Once you're in fastboot, run “fastboot oem unlock” in Terminal or Command Prompt. Now the bootloader is unlocked.
Now it's time to flash TWRP, a custom recovery for Android. It's going to be the way you install custom ROMs and add-ons. Download Official TWRP here. Once you've extracted the recovery.zip, run this command: “fastboot flash recovery path/to/recovery.img”. Once the file has flashed, disconnect the USB cable and battery. The next step is important! You're going to need to boot into TWRP for the first time. With the phone off, hold down VOL- and press power until the phone vibrates and the LG logo appears. While still holding down VOL-, release and immediately press and hold power. You should now be at a white screen that says “Reset all data and restore to factory settings?” Use the volume and power keys to select yes and yes again. If you've installed TWRP successfully, it won't actually factory reset your phone. Now you should see the TWRP screen. If you don't see the TWRP screen and instead see a floating ring that says “Erasing”, don't worry. Let if complete and try flashing TWRP in fastboot again.
In TWRP, you'll be greeted by a screen that says “Swipe to allow modifications?” Swipe it, then go to the Wipe tab. Go to Wipe, then Format Data, then type yes, then go to the Reboot tab and select Recovery to reboot into TWRP again. If you're prompted to install the TWRP app, don't bother.
Once you've rebooted into TWRP again, it's time to disable encryption and root the phone. Download the latest zips here and here. Skip downloading them if you already put them on your SD card earlier. On your PC, push the files to your phone using the command “adb push path/to/file.zip /sdcard/”. You can drag and drop the file into Terminal or Command Prompt to copy file path. Then go to the Install tab in TWRP and select the no-verity-opt-encrypt.zip, tap Add more zips, then add the root zip, then swipe to flash. Let the zips flash, then tap the Reboot System button when it's done. Your phone will take a little longer to boot and might reboot a couple times.
Once you're back in the OS, go through the setup wizard. Set up Magisk. If you stay on stock, you should install an app like Quick Reboot Pro from the Play Store to make it easier to reboot into recovery. Now reboot back into TWRP and go to the Backup tab. If you have a SD card, set it as the backup location. You can enable compression if you want. This will make a full system backup that you can restore from as long as you have TWRP. If the backup takes up too much space, you can put it in Google Drive or your PC later on.
You are now ready to install ROMs!
Thanks to @messi2050
My device will not start boot loader with command "adb reboot bootloader" or with the method of holding volume down and pugging it into the PC, it just restarts and boots like normal. i cannot even get to the stage to use the command "fastboot oem unlock"
I cant get it too boot into TWRP
? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.
meg540 said:
? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.
Click to expand...
Click to collapse
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?
SM210 said:
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?
Click to expand...
Click to collapse
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.
meg540 said:
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.
Click to expand...
Click to collapse
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit
SM210 said:
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit
Click to expand...
Click to collapse
Ill try that i think i wasnt doing it correctly i was holding down power button then i let go an i was holding down the down button. Ty for u help ill try it later today.
Hey there, I've got the LG K530F, is there any chance of unlocking it? I looked up the LG developer website and it's not listed in there, filling that form will just lead to a popup regarding that. I thought about downgrading it back to MM (Android 6.0) using the K350F10d_00_02221.kdz firmware package aiming to be able to run fastboot oem unlock, but I'm afraid of getting it bricked. Anyone tried it? I recall doing something like that to unlock the LG Optimus L9, but that one was way older and had much weaker security measurements.
Can't get into Bootloader
Hi i have a LGL82VL and when trying to use adb reboot bootloader it just restarts, And when using Vol Down and Power it just comes to the factory reset page (Hard Reset)
Any ideas on how to get to the bootloader? i checked with fastboot devices while on the hard reset page and got nothing. Any Ideas?