I am having this problem. I enter to fastboot mode (with Volume Down+Power Button), but then when I chose recovery mode I get this screen
{
"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"
}
In this case, I have to wait like a minute and it will reboot normally.
It happened to me several times, until once it entered without problems and I was able to root my device. Now I want to flash the AOKP rom, and I got to the same screen over and over.
Does anybody know what could be happening ?
What custom recovery are you using? The quick answer would be that you should just reflash CWM or TWRP.
That screen is showing you that the android is broken. It seems like maybe ROM manager or goomanager or something else didn't do a good job of flashing your custom recovery image.
just start up the N4 to bootloader/flashboot screen
drop your CWM or TWRP file in your fastboot directory (mine is c:\android-SDK\platform-tools\)
run cmd
Then type what's inside the quotes:
"fastboot devices"
[your n4 should be listed]
"fastboot flash recovery [recovery image file name]"
[for me] "fastboot flash recovery recoveryCWM.img"
you should then load up your recovery on the n4 and it should start up properly.
I'd download your recovery image again too since it might be bad.
thehumble1 said:
What custom recovery are you using? The quick answer would be that you should just reflash CWM or TWRP.
That screen is showing you that the android is broken. It seems like maybe ROM manager or goomanager or something else didn't do a good job of flashing your custom recovery image.
just start up the N4 to bootloader/flashboot screen
drop your CWM or TWRP file in your fastboot directory (mine is c:\android-SDK\platform-tools\)
run cmd
Then type what's inside the quotes:
"fastboot devices"
[your n4 should be listed]
"fastboot flash recovery [recovery image file name]"
[for me] "fastboot flash recovery recoveryCWM.img"
you should then load up your recovery on the n4 and it should start up properly.
I'd download your recovery image again too since it might be bad.
Click to expand...
Click to collapse
Thank you very much! That did the job! (I was using CWM).
Related
Hi Guys,
i have a very specific issue.
Its HTC hero which been upluged before finishing official upgrade to froyo.
So, where is the problem?
Hero cant boot, all the time just stay stucked on "HERO" boot animation. The problem is, that it was upgrade from stock Eclair to stock Froyo. They didn't have any root, or recovery (CWM, RA, nandroid)...
The phone can be started in hbot, fastboot, stock recovery.
HBOT->
I've found this > http://forum.xda-developers.com/showthread.php?t=575448 < but i think its need a function hero to set up setup.
So there is no way i think
Fastboot->
I've try to flash recovery with AR, CWM via
"fastboot flash recovery recovery.img"
but only get this
{
"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"
}
Stock recovery->
I've also try to flash via "apply update.zip from SD card" from this
http://www.modaco.com/topic/291942-22jan-stock-roms-radios-in-updatezip-format-for-gsm-hero/
every single file crashed "E:Verification failed!"
I'm such a big noob, but is there any way which i didn't try? Something like flash CWK recovery mode via update.zip? Every idea can help.
Thanks
Do you have your hero drivers set up on your PC?
Also, when flashing recovery.img using fastboot, please rename your clockworkmod.recovery.blablabla.img in recovery.img and then try to flash again.
as i thought so
prntscr.com/aun85 <its a link, but i'm newbie here, so i have a constraints
but its exactly the same as the file was named clockwokrmod.....img
Driver should be ok (get from android-cellphones com)
Q: how can i access the adb? In device manager a use this driver. But in cmd "adb devices" cannot find my hero. But idk if it helpfull.
Sorry for my english
When your phone is plugged in your windows PC (in hboot mode), check that the driver installed is called My HTC (in device manager), then download the latest RUU under HTC Hero support site (not the 2.1 one) and run the program, it will erase everything, but if it is successful it will install the 1.5 system to your phone, and you can start over
Sent from my GT-I9100 using xda premium
Problem was solved via hboot mode. Thx guys
Hey Everyone!
Its not new that there is quite some chaos regarding the fastboot mode on our device. Though some could access it, others could not. All that would happen when I tried to reboot into bootloader was that it would get stuck on the boot logo. Many said that the bootlogo itself was the fastboot mode. However lsusb on my linux term would not recognize anything attached. So I was quite sure there was some issue. Recently when I was having a chat with Nori, I could confirm that the same. It so happens that when he boots into fastboot mode, there appeared a tiny text at the left bottom of the screen would appear saying the device was in fastboot mode.
A little bit of research and experimentation, I figured out that there was an issue in the appsboot image on the Indian version. So, I flashed the Taiwan version of the aboot on my device and VOILA! I had fastboot mode! Here is how you can get it.
BEFORE I GO ANY FURTHER, I MUST WARN YOU THAT THIS IS HIGHLY RISKY IF DONE WRONG! THERE IS A RISK OF HARD BRICKING YOUR DEVICE! AND I AM NOT RESPONSIBLE FOR WHATSOEVER THAT HAPPENS TO YOUR DEVICE.
1) Head over to http://140.115.126.139:808/gplus_e7/E7_0301_v5832_IMG/ or here
2) Download the aboot.img and save it to the root of your sdcard.
3) Open up a terminal emulator or adb shell and type in the following code.
Code:
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4) Thats it.. Now reboot into bootloader using any rebooter or using adb and you should see something like this
{
"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"
}
(sorry for all the dust.. should have viped it I guess.. well, atleast shows how good the camera is..)
Good Luck!!
hi.
my device goes to fastboot mode but fastboot command is not working on it.. what can be pb..?
\Desktop\GenerelMobile_Elite>fastboot oem unlock
< waiting for device >
pc detects is "Android Composite ADB Interface" in the device manager..
adb reboot-bootloader is working or wol down + power on..device goes to fastboot mode..
but not working on root directory..
Code:
[email protected]_MOBILE:/ # fastboot reboot
fastboot reboot
[B]sh: fastboot: not found[/B]
127|[email protected]_MOBILE:/ #
this should be closed this does not work
gaganpattanayak said:
this should be closed this does not work
Click to expand...
Click to collapse
It works fine for me. Have you followed the instructions properly?
Yes it goes to the screen and then if you give a fastboot command something seems to happen but nothing happens
HI , my phone gionee e7 is in fastboot mode..I dont know how it got into this mode .. can you tell me how to exit from this mode and get the phone started
my fone is stuck on fastboot mode how to get over it ?
Hello guys, just wondering if there is a way to reload the factory recovery partition?
I am getting a demigod error and cannot do anything in recovery once I try to restart into it, but the phone when restarted works fine with the factory image.
I tried to load a custom rom and done screwed up
I did make a recovery backup, but I am pretty sure I screwed it as I was trying to copy recovery.img to the phone during some un-bricking troubleshooting.
Thanks
Okay guys, I know I should be doing my own research but I'm stuck.
I found this youtube video:
https://www.youtube.com/watch?v=hQVTc2m6U-I
I've downloaded all of the LG G2 D801 T-Mobile files:
http://downloads.codefi.re/autoprime/LG/LG_G2/D801BK/Stock_Firmware/20a_partitions
I am able to get ADB to recognize my device and I am able to 'send' commands via fastboot BUT my phone doesn't seem to accept them.
I've tried via command line and using SRK tool:
Here is what happens when I try to run the fastboot commands in fastboot mode (UP button + USB plugin)
{
"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"
}
Here is what I get when I try to run SRK Tool:
So as you can see from the output, the phone is detected and it seems like the files are in the process of being 'sent' but nothing actually installs.
When I was doing it in command prompt, I let it sit for a few minutes for a few commands and they just sat there at writing.
On the phone itself, this is what it states at this moment:
[500] fastboot mode started
[500]--reset--
[500]--portchange--
[500]--reset--
[500]--portchange--
[500] fastboot: processing commands
[500]fastboot: getvar: partition-type:laf
[500]fastboot: getvar:max-download-size
[500]fastboot: download:00e00000
[500]fastboot: flash:laf
That's all I get on the phone, nothing changes. It just sits there idle.
I am unsure what to do and was wondering if anybody knows how I can fix this?
So I seem to be having some kind of issue with the phone not accepting fastboot commands and/or my computer is not recognizing fastboot.
I did install the ADB/Fastboot installer. I have Java and SDK installed.
When I try to run ADB devices, it identifies the device.
When I try to run fastboot devices, all I get is:
command prompt> fastboot devices
? fastboot
That's all.
Anyone? I am having the same exact problem and have not found a fix yet.
Look at my last reply here: http://forum.xda-developers.com/lg-g2/help/g2-fastboot-mode-t3427770 it may work
I have flashed twrp recovery on my redmi note 4g. But after flashing when I rebooted to recovery mode, The teamwin logo appeared 4 times divided on my screen. I am unable to read any option.
Please give me a solution for this. I am attaching an image of my problem. Please help me.
{
"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"
}
aks279 said:
I have flashed twrp recovery on my redmi note 4g. But after flashing when I rebooted to recovery mode, The teamwin logo appeared 4 times divided on my screen. I am unable to read any option.
Please give me a solution for this. I am attaching an image of my problem. Please help me.
Click to expand...
Click to collapse
Flash this.
ray.77141 said:
Flash
Unable to flash from from my mi recovery. Verification error. I think i need a signed version of this or any other method of flashing?
Click to expand...
Click to collapse
aks279 said:
ray.77141 said:
Flash
Unable to flash from from my mi recovery. Verification error. I think i need a signed version of this or any other method of flashing?
Click to expand...
Click to collapse
Flash Recovery Using Adb Tools
You need 3 things
(a) Xiaomi usb drivers [download from Here ]
(b) adb drivers (download from Here ]
(c) TWRP recovery (TWRP download from Here ]
Procedure:-
1. install xiaomi usb drivers
2. extract adb drivers anywhere in your computer
3. copy recovery.img into adb tools folder
4. boot your phone into fastboot mode by pressing volume down key and pressing power key simultaneously , and then releasing power key .
5. connect your device to your computer through data cable
6. go into adb tools folder => while pressing shift key => right click => and click open cmd here !
7. type "fastboot flash recovery recovery.img" and press enter
8. Done
Click to expand...
Click to collapse
Hi. I am facing an issue with my oneplus 2 device, I wanted to make it boot multiple ROMs so searched on google about this and I found a thread on this website only, and in that thread, there was a recovery and zip file given to flash so I booted into TWRP recovery and flashed the zip file first and then recovery and then reboot-->recovery, after that oneplus logo with "powered by android" text came and for 5 mins nothing happened. I connected the phone to my computer and typed the fastboot command-"fastboot reboot recovery", it reboot and stuck at the same state as before, then I used-"fastboot reboot", it rebooted into the oxygen os which was installed on it. then I flashed the original TWRP recovery using its official app as my phone was rooted. After that, I again tried to flash the multirom recovery but this time I flashed the recovery first and then the zip file but the same happened. I again booted into the rom and flashed the original TWRP recovery using the app and then I got to know on the internet that I should first shutdown the phone after flashing multirom recovery and then reboot it in the recovery and then flash the zip file, so I did the same but to my bad luck this time also same happened and this time I am not able to boot into the rom also and I am only now able to use fastboot and to the very worst my bootloader has also got locked I don't know how but it was unlocked last time but when I saw in fastboot it was saying that bootloader is locked. Please help me to fix my phone I have attached the multirom recovery file and the link to the thread. Please tell me if you all want any other info I will try to provide you that.
LINK TO THE THREAD:-
[MOD][FEB-28][TESTING] MultiROM v33 for OnePlus 2
TLDR: MAKE A BACKUP. Seriously. Downloads in second post. Flash recovery, then kernel, then MultiROM. A kernel with the kexec-hardboot patch doesn't exist as of now. It is being worked upon be me Introduction This is a port...
forum.xda-developers.com
{
"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"
}