Develop Bugs

Stock Kernel for Primo U (CID HTC__J15)?

Hi guys,
I was wondering if anyone had the stock Kernel for the PrimoU HTC One V. If anyone does, can they supply me with it?
Thank you,
-M

Here you go...

Umm, is that what I need to revert to stock? (Kernel + Recovery?)
-M

Flashing RUU to revert to stock
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU

[Q] Can I unlock my bootloader again as I have lost the unlock code to upgrade to JB

This is what I need to do to upgrade Hboot from 1.36 to 1.79, so I would get stuck on no 4
Even with the .zip method you'll need to relock/unlock the bootloader. It's NOT flashable in
recovery. Create a new account at htcdev.
Here's how to use the zip:
1. fastboot oem lock
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip (do several times if it fails)
4. fastboot flash unlocktoken Unlock_code.bin.
Any help would be great, thanks in advance

lindsey80 said:
This is what I need to do to upgrade Hboot from 1.36 to 1.79, so I would get stuck on no 4
Even with the .zip method you'll need to relock/unlock the bootloader. It's NOT flashable in
recovery. Create a new account at htcdev.
Here's how to use the zip:
1. fastboot oem lock
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip (do several times if it fails)
4. fastboot flash unlocktoken Unlock_code.bin.
Any help would be great, thanks in advance
Click to expand...
Click to collapse
Htc sends unlock code via email, go searching old mail.
Or sign in at htcdev and follow the steps to have new unlock code.
Sent from my HTC One X using xda app-developers app

lindsey80 said:
This is what I need to do to upgrade Hboot from 1.36 to 1.79, so I would get stuck on no 4
Even with the .zip method you'll need to relock/unlock the bootloader. It's NOT flashable in
recovery. Create a new account at htcdev.
Here's how to use the zip:
1. fastboot oem lock
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip (do several times if it fails)
4. fastboot flash unlocktoken Unlock_code.bin.
Any help would be great, thanks in advance
Click to expand...
Click to collapse
Yes you can receive a lot of Unlock_token.bin from HTCDEV I take from them 3 for my phone and all of them working. Just go again in htcdev choice unlock bootloader enter with your username and pass fallow the instruction and you will receice new unlock_token.bin it is no problem to register again with the new acount and new mail and again fallow the instruction and you will receive your Unlok_token.bin

[Q] Boot loop and can't find appropriate boot.img

Hi
I've been given a One X (he bought an M8) and I thought I'd easily put on KK 4.4.4, but I have hit a brick wall.
It was running ViperX 2.6.0 with Hboot 0.95, and it's S-ON.
Well 4.4.4 needs a Hboot above 1.28, so the flashing failed.
So I did my homework and got the CID (it's HTC-023) to install the firmware so that I could update the Hboot via OTA.
So I installed the boot.img for the HTC-023 firmware and that (of course) was a an error as I didn't have a copy of the boot.img for the ViperX 2.6.0.
Then the firmware was a .rar file and didn't install anyrate.
So now it's in bootloop.
I have not been able to find a copy of ViperX 2.6.0 to extract the required boot.img
I've got TWRP with Sideloader installed, and ADB works fine.
So I am stuck (like my One X really) so any advice would be appreciated.
Thanks

Solution
I thought I should post the solution.
The essential problem was to get a Hboot 1.28 or higher so that a new version of Cyanogenmod could be installed.
On this page http://forum.xda-developers.com/showthread.php?t=1957376&page=189 is the following from ClydeB1
To flash you need to run the following commands: (It is advised to take a backup of your data and important files on your sd card)
1. Lock bootloader - fastboot oem lock
2. Boot to RUU mode - fastboot oem rebootRUU
3. Flash firmware - fastboot flash zip firmware.zip (if you get an error then rerun this command)
Note: The firmware will flash the new hboot, as well as a new stock boot.img and stock recovery.img.
To flash a custom rom you then need to do the following:
4. Unlock bootloader - fastboot flash unlocktoken Unlock_code.bin (you can use the same unlock_code file as you used previously, check your emails if you can't find it, or else reapply at htcdev.com)
5. Flash custom recovery - fastboot flash recovery nameofrecoveryfile.img
Note: If the unlock process wiped your sd card you may need to boot to recovery and mount usb storage to copy the rom file across again. If your phone won't boot into recovery then run command - fastboot erase cache and try again.
If you then wish to flash a JB custom rom:
6. Flash new boot.img from rom - fastboot flash boot boot.img
7. For good measure - fastboot erase cache
8. Boot to recovery and flash rom
I followed these steps exactly and it worked perfectly. I did need to use CWM as with TWRP the touch screen did not work.

and have more ease way to do this. You are with too low HBOOT and you can run RUU and then update the phone to latest JB because are you know witch HBoot you install to your phone

Reverting to stock to sell - best method?

I bought an M8 last year, locked to vodafone UK (CID VODAP001). I have since unlocked through HTC-DEV, S-OFFed using sunshine, converted to GPE for a while, and am now using it on a developer CID (BS_US002) entirely stock in order to get the OTA lollipop update straight from HTC. I obviously have the tampered message and unlocked bootloader, I am looking to return it to stock as much as possible (apart from S-ON). I have been looking at this thread but am not sure if it will work. I was looking to keep stock lollisense. My question is do I need to change my CID/MID back to the original ones or can I leave them as is and remove the tampered message etc.

My guide will work but there are bits that aren't needed now we have the RUU. I'll post in the morning with proper steps as I'm my phone at the mo and links are a PITA on here!

EddyOS said:
My guide will work but there are bits that aren't needed now we have the RUU. I'll post in the morning with proper steps as I'm my phone at the mo and links are a PITA on here!
Click to expand...
Click to collapse
Much appreciated! I'll check back tomorrow.

Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot

EddyOS said:
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
Click to expand...
Click to collapse
Is there any way I can use regular fastboot instead of htc_fastboot? I'm on a mac..

Nope, the Google one doesn't work for some reason. HOWEVER, apparently there is an HTC version on the HTC Dev site, which might very well work...
https://www.htcdev.com/process/legal_fastboot_mac
Failing that you'll need to use a Windows PC

EddyOS said:
Nope, the Google one doesn't work for some reason. HOWEVER, apparently there is an HTC version on the HTC Dev site, which might very well work...
link
Failing that you'll need to use a Windows PC
Click to expand...
Click to collapse
I was getting failures with remote:32 header error when usng that fastboot, managed to get on a windows PC and all sorted now. Thanks for your help!

No worries, glad I could help. I take it all the locking/tamper removing went OK as well?

EddyOS said:
No worries, glad I could help. I take it all the locking/tamper removing went OK as well?
Click to expand...
Click to collapse
Everything went to plan, all back to stock apart from S-OFF now

EddyOS said:
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
Click to expand...
Click to collapse
Hey, just did all points but how to go back to s-on and get ride of "test device" info?
EDIT: nvm, problem solved by myself. Thanks for the tutorial

[Flashing STOCK ROM from Custom Rom] [No Recovery Mode, Fastboot accessible]

I followed these steps and now my Asus zf2 (ze551ml) is back alive! For the issue mentioned below, I didn't find much anywhere so I thought I'd put here what helped me.
Issue: Only fastboot mode accessible, can't enter recovery. (Also my bootloader was locked, MM bootloader, No OS). After selecting recovery mode from bootloader, again it enters fastboot, i.e the process in video above couldn't install the recovery (This must be because my bootloader was locked). I tried unlocking the bootloader by the .bat files available on XDA but since I'd not enabled OEM unlocking, unlocking failed everytime. My OS got wiped out, so only fastboot mode was accessible.
Solution:
I believe you have installed Minimal ADB and fastboot on your PC.
Download the raw file from the XDA thread.
Now first of all, change extention of the .raw firmware file to .zip.
Then just extract all files from it into adb and fastboot folder.
Now in folder (where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
Perform the following commands one after another:
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again, if USB debugging was on then this will definitely work)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. Don't worry, first boot gonna take a little longer time.

Download raw file
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance

bb04 said:
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
Click to expand...
Click to collapse
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
FYI, I didn't add the links because one can't add external links in their first posts.

mukunds11 said:
FYI, I didn't add the links because one can't add external links in their first posts.
Click to expand...
Click to collapse
it could be better if you would have removed or edited last line while copying commands

help. my phone condition is just like this. at first when i connected my phone to computer, powershell detected it, but then after a while, my phone disappeared from powershell. can someone help me ?
edit, i just did the thing and its doing fine even though my phone look like it is not detected