Database Info

help.

i just installed pacman rom using clockworkmod recovery something..

fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.

Jack_R1 said:
fastboot flash boot boot.img.
Google the damn thing, instead of spamming threads in all the forums.
Click to expand...
Click to collapse
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!

jigi1993 said:
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!
Click to expand...
Click to collapse
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error

Jack_R1 said:
fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.
Click to expand...
Click to collapse
jigi1993 said:
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error
Click to expand...
Click to collapse
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.

SimonTS said:
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.
Click to expand...
Click to collapse
Sir m damn serious..
i hve been googling in around 4 hrs now..
i did my best but i cant now..
please provide an easy solution..
the boot image error comes in..
i cant extract that file .

Here you go

SimonTS said:
Here you go
Click to expand...
Click to collapse
kk.

So you've installed ADB then?

SimonTS said:
So you've installed ADB then?
Click to expand...
Click to collapse
i downloaded pacman rom.
copied it into root of sd.
wiped data and installed it through clockmod recovery .!
it was installed properly but after reboot it stuck on htc white screen..

:banghead:

teadrinker said:
:banghead:
Click to expand...
Click to collapse
I couldn't agree more - I give up on this guy, if he can't even deal with what I asked then there is no hope for him.

Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege

jugg1es said:
Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege
Click to expand...
Click to collapse
Because we are too nice...
@op cd ( http://en.wikipedia.org/wiki/Cd_(command) ) in the directory where your fastboot and adb in located ( path-to/platform-tools) and fastboot commands should be working.

Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app

Jedioscuro said:
Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

jugg1es said:
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
Click to expand...
Click to collapse
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?

SimonTS said:
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?
Click to expand...
Click to collapse
Yeah, you're right. But from the disperation of the guy It seemed to me pointless to leave him with a non-functioning phone without any advise. After all this is a forum plenty of people that know how to do practically everything with an android device, but I don't think that everyone have started from a solid programming base or a perfect hardware knowledge.
Regarding me, I have looked into this forum a couple of months BEFORE even try to unlock my phone and flashing something other than the horrible desire's gingerbread stock rom, but I understand the people who wants to try something new, even if they are not so expert.
For the next time, don't worry I'll be mercyless

I'm always ready to help where i can but. It seems like the op followed half a guide then just assumed it would work, i must of read all the guides until my head hurt, and most of my first posts were silly questions already posted. I learnt far more about my phone from searching than i think i could have from my first posts
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

He would have avoided all the pain if he used the boot img flashing software
Sent from my Desire S using xda premium

how to push file to device?

So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?

flash factory image with fastboot.
Tapatalked from my Hammerhead.

Timoooo said:
So i messed around with my n5 and now it wont boot, black screen with background light on. No back up, no .zip on the phone.
Apparantly I cant mount usb my phone with TWRP(v.2.7.1) - nothing happens when I press the buttons.
ADB doesn't recognize my phone as well.
Got ideas on how to fix?
Click to expand...
Click to collapse
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396

upndwn4par said:
First off, never mess around with your device without making a backup first. If you had, this post would not be necessary.
Take a look here:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..

Timoooo said:
Yeah I learned that the hard way now...
I'm guessing the main problem is that I cant access my system to turn adb on. So I followed the steps and installed the drivers. When the phone is in bootloader and I install the drivers its now connected as Android Bootloader Interface and not recognized by adb. When I try to install the drivers in recovery mode(phone was recognized as AOSP on Hammerhead with a yellow warning triangle) it says that no driver was found..
Click to expand...
Click to collapse
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.

rootSU said:
adb works in custom recovery, not bootloader. You do not need USB debugging (this is an Android setting only) or to turn "adb on", so lets bust those myths right here
for more info, click the link to the sticky in my signature and read the "adb and fastboot, What is it?" thread, which will help you out with drivers etc too.
Click to expand...
Click to collapse
thanks got everything to work that way!

Timoooo said:
thanks got everything to work that way!
Click to expand...
Click to collapse
No problem. Cool

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!

Retard in need of Help. Weird problem with recovery of my OPO

Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking

Can post pictures of the screen if it is needed

@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.

h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.

might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone

Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.

kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD

h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem

I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on

Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.

kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing

are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.

[SOLVED] I think my I may have bricked my tablet

I had the Katkiss 5.1.1 ROM and decided to go with the KatKiss 6.0 ROM. I did a backup to an external card using TWPR. Since I was going from 5.1 to 6.0, I decided to format/data before flashing the ROM. I left the room and came back to see that my daughter reset the tablet. Now it seems to have been stuck in a boot loop similar to what happened in this thread:
https://forum.xda-developers.com/transformer-tf300t/help/softbricked-tf300t-trying-to-flash-to-t3508565
But I can't even get into the recovery. It'll get to the TEAMWIN screen and restart and it won't stop. I can't even shut it off to stop it. I've been searching for a solution and found this link:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated

the_KEV said:
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated
Click to expand...
Click to collapse
Really bad luck!
Hopefully you can reach fastboot. Then follow step by step the instruction in post #2 in the first link of your post to get back on stock rom JB 4.2. Good luck!

Am I supposed to be on a certain screen in order for me to use fastboot?

the_KEV said:
Am I supposed to be on a certain screen in order for me to use fastboot?
Click to expand...
Click to collapse
I don't know what is your knowledge in general, but the post I recommended above gives you all what you need. All erasing steps are based on "Buster99" and have been used several times successfully.
Minimal ADB & Fastboot allows your PC to communicate with your device via a DOS window on your PC. Therefore the USB driver must be installed. USB Debugging on your device must be activated. Hopefully you can start the "Fastboot USB download protocol" via "Power on"/ "Vol down" in the left corner above of the device display.

I'm sorry, I might not have been clear enough... I saw your post with the instructions, I was asking if the tablet should be on a certain screen because the only screen I can get to is where it asks if you want to boot to recovery, android or wipe data. I was wondering if this where I should be on the tablet when attempting this fix. Thanks

OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!

the_KEV said:
OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!
Click to expand...
Click to collapse
Congratulations! You are welcome!