Related
Hello,
I was trying to return my phone to stock, I ran a RUU (latest out there from shipped roms) which gives me a error 110 after the install. It lays down the rom it appears because if I used the ADB command "fastboot oem boot" I can actually use the phone, If I turn off the phone and turn it back on trying to boot up normal I get the HTC logo with the triangles on each side like my boot up script is screwed.
Anyone know how to fix this?
I posted this in Q&A with no response, trying here.
Hey man. I am assuming you never got any other roms to install? i still cant come up with any reason that CM6 and DC would install but not FRESH or any of the rest. Never had this issue so cant help much but hopefully someone can.
good luck
Hey guys, i am in need of some advice and was hoping someone could help me out. Im in the process of rooting my phone. I unlocked bootloader and now when i try to push the recovery i get.... " Sending Recovery 4036 kb" However it just stays on that and never actually pushes it. I have tried numerous times and was hoping someone coulld give me a quick tip. Thanks!
Are you using the command "fastboot flash recovery imagename.img"?
Try re downloading the image.
Oops. Wrong thread
Yes i am using that command. i Have re downloaded it and tried again, yet i still get the same thing.
Does "fastboot devices" give you any response?
Make sure you're in the bootloader screen.
Yes i do get a response from fastboot devices. i just tried again and it is still just saying "sending recovery" but doesnt finish. so weird.... any other ideas?
Do you see any text come up on the bottom of the phone screen?
haha i just switched to a different cable and for some strange strange reason it actually pushed and completed!!
Thanks so much for your help i appreciate it
Haha, that was going to be my next suggestion...
Yeah i cant believe that was my problem ha
Okay so I attempted to root my phone, coming from an iphone i figured this would be much like jailbreaking...but not at all.
I got stuck during root, i was using a tutorial then it failed to do anything but mess up my phone, later found out it was an old tutorial.. ever since then I have been trying to fix it with no luck.
Ive tried to re-root, unroot, nothing works because my phone takes so long to reboot itself.
My phone takes 10 minutes to boot up, then when i gets on the white HTC screen it vibrates for exactly 2 minutes. I can't press VOL down + power, it never works. When it finally boots up I have no sound whatsoever.
I've tried everything, read every tutorial, maybe im just new to this..but i cant get anything to work.
deztuhnee said:
Okay so I attempted to root my phone, coming from an iphone i figured this would be much like jailbreaking...but not at all.
I got stuck during root, i was using a tutorial then it failed to do anything but mess up my phone, later found out it was an old tutorial.. ever since then I have been trying to fix it with no luck.
Ive tried to re-root, unroot, nothing works because my phone takes so long to reboot itself.
My phone takes 10 minutes to boot up, then when i gets on the white HTC screen it vibrates for exactly 2 minutes. I can't press VOL down + power, it never works. When it finally boots up I have no sound whatsoever.
I've tried everything, read every tutorial, maybe im just new to this..but i cant get anything to work.
Click to expand...
Click to collapse
You botched up the bootloader. Go to the Ace hack kit thread and then go to the IRC. They will be able to fix you up.
Just a word to the wise. This is nothing like jailbreaking. This is alot more advanced. Doing something wrong can leave you with a brick that you cant fix or repair.
also Please post in the correct section. As this is a question it should go into the Q&A section
yeah unfortunately i learned that the hard way.
Ace Hack Kit is what i was using to try to fix my phone but since my phone takes so long to boot, i cant ever get it to work.
Can you post a link to the IRC or how to get there
deztuhnee said:
yeah unfortunately i learned that the hard way.
Ace Hack Kit is what i was using to try to fix my phone but since my phone takes so long to boot, i cant ever get it to work.
Can you post a link to the IRC or how to get there
Click to expand...
Click to collapse
Look in the hack kit thread its in the OP
I followed these commands:
wget PD98IMG-HTCUL.zip
adb reboot oem-78
fastboot flash zip PD98IMG-HTCUL.zip
fastboot reboot
and im getting stuck on fastboot flash zip PD98IMG-HTCUL.zip
it keeps saying waiting for device.
deztuhnee said:
I followed these commands:
wget PD98IMG-HTCUL.zip
adb reboot oem-78
fastboot flash zip PD98IMG-HTCUL.zip
fastboot reboot
and im getting stuck on fastboot flash zip PD98IMG-HTCUL.zip
it keeps saying waiting for device.
Click to expand...
Click to collapse
The IRC chatroom will be the quickest/best way to get you fixed. This thread will most likely get lost in a few days...give the IRC guys some time as they do have other things on their plate but I assure you once someone is in there, they will get you fixed. Attn1 and the majority of those in the IRC chatroom have seen just about everything.
Hai guis
MMM-BACONSTRIPS said:
The IRC chatroom will be the quickest/best way to get you fixed. This thread will most likely get lost in a few days...give the IRC guys some time as they do have other things on their plate but I assure you once someone is in there, they will get you fixed. Attn1 and the majority of those in the IRC chatroom have seen just about everything.
Click to expand...
Click to collapse
Weetee off with your high thanks count!
deztuhnee said:
I followed these commands:
wget PD98IMG-HTCUL.zip
adb reboot oem-78
fastboot flash zip PD98IMG-HTCUL.zip
fastboot reboot
and im getting stuck on fastboot flash zip PD98IMG-HTCUL.zip
it keeps saying waiting for device.
Click to expand...
Click to collapse
You should flash PD98IMG.zip files by putting them on the root of the sd card.
I have the exact problem.
Went to IRC and asked the guys there they told me to enter the command above:
wget http://tau.shadowchild.nl/files/PD98IMG-HTCUL.zip
adb reboot oem-78
fastboot flash zip PD98IMG-HTCUL.zip
fastboot reboot
I have tried this and right now I am stuck for 20 minutes on the HTC black screen and cmd stuck on writing zip...
Anyone have any ideea why this is? I really need to get the phone working again.
And I can not send the phone back to att becasue I live in europe
mzr9mm said:
I have the exact problem.
Went to IRC and asked the guys there they told me to enter the command above:
wget http://tau.shadowchild.nl/files/PD98IMG-HTCUL.zip
adb reboot oem-78
fastboot flash zip PD98IMG-HTCUL.zip
fastboot reboot
I have tried this and right now I am stuck for 20 minutes on the HTC black screen and cmd stuck on writing zip...
Anyone have any ideea why this is? I really need to get the phone working again.
And I can not send the phone back to att becasue I live in europe
Click to expand...
Click to collapse
Go back to the IRC Channel. It will the best option for a fast answer, the guys there have seen almost everything.
Well, I fear I may have completely buggered myself this time...
I unlocked using HTC Dev, and then followed: http://forum.xda-developers.com/showthread.php?p=26181347#post26181347 to root my device, which worked perfectly, big thanks to the guy for taking the time to sorting that out!
Now, Billy big balls here thought he was an expert because he'd done it once, and now thought he could install a custom rom, and, I can't load past my network providers screen. I think, with hindsight, I should have asked if it was compatible, my, HBOOT is 2.00(blah), which I fear may have been where I went wrong...
Now, I've got nothing on my memory card, I tried to clear the data, like some videos said we should do. But, it didn't work. So, I've took the memory card out, put it in another device, and put Fastboot and dll file, as well as the .Zip I used when I first rooted the device, and nothing. Still can't get passed the network providers screen.
I was wondering if you guys could help me out, but do it in very newbie and clear steps! (I am a bit slow)
Many thanks in advance guys!
Did you flash the boot.img separately?
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
Have you flashed the kernel?
fastboot flash boot <path to boot.img>/boot.img
Yeah - What he said :O
Can you still access the bootloader? Volume down + power
Firstly, thanks for the speedy responses.
Secondly, I have no idea what you guys are saying... What does all this mean?
But yeah, Dan-Fish, I can still access that menu, and I can still go into recovery mode!
OK
Now go to boot loader
Select fastboot using your volume keys
Hit power to get into fastboot mode
Connect to PC
Type
fastboot devices
Your phone should be listed here
Then extract the boot.img from the ROM's zip that you flashed
Fire the command
fastboot flash boot <path to boot.img>/boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
Because you unlocked with HTC DEV you need to make sure that you flash the correct kernel separately from the ROM. Have a look at this http://forum.xda-developers.com/showthread.php?p=19071114#post19071114
Right, I've finally managed to get that done, Suku_Patel, and thus far, it has loaded further than it has before, I am aware that it takes some time, for first boot especially, so, I'll give it a chance. As I speak, it's loaded up.
It's gone through set up, and it works! Many, many, many thanks for your help with this!
A afterthought, read the guides, can't count the number of times I have swyped the fastboot command.....
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
So, after the initial problems, and following the steps, it all worked perfectly, however...
I didn't like the ROM I was using, it kept cutting the volume in calls, and the camera didn't work, etc. Titanium back-up also did not register that it was rooted, so, I want to change the ROM.
I've got the ROM that I want, and I thought I'd done it right... Cleared all the data, etc. Again, I'm stuck on the loading screen. It gets past the vendor screen, but, fails to boot completely.
Is there any advice/help that you guys can offer me?
Many thanks in advance.
Repeat the steps for boot.img
Sent from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!
I'm pretty sure I have, I've:
Extracted the .img on the SD card, with the .Zip there,
Shut down the phone, started it in Fastboot, USB connected
Opened CMD prompt: Fastboot Flash Boot Boot.img
Done that, then restarted it with the ROM installed
Then it just gets stuck after my service provider, on the what would be 'HTC screen'. And fails to boot. I am a quite patient man, and I am aware that it may take a while, but, it's been on this for an age!
You need to extract boot.img to your PC, not to SD card. You're flashing from PC!
Why can't people follow the guides...
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?
gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
The phone is stuck I a startup loop. I can’t enter recovery mode but I can come in to fastboot mode. When I use the command “fastboot oem device-info” I can see that the bootloader is tempered but not unlocked. It seems that I cant unlock it. Because when I use the command “fastboot oem unluck” the phone just reboot into a new loop. Under “Unlocking the device” stage 7 is says “A disclaimer will display on the device that must be accepted.” That never happens with my phone.
wiki.cyanogenmod.org/w/Install_CM_for_bacon
What can I do!?
Click to expand...
Click to collapse
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful
playya said:
I see this is you first post here in xda and wish it was a better one than this but there are threads on how to fix your issue. May I suggest in the future you do a little more research prior to doing anything with your expensive phones. Sorry to sound like an ass but I see this happen so often. Now to help you out
1 Download all the fastboot images for your phone and flash each other to restore your phone to stock http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
2 Here is the thread you should of read and used prior to doing anything http://forum.xda-developers.com/showthread.php?t=2788632
Good luck and be careful
Click to expand...
Click to collapse
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?
gunvald89 said:
After a bad root-attempt it seems that my bootloader is damaged. It happens when I used Oneplus One toolkit 1.6. I need help!
Click to expand...
Click to collapse
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.
mbudden said:
This is what happens when you use "toolkits".
It's much easier to learn what you should do vs clicking a button or hitting "1" on your keyboard.
Click to expand...
Click to collapse
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon
http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909 is a good read.
timmaaa said:
^^^This
While toolkits may seem like they make things easier, they're not always reliable, and they allow the user to skip over some really crucial learning experience from doing things manually.
Transmitted via Bacon
Click to expand...
Click to collapse
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.
abcarter said:
Try reading this thread http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I'm not entirely sure what is going on in the thread. It says toggle, so maybe you could toggle the tamper bit closes and try to unlock again.
It would also be possible to boot the recovery without loading it on the phone.
This uses the command "fastboot boot recovery.img" rather than flash. Then from there you could use TWRP's recover to to play with stuff.
Click to expand...
Click to collapse
Thanks for your replay! I’m looking in to this now
gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.
I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.
gunvald89 said:
To replay to the several message that is wrong to use toolkit. I understand you all and obviously now with results to hand it is obvious that it wasn’t the best thing to do. With my prior phone SGS3 I first did everything the manual way and then I was spoiled with a wonderful toolkit from the xda moderator, mskip, that did everything I did but faster.
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Nobody is kicking you when you're down, just providing good information for people to learn from.
Transmitted via Bacon
I really hope that you will find your solution mate...Just read here and there and be confident.
Anyways, this is my second experience with phone rooting (prior my OPO i had a SGS4) and at the moment of rooting the phone i did not trust all these toolkits, i just dont feel safe using commands written by other people.
I guess i was right...
Best of luck!
gunvald89 said:
Please don’t kick a man when he’s down. If someone have any idea to fix this then please write here.
Click to expand...
Click to collapse
Who's kicking you when you're down?
We're just replying just in case someone else comes by this thread and doesn't understand the risks of "toolkits".
Just because something is faster, doesn't mean it's the best route.
Just like the toll on the highway. Faster but gonna cost you in the end.
[armitage] said:
I'm sure it is just a typo, but as you spelled it several times in this thread like this I just have to ask.
You're not actually typing "fastboot oem unluck" when trying to unlock your phone, are you? :silly:
Cause that would kinda explain why you're so unlocky with it.
Click to expand...
Click to collapse
Hehe that right my spelling is quite bad. Unfortunately that was not the problem here even if my spelling in this thread is really bad… Have to start reading more books or something
Following this guide right now
https://forums.oneplus.net/threads/install-adb-drivers-for-windows-8-1-64-bits.51264/
abcarter said:
On further reading, It seems you'd push the zip to reset the tamper flag:
adb push FILENAME.zip /sdcard/
Then you'd boot TWRP
"fastboot boot recover.img"
Then you'd flash the file.
I've not used this personally, I have booted a recovery through adb, which is how I rooted my phone without unlocking the bootloader.
Click to expand...
Click to collapse
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else
gunvald89 said:
Fist of. Thanks for all your help!
I am trying to push it but now it seems that my mobile isn’t correctly connected. When I run adb devices my phone doesn’t come up the list. It has been there before but I believe I have to fix this before anything else
Click to expand...
Click to collapse
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.
Well done....
The first person who bricked the Opo, writing three lines of code...
Dont know how is that possible
gunvald89 said:
Yes you are absolutely right. I should have read more before trying to root it. What is done is done and now I try to learn from my misstates and save my phone from the garbage can. All help is very appreciated!
Regarding your links, they were unfortunately not helpful in my case. As every other guide I have read they all assume that the bootloader is unlocked or that is possible to unlock it with the “fastboot oem unluck” command. Which in my case seems impossible/hard to do. The question is why I can’t unlock the bootloader or/and how can it be done?
Click to expand...
Click to collapse
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip
DuckMcQUack said:
Download this: theyre the drivers for USB from Google.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Then unpack the file and go into Hardware manager. Right click on your android device connected with USB and select upgrade drivers. Select the folder that you previously unpacked and select ADB drivers.
Do the same but in this case for Fastboot-bootloader driver version if you cant find your fastboot device after rebooting into bootloader via ADB.
It's not fully detailed as a guide but if you're at least a minimum used to manage peripherals in windows you will not have any problem in using the drivers.
Click to expand...
Click to collapse
Thanks your suggestion. I tried that and is just says that I have the same driver installed. Also tried to uninstall every driver that has anything to do with google android and phones and then reinstall. I also tied to install from my Android SDK folder but I got the same message.
playya said:
The guide I provided does not require you to have a unlocked bootloader. This is to restore phone to 100% stock and is done in fastboot with fastboot commands. Are you sure you read it right
Straight from Cyanogen themselves right here
Code:
Instructions:
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
Download the file cm-11.0-XNPH25R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update cm-11.0-XNPH25R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
Oh nice. I will try that after i get the drivers up and running!