Develop Bugs

fire 2 will not boot stuck in boot screen

my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer

dyson77 said:
my kindle fire 2 is stuck in the blue whit fire-fire screen
I can access the twrp recovery but after a incorrect wipe i have no android or so i am assuming.
i have installed the Google usb drivers through adb but the tablet will not show up i explorer
it will show as a android device but will not load anything else.
i have also booted into the twrp and attempted to mount it and it didn't work
lastly i have tried to use a fastboot cable. i get a screen on the device that says fastboot and what looks like a stoplight with the green blinking but again will not show up in explorer
Click to expand...
Click to collapse
First check you have fastboot drivers installed correctly:
Plug the cable into your device and then the computer. Reboot the Kindle. It *SHOULD* show a Fastboot screen. Once at the screen use this command on your computer:
fastboot -i 0x1949 devices
You should see something like this:
0123456789ABCDEF
Click to expand...
Click to collapse
Then enter these commands one at a time
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse

kidicarus1602 said:
First check you have fastboot drivers installed correctly:
Then enter these commands one at a time
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0q-ce_LYNLFQW16QWFEbDlKSUk/edit?usp=sharing
the unit wont show up in explorer at all,I have tried to run the command listed and it just says waiting for device.
I have tried rebooting into recovery reboot and still locks up
any other ideas

{
"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"
}
this is what device manager says

dyson77 said:
View attachment 2709099
View attachment 2709100
View attachment 2709101
this is what device manager says
Click to expand...
Click to collapse
any ideas?

Manually install the drivers.
-》Sent from my mind to your screen.

i have installed the google and adb drivers what other ones are there

dyson77 said:
i have installed the google and adb drivers what other ones are there
Click to expand...
Click to collapse
MANUALLY install the adb drivers.
-》Sent from my mind to your screen.

ok I have manually installed the drivers.
it then was showing up as a Otter-2
I then went through the same steps to add the drivers for it as a google usb driver.
but its still not showing up in my explorer and when i do a adb devices it doesn't show up
mind you that was all with the fastboot cable
when I hook it up with a standard usb and gho into the teamwin twrp it shows as a Kindle fire 2
and adb devices finds it as 0123456789abcdef
see attached pics

Ok I have been able to push a file to the fire 2 but the only file that will install is cm-10.1.3-otter2.zip
when i try to install anything else i get a error 7 and then it wont boot at all when i reboot it just goes into a loop.
would like to put cm 11 on there seems a little better

You need to update your recovery.
Sent from my Galaxy Nexus using Tapatalk

Bro you are in the wrong section. I repoted you so this thread should be in the right section soon.

Need help, Error flashing HTC one m8 stock rom

Hello friends,
I have tried downloading following ROMS RUU and each rom gives same error, whats wrong? what should I do to fix this?
roms i have tried so far
{
"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"
}
ERROR i get every time with these roms
Current ROM Version is 2.23.502, ( RUU reads 2.23.502.3 as current IMAGE version)
Hardware: m8_ul_ca
MID: 0P6B12000
Thank you for reading.

Did u chnge it to international version
Sent from my HTC One_M8 using Tapatalk

manish dubey said:
Did u chnge it to international version
Click to expand...
Click to collapse
According to his statements (on the MID and version) it appears that NO, he did not change to international version.
But I agree, we need more info to be sure. OP should do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
Or just try a different PC. RUU freezing while sending is common, and usually nothing to do with the phone. Win7 and USB 2.0 (not USB 3.0) for the best possibility for RUU to succeed.

And error 155 usually referring to bootloader not relocked when device is S-On

ckpv5 said:
And error 155 usually referring to bootloader not relocked when device is S-On
Click to expand...
Click to collapse
Ahh, I missed that. I looked at the screenshot too quickly!

hello guys,
thanks for replies,
below is more info you asked for
-- The phone is going in TWRP because previously, i tried to install a custom ROM [ i forgot which one ]
-- Phone is stuck at htc one boot splash screen
-- if i reset phone by twrp, then after it gets boot up and then i get 'UNFORTUNATE ERROR' and then again it gets restarted and get stuck in htc boot splash screen
-- i am trying to flash ruu in windows 10.1, should I try windows 7 32bit?
Thank you

You don't read what people said above.
1. you need to relock bootloader to run a RUU because you have a S-On device.
command : fastboot oem lock
then reboot bootloader/fastboot
2. run RUU while on bootloader/fastboot
What you need :
A Windows PC with USB2.0 (I never have problem running RUU on Win 10 64 bit)
Latest HTC USB drivers installed - install HTC Sync Manager as it will install the drivers and some needed Microsoft Visual C++ Redistributable files
then uninstall HTC Sync Manager but leave other things.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
You also can directly install the latest RUU - http://www.htc.com/us/support/htc-one-m8-att/news/ instead of the old version

Administr4tor said:
below is more info you asked for
Click to expand...
Click to collapse
This is not what was asked for. This doesn't tell us much we didn't already know. Aside from confirming that your bootloader is unlocked, and you are s-on.
The proper advice was already given in Post #5 above. You need to relock the bootloader with the following command, in order to RUU: fastboot oem lock

alright, sorry I didnt pay attention,
now when I try to run command "adb devices", I dont see any devices though the device is perfectly installed in windows device manager as " my htc"
also this the screen which i get when I try to turn the phone on

Administr4tor said:
now when I try to run command "adb devices", I dont see any devices though the device is perfectly installed in windows device manager as " my htc"
also this the screen which i get when I try to turn the phone on
Click to expand...
Click to collapse
You don't need to run an adb command, you need a fastboot command. Fastboot and adb are related, but very different things:
adb will never run unless in OS or recovery. What you are seeing (adb not connecting) is normal.
Fastboot commands require the phone to be in bootloader-fastboot mode (which you are in during the pic in Post #7 above).

Thank you very much, it worked, problem solv3d

Help me, nokia n1 error bootloader

Hi
My n1 can not boot up, besides not being a way to recovery . Now it's just getting fastboot , not receiving ADB ( device not found) . I can not use " ADB sideload ... " I want you to help me out of this situation . Thank you very much.

winterday said:
Hi
My n1 can not boot up, besides not being a way to recovery . Now it's just getting fastboot , not receiving ADB ( device not found) . I can not use " ADB sideload ... " I want you to help me out of this situation . Thank you very much.
Click to expand...
Click to collapse
Go to the nokia n1 general forum and click the link "Nokia n1 Rooted with Google Play" and install adb systemwide according to step 1, then download and unpack the file from step 2 and follow step 4 till 6 until you get in to clockwork recovery from there go to advanced storage and do data wipe/factory reset (this will clean the bootloop you may be experiencing and brings back the nokia n1 to its first boot) hope this helps, if not please say so and i try to help you out.

defendos said:
Go to the nokia n1 general forum and click the link "Nokia n1 Rooted with Google Play" and install adb systemwide according to step 1, then download and unpack the file from step 2 and follow step 4 till 6 until you get in to clockwork recovery from there go to advanced storage and do data wipe/factory reset (this will clean the bootloop you may be experiencing and brings back the nokia n1 to its first boot) hope this helps, if not please say so and i try to help you out.
Click to expand...
Click to collapse
Thank Defendos
I have followed your instructions, but it does not receive ADB (I type the command: adb devices), and fastboot devices are ok. Sorry for my english.

winterday said:
Thank Defendos
I have followed your instructions, but it does not receive ADB (I type the command: adb devices), and fastboot devices are ok. Sorry for my english.
Click to expand...
Click to collapse
I discovered the device can not connect "MTP usb device" ( error code 10 ) .. you can help me

winterday said:
Thank Defendos
I have followed your instructions, but it does not receive ADB (I type the command: adb devices), and fastboot devices are ok. Sorry for my english.
Click to expand...
Click to collapse
The (root) program in the guide have an automated adb (the t4 command) as the adb does not work yet with nokia n1.
---------- Post added at 12:33 AM ---------- Previous post was at 12:32 AM ----------
winterday said:
I discovered the device can not connect "MTP usb device" ( error code 10 ) .. you can help me
Click to expand...
Click to collapse
Are you in the bootloader, recovery or just normaly booted? as the device name will change according to where it is booted in i have noticed.

defendos said:
The (root) program in the guide have an automated adb (the t4 command) as the adb does not work yet with nokia n1.
---------- Post added at 12:33 AM ---------- Previous post was at 12:32 AM ----------
Are you in the bootloader, recovery or just normaly booted? as the device name will change according to where it is booted in i have noticed.
Click to expand...
Click to collapse
Dear
image of status the divice, i can't working ADB , thank 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"
}
[/URL][/IMG]
[/URL][/IMG]
[URL=http://up.ssc.vn/view.php?filename=21420160326_111403.jpg][img]
[URL=http://up.ssc.vn/view.php?filename=12720160326_112009.jpg][img]http://up.ssc.vn/images/12720160326_112009.jpg[/URL][/IMG][/IMG]
[/URL][/IMG]
[/URL][/IMG]
[/URL][/IMG]

any progress on this? I seem to have the exact same problem..

I'm in the same situation, please anybody have idea how get back the system works?
My my pc doesn't see my N1 now as mtp and camera connection has been deactivated

winterday said:
Hi
My n1 can not boot up, besides not being a way to recovery . Now it's just getting fastboot , not receiving ADB ( device not found) . I can not use " ADB sideload ... " I want you to help me out of this situation . Thank you very much.
Click to expand...
Click to collapse
I have same trouble ((

If you're in fatsboot mode adb commands are useless. You have to flash a different recovery and afterwards a different rom. I ported my N1 from A5CNB19 to A5FMB19 (taiwan version with google services) in the same way. First find out a recovery so:
fastboot flash boot recovery.img
Then
fastboot flash system system.img
And your N1 will be back with play services
You need the minimal adb and fastboot drivers installed on your pc

Hi all, I found the entrance for the brick write Whats App +79621045474

Flashed wrong kernel by mistake

Hi,
I got a little bit of a problem on my head.... I planned to flash CM12.1 on my HOX but i flashed a different boot.img by mistake! Now i cant get the phone into debugging mode and while using hasoonss toolkit it wont see my device cause i cant get it into debugging mode . Any ideas on how to solve the problem? There are a lot of threads inhere about bricked hox but i cant find one talking about the same problem....
Hope i can get some help on this.

Ow and a bit more info, i can get into bootloader and recovery.

go_insane1981 said:
Ow and a bit more info, i can get into bootloader and recovery.
Click to expand...
Click to collapse
if you can get into bootloader then just get the good boot.img and flash it using fastboot flash boot boot.img

Tried that but it won't see my device.

It doesn't apear in my devices.

go_insane1981 said:
It doesn't apear in my devices.
Click to expand...
Click to collapse
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot

ckpv5 said:
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
Click to expand...
Click to collapse
Tried both ways again but no reaction wth a list of devices. It's blank...

install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1

SÜPERUSER said:
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
Click to expand...
Click to collapse
Any options on how to install the drivers different from normally? Apparently the drivers won't install as it should install...
Have HTC sync on my system, can i use some of those exe's in there?

This is wat happens with HTC installer.

go_insane1981 said:
This is wat happens with HTC installer.
Click to expand...
Click to collapse
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
{
"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"
}
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.

Cant seem to get the drivers in my device manager, they are installed but not showing in my device manager...

SÜPERUSER said:
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Click to expand...
Click to collapse
Ok i used a old htc and now it sees my device again.

Device manager sees the HOX now too.

go_insane1981 said:
Device manager sees the HOX now too.
Click to expand...
Click to collapse
It was my thought at first. So now we know that htc apparently dropped the support for one x and older devices in their driver pack. Good to know

Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..

go_insane1981 said:
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
Click to expand...
Click to collapse
What rom are you trying to install?

SÜPERUSER said:
What rom are you trying to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521

go_insane1981 said:
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
Click to expand...
Click to collapse
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358

SÜPERUSER said:
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Click to expand...
Click to collapse
Making a new layout is something i missed, Mone said ;
Flashing instruction like usual: perform a full wipe with TWRP for new layout, flash the ROM, flash the suggested GApps, reboot into fastboot mode, flash the boot.img exctracted from the ROM.zip, reboot into system, enjoy cm-12.1.
So i wiped the damn thing( ) after making a backup offcourse(which btw doesn't help cuz its screwed...). But i completely missed that i had to make a new layout... But stil i am convinced it can be "unbricked" one way or another.
I basicly follwed all the steps mentioned in this thread; http://forum.xda-developers.com/showthread.php?t=2069904 and it al worked up to the point i flashed the wrong kernel. After that i searched the forum for hours and found some things which could be connected but with a total different view of what my problem is/was(partially solved with your help) and ended up with putting a SOS sign up for help.

device null not found

Hello,
I have a got error from Rom setup.
Recovery setup was succeeded,
but when i write "adb sideload OxygenOs3.5.5.zip" to console. I got "
loading: 'OxygenOs3.5.5.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
"
{
"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"
}

acarzeyd said:
Hello,
I have a got error from Rom setup.
Recovery setup was succeeded,
but when i write "adb sideload OxygenOs3.5.5.zip" to console. I got "
loading: 'OxygenOs3.5.5.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
"
Click to expand...
Click to collapse
it seems that the phone isn't recognized by the computer.
try "adb devices" and your device should be listed there

hellcat50 said:
it seems that the phone isn't recognized by the computer.
try "adb devices" and your device should be listed there
Click to expand...
Click to collapse
Recovery can be installed
But I can not give rum, does not see the device, do you have a driver you can suggest?

acarzeyd said:
Recovery can be installed
But I can not give rum, does not see the device, do you have a driver you can suggest?
Click to expand...
Click to collapse
try it with the ones i attached
btw your device should be booted into recovery and in sideload mode of course

hellcat50 said:
try it with the ones i attached
Click to expand...
Click to collapse
I'm trying it now, hope will not be a problem

acarzeyd said:
I'm trying it now, hope will not be a problem
Click to expand...
Click to collapse
sure. and if you have issues, you can follow this official guide provided by oneplus official

hellcat50 said:
sure. and if you have issues, you can follow this official guide provided by oneplus official
Click to expand...
Click to collapse
does not see

acarzeyd said:
does not see
Click to expand...
Click to collapse
if you use official recovery:
boot to recovery
select language
select "install from usb"
now the recovery should say "you are in sideload mode"
now type "adb devices" to check if your device is recognized by the computer
if you use twrp:
boot into recovery
on the main page, go to advanced and then adb sideload
swipe to start sideload
now type "adb devices" to check if your device is recognized by the computer

hellcat50 said:
if you use official recovery:
boot to recovery
select language
select "install from usb"
now the recovery should say "you are in sideload mode"
now type "adb devices" to check if your device is recognized by the computer
if you use twrp:
boot into recovery
on the main page, go to advanced and then adb sideload
swipe to start sideload
now type "adb devices" to check if your device is recognized by the computer
Click to expand...
Click to collapse

I try in two ways. " cannot read " gives warning

acarzeyd said:
I try in two ways. " cannot read " gives warning
Click to expand...
Click to collapse
is the filename the right one? because oos 3.5.7 isn't out yet, the newest is 3.5.5

hellcat50 said:
is the filename the right one? because oos 3.5.7 isn't out yet, the newest is 3.5.5
Click to expand...
Click to collapse
The file name is correct, I typed it incorrectly while shortening the name

acarzeyd said:
The file name is correct, I typed it incorrectly while shortening the name
Click to expand...
Click to collapse
can you check the device manager? just search in the start menu for it

hellcat50 said:
can you check the device manager? just search in the start menu for it
Click to expand...
Click to collapse
What should I look for in the device manager?

acarzeyd said:
What should I look for in the device manager?
Click to expand...
Click to collapse
under usb devices called "android"

hellcat50 said:
under usb devices called "android"
Click to expand...
Click to collapse
no android

acarzeyd said:
no android
Click to expand...
Click to collapse
please go onto "Diger aygitlar" and check there

hellcat50 said:
please go onto "Diger aygitlar" and check there
Click to expand...
Click to collapse
There is no

try this
"
I finally fixed it turns out it's windows 10 at fault. Here's how I get it to work.
1. Uninstall the Kedacom bootloader interface while phone is in bootloader. Tick delete the driver software for this device.
2. Switch to airplane mode on your PC (or disconnect wifi or your internet connection). Doing this is important as windows 10 will reinstall the Kedacom interface all over again.
3. Then unplug and replug your device. Device Manager should now show as an unidentified driver (Other devices -> Android).
4. Right click on Android and update driver software -> Browse my computer -> Let me pick -> Show all devices.
5. Once drivers are loaded, pick Google, Inc. under Manufacturer section. Click on Android Bootloader Interface.
6. Voila, fastboot devices will now detect your device.
Spread the word!
"
by ajama1
Oneplus three not recognised in fastboot mode
reddit.com