I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/g...-erd79-frf83-superboot-rooting-the-nexus-one/
You need to download the EPF30 update, save it to your SD card as PASSIMG.zip.
http://shipped-roms.com/shipped/Passion%20(Nexus%20One)/PASSIMG_Passion_Google_WWE_1.14.1700.1_EPF30_release_signed.zip
Create a new mtd0.img file through this site
http://ks33673.kimsufi.com/misc/
I used the values, CID: 11111111 and Rom version: 0.22.997.0
Save the mtd0.img file to you PC.
Download the flash_image binary (right click, save as)
http://benocharm.lensworks.org/flash_image
Make sure it's saved as flash_image, and not flash_image.txt
If it has a Notepad icon, then it's not saved right.
With mtd0.img and flash_image in the same folder, type these commands from within that directory:
Code:
adb push flash_image /data/flash_image
adb push mtd0.img /data/mtd0.img
adb shell
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
NOTE: After flashing the MISC partition with the MTD0 from the Desire, you will notice that you have an HTC logo on your phone.
No worries, this goes away after reflashing the EPF30 Nexus One PASSIMG.zip package.
Power off your phone, then turn it on by holding VolDown and pressing Power.
It will start up in HBOOT mode and will prompt you to flash the EPF30 PASSIMG.zip update.
Once this is finished you can root the EPF30 system through Paul's superboot instructions above, then use Rom Manager from the market to apply a custom recovery again.
Now, remember not to flash the new HBOOT again.
I'd recommend flashing the 5.08 radio for the N1 through other means. Search the forum to find the instructions.
Reserved.
Thanks a lot cursordroid.
Finally I managed to downgrade my hboot.
I could save several steps as my phone is unlocked.
So I just needed to:
- make a nandroid backup
- Go through the steps of flashing mtd0.img
- Apply PASSIMG.zip file
- Through fastboot re-install a custome recovery image
- Nandroid restore
Thanks!
rommelin said:
Thanks a lot cursordroid.
Finally I managed to downgrade my hboot.
I could save several steps as my phone is unlocked.
So I just needed to:
- make a nandroid backup
- Go through the steps of flashing mtd0.img
- Apply PASSIMG.zip file
- Through fastboot re-install a custome recovery image
- Nandroid restore
Thanks!
Click to expand...
Click to collapse
That sounds like it should work, except I'm not sure fastboot accepts unsigned recovery images, you might still need to use Rom Manager to flash one.
YMMV
WTF! This can relock the bootloader?
Where is the link to the latest HBOOT?????????????
cursordroid said:
That sounds like it should work, except I'm not sure fastboot accepts unsigned recovery images, you might still need to use Rom Manager to flash one.
YMMV
Click to expand...
Click to collapse
Just did it
You can definitely flash the recovery directly from bootloader when the phone is unlocked.
I forgot to mention one extra step I took.
Delete through adb the PASSIMG.zip file from the sdcard before trying to enter in bootloader and flash the recovery.
For that, I just needed to boot the stock firmware, enable usb debugging mode and:
#adb shell rm /sdcard/PASSIMG.zip
So if I upgrade I loose root? then i root and reflash stock PASSIMG.zip with original HBOOT after flashing Desire hboot I can get stock bootloader meaning? Security gets disabled when using HTC HBoot? so i can relock my bootloader then update using PASSIMG??????????????
I dont think youve realized how happy you made everyone on this forum is you figured out you can relock the bootloader lol!
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
cursordroid said:
This only reverts your SPL/HBOOT back to 0.33.0012
Click to expand...
Click to collapse
And that's already a lot
Not being able to install or upgrade to any signed build (like recent CM 6.0) including official ones... is not funny. It's really annoying.
Going back to normal is lik
e having a new phone again
Then, what does 0.35.0017 do, if not locking the Nexus?
i'm getting an error saying incorrect cid. i actually have korean nexus one. i've been following all the steps but stuck when i try to flash the rom with passimg. big error msg saying incorrect cid. what to do now?
I can also confirm that this method worked with me. Initially screwed by the Korean ROM, but now back to the old bootloader. Thanks!!
i have tried all the method there and followed all the stuff, but it just won't let me flash passimg.zip. i keep getting cid incorrect. any solution people?
evank418 said:
i have tried all the method there and followed all the stuff, but it just won't let me flash passimg.zip. i keep getting cid incorrect. any solution people?
Click to expand...
Click to collapse
Are you using CID value: 11111111?
Yes and it didn't work. Also tried Googl001 but didn't work either. I actually do have Korean nexus one maybe that's why???? Any solution?
Sent from my HTC Legend using XDA App
@cursordroid help me
i'm a newbie, i don't know much about these, but i have installed Korean FRF91
After seeing u'r post i was happy that i could revert back now, but i don't know how to do
i have followed u'r post but i'm stuck in the middle.................
i have created that two files and downloaded EPF30 update.............
where to enter these commands
adb push flash_image /data/flash_image
adb push mtd0.img /data/mtd0.img
adb shell
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
i have windows 7..............
please help me
my emailid [email protected]
thank you
No need for the help!
I'm back to erd79
evank418 said:
Yes and it didn't work. Also tried Googl001 but didn't work either. I actually do have Korean nexus one maybe that's why???? Any solution?
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
Well, if you have a korean one, i'm not sure if there is anything different in that version.
Can you write down all the details from the bootloader screen?
What's the problem with the newer bootloader? Why even downgrade?
rommelin said:
Well, if you have a korean one, i'm not sure if there is anything different in that version.
Can you write down all the details from the bootloader screen?
Click to expand...
Click to collapse
nexusone pvt ship s-on
hboot-0.35.0017
microp-0b15
touch panel-synt0103
radio-5.00.00.04
june 14 2010,12:02:27
Related
Well I rooted my thunderbolt yesterday and today I was going to try to install a ROM but for some reason I can't do it.
I'm using rom manager. I flashed the clockworkmod recovery. Then I went to backup my current rom and the phone restarts then just goes straight to the boot loader where I only have a few options.
Hboot
Power down etc...
What am I doing wrong?
When I tried yesterday I got a little farther and went to install the rom and the same thing happened. No recovery or options to install off SD.
There is no option for recovery?
If not, go back into rom manager, settings, and check erase recovery. Then flash CM Recovery again (the top option on rom manager) and it should fix the problem for you.
Tried that:
I get HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
I go select recovery and the phone restarts briefly and I get FASTBOOT USB
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
No other options.
I would flash back to stock and root again, maybe something didn't take right the first time.
g00s3y said:
I would flash back to stock and root again, maybe something didn't take right the first time.
Click to expand...
Click to collapse
Agh really. It rooted perfectly I thought. I have root access and everything. Any other ideas before I have to go through that process again?
Maybe go to the thunderbolt chatroom on IRC and see if people can help you there. Unless someone else here knows what to do. But i never heard of a problem like that.
I think I might have figured out the problem.
After I go to install the ROM it brings me to the bootloader. Under the pink ***security warning*** I'm showing
MECHA XD SHIP S-ON
I thought S was supposed to be off? Does the root for Mac not do S off?
droidboy850 said:
I think I might have figured out the problem.
After I go to install the ROM it brings me to the bootloader. Under the pink ***security warning*** I'm showing
MECHA XD SHIP S-ON
I thought S was supposed to be off? Does the root for Mac not do S off?
Click to expand...
Click to collapse
That is not good at all I believe. You should go to the chat ASAP, I think you have to restore your system to stock and then root again. You aren't supposed to be showing the pink ***Security Warning*** and you should also be S-OFF.
EDIT: Just saw you were on a mac, I don't have one so any instructions on MAC specifics I wouldn't be able to tell you, sorry.
Any tutorials for going back to stock on a mac? I saw a regular unroot procedure but it said push the image and exploits and I'm not sure what push means. I also don't have ADB or anything on my phone so can I still do it?
droidboy850 said:
Any tutorials for going back to stock on a mac? I saw a regular unroot procedure but it said push the image and exploits and I'm not sure what push means. I also don't have ADB or anything on my phone so can I still do it?
Click to expand...
Click to collapse
ADB would be in your computer. If you used a simple root process, then you will have to learn ADB to fix your issue.
the solution is here: http://forum.xda-developers.com/showthread.php?t=1009423
and if you did the long root way, this will be easy for you.
First, download the following files: To where? The SD?
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img. What is push?
I go into terminal to do adb push misc.img /data/local/ and it says adb: command not found.
Where do the unroot files have to be? I'm still confused how I can be rooted with S on?
droidboy850 said:
I go into terminal to do adb push misc.img /data/local/ and it says adb: command not found.
Where do the unroot files have to be? I'm still confused how I can be rooted with S on?
Click to expand...
Click to collapse
if you type "adb devices" what does it tell you?
I've gotten a little farther but look what it says now:
$ su
/data/local/busybox md5sum /data/local/misc.img
Permission denied
$ c88dd947eb3b36eec90503a3525ae0de /data/local/misc.img
$ dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
/dev/block/mmcblk0p17: cannot open for write: Permission denied
Aloha everyone,
I'm currently running Innefabilis 1.0 (Gingerbread) and running DSB's Kernel (Stock but tweaked). I'm a little confused on how to update my Firmware and Radio after reading many threads in the Development Section.
Recently I flashed an ICS ROM and had the mainver error every time I tried to revert back to Gingerbread. I finally fixed the mainver error and would like to update my phone to the latest Firmware AND Radio.
As far as I've read, in order for me to update my Firmware and Radio, I have to do a NAND Backup, relock my device, install the latest update via bootloader, and unlock again and restore my ROM. Though I've seen in other threads some people didn't need to relock their devices to install the latest update.
My questions are:
1) Do I need to flash a Stock Rooted ROM before I relock my phone to do the update? Because I've removed some bloatware from my current ROM.
2) Is there an easier method to Update my Firmware and Radio on my Rooted Rezound? If so, would someone like to provide me easy steps to doing so?
Any help would be much appreciated. Thanks in advance!
Nandroid backup
Flash radios via hboot
Relock
Flash kernel for ICS. You can find it in Nils kernel thread.
Unlock
Restore amon ra recovery
Reroot via amon ra
Restore nandroid.
That is ofcourse if you mainver is below or at 2.10. If not then you have to play that game again.
That is the short and sweet version. If you need more I can lay it out again in a more detailed way later tonight.
Sent from my ADR6425LVW using xda premium
Or flash the kernel you need. Nils kernel thread explains it all.
Sent from my ADR6425LVW using xda premium
Thanks EmerikL,
I do have a couple more questions, I currently have CWM installed.
Is it okay to flash Amon Ra over CWM?
Also, can you tell me how to unlock and relock my Rezound please? LOL.
I know how to unlock via HTCDev website but unsure about locking.
Yes you can flash over CWM with Amon Ra.
In fastboot type fastboot oem lock. To unlock type fastboot oem unlock unlockrohen.bin
Sent from my VTAB1008 using xda premium
madhomey752002 said:
Aloha everyone,
I'm currently running Innefabilis 1.0 (Gingerbread) and running DSB's Kernel (Stock but tweaked). I'm a little confused on how to update my Firmware and Radio after reading many threads in the Development Section.
Recently I flashed an ICS ROM and had the mainver error every time I tried to revert back to Gingerbread. I finally fixed the mainver error and would like to update my phone to the latest Firmware AND Radio.
As far as I've read, in order for me to update my Firmware and Radio, I have to do a NAND Backup, relock my device, install the latest update via bootloader, and unlock again and restore my ROM. Though I've seen in other threads some people didn't need to relock their devices to install the latest update.
My questions are:
1) Do I need to flash a Stock Rooted ROM before I relock my phone to do the update? Because I've removed some bloatware from my current ROM.
2) Is there an easier method to Update my Firmware and Radio on my Rooted Rezound? If so, would someone like to provide me easy steps to doing so?
Any help would be much appreciated. Thanks in advance!
Click to expand...
Click to collapse
Here's a post of directions I made for someone else recently. Hope it helps.
Also, if you want to get back on Ineffabilis you can either restore a nand or flash it again without issue, then if you want to use the dsb kernel you will need to either 1) edit the android-info.txt file inside the dsb zip file or 2) flash it up to the point where it wants to "update", don't update, go to fastboot and copy out the boot.img from the dsb zip into your sdk folder and flash it from there. If you want to use Ineffabilis and the new stock kernel you'll need to flash the new kernel modules from here:
http://forum.xda-developers.com/showthread.php?t=1467793 since Ineffabilis has the old ones. *Unless they've updated the ROM, I haven't checked the last couple days.
fastboot flash boot boot.img
You'll then have to delete the PHzip file from your sd card.
Now back to getting the OTA update...
1) get the sdk working on your computer
2) On your phone, do a battery pull, then boot it into fastboot and then connect it to your computer.
3) Type the following at your computer's cmd prompt:
fastboot getvar all
and find out what mainver you are on.
* If you are on a mainver that starts with 3.x then you cannot run the RUUs. If your mainver starts with 1.x or 2.x then continue onto step 4.
4) Relock your phone by typing the following:
fastboot oem lock
5) Download the RUU for your mainver to your computer. Use the file from here that corresponds to your mainver:
http://www.filefactory.com/f/c2e320ee1d5c7886/
This is an exe file so just run it on your pc with your phone attached. I know you need to be locked, I think you need HTC Sync installed, so if it's not working search for those answers, it will work, others have done it. Now you are back to stock.
5) Unlock your phone again using the same unlock bin file you got before by putting it in the same folder you are now using for sdk. Type the following command:
fastboot flash unlocktoken Unlock_code.bin
If you don't have it obtain a new one by following the same steps you did before to get it originally. Here is a guide for that:
http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
Now you should be stock and unlocked.
6) Flash Amon Ra in fastboot. Get the lateset version, 3.13. here:
http://www.mediafire.com/?chpoxzb8bl4nn2b
Type the following command to flash it:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Now you should have Amon Ra on your phone.
7) Root your phone by installing su using Amon Ra. Go to the developer menu and find the option in there.
Now you should be stock, unlocked and rooted.
8) MAKE A NANDROID BACK UP NOW AND LABEL IT.
9) Flash a new ROM.
*** If your mainver is 3.x try this thread to see if you can come up with a method to go back to stock. I haven't looked into this since I have not ventured into ICS land as of yet.
http://forum.xda-developers.com/showthread.php?t=1459347
There are also some threads about getting back to stock from ICS I think so here are my search results for "stock ics" in the thread title and you can probably find an answer in there somewhere.
Here's another post I had made with an alternative method in it in case you have any trouble with the RUU:
ATERNATIVE METHOD:
You can also use con247's Stock OTA ROM instead of running the RUU.
http://forum.xda-developers.com/showthread.php?p=21880389
Here are the steps to take to accomplish that:
1) use Amon Ra to flash con's vigorStock OTA ROM. It will do its thing then reboot to hboot. I think it then asks you if you want to update. Don't do it yet.
2) At this point you want to relock. So go into fastboot on the phone. Using adb/fastboot type the following at the cmd prompt:
fastboot oem lock
3) Reboot phone and let it flash the PHzip file. It should reboot completely when it's finished.
4) delete the PHzip file using a file explorer app like ES File Explorer or Root Explorer.
5) get the phone back into fastboot. Unlock again using adb/fastboot. I don't remember the exact command but you can find that in the guide for unlocking.
6) reinstall su using Amon Ra.
Now you should be stock OTA rooted with the new goodies.
Check in Settings > About phone > Software info > More to see that you got all the new stuff.
Mahalo EmerikL and feralicious for your responses and help. I think I'm gonna give these instructions a shot over the weekend. The instructions you both provided were well written, now I just have to be able to actually do it without messing anything up, lol.
If I do need further assistance, I will definitely report back with my questions, lol.
Thanks,
Linda
feralicious said:
Here's a post of directions I made for someone else recently. Hope it helps.
Also, if you want to get back on Ineffabilis you can either restore a nand or flash it again without issue, then if you want to use the dsb kernel you will need to either 1) edit the android-info.txt file inside the dsb zip file or 2) flash it up to the point where it wants to "update", don't update, go to fastboot and copy out the boot.img from the dsb zip into your sdk folder and flash it from there. If you want to use Ineffabilis and the new stock kernel you'll need to flash the new kernel modules from here:
http://forum.xda-developers.com/showthread.php?t=1467793 since Ineffabilis has the old ones. *Unless they've updated the ROM, I haven't checked the last couple days.
fastboot flash boot boot.img
You'll then have to delete the PHzip file from your sd card.
Now back to getting the OTA update...
1) get the sdk working on your computer
2) On your phone, do a battery pull, then boot it into fastboot and then connect it to your computer.
3) Type the following at your computer's cmd prompt:
fastboot getvar all
and find out what mainver you are on.
* If you are on a mainver that starts with 3.x then you cannot run the RUUs. If your mainver starts with 1.x or 2.x then continue onto step 4.
4) Relock your phone by typing the following:
fastboot oem lock
5) Download the RUU for your mainver to your computer. Use the file from here that corresponds to your mainver:
http://www.filefactory.com/f/c2e320ee1d5c7886/
This is an exe file so just run it on your pc with your phone attached. I know you need to be locked, I think you need HTC Sync installed, so if it's not working search for those answers, it will work, others have done it. Now you are back to stock.
5) Unlock your phone again using the same unlock bin file you got before by putting it in the same folder you are now using for sdk. Type the following command:
fastboot flash unlocktoken Unlock_code.bin
If you don't have it obtain a new one by following the same steps you did before to get it originally. Here is a guide for that:
http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
Now you should be stock and unlocked.
6) Flash Amon Ra in fastboot. Get the lateset version, 3.13. here:
http://www.mediafire.com/?chpoxzb8bl4nn2b
Type the following command to flash it:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Now you should have Amon Ra on your phone.
7) Root your phone by installing su using Amon Ra. Go to the developer menu and find the option in there.
Now you should be stock, unlocked and rooted.
8) MAKE A NANDROID BACK UP NOW AND LABEL IT.
9) Flash a new ROM.
*** If your mainver is 3.x try this thread to see if you can come up with a method to go back to stock. I haven't looked into this since I have not ventured into ICS land as of yet.
http://forum.xda-developers.com/showthread.php?t=1459347
There are also some threads about getting back to stock from ICS I think so here are my search results for "stock ics" in the thread title and you can probably find an answer in there somewhere.
Here's another post I had made with an alternative method in it in case you have any trouble with the RUU:
ATERNATIVE METHOD:
You can also use con247's Stock OTA ROM instead of running the RUU.
http://forum.xda-developers.com/showthread.php?p=21880389
Here are the steps to take to accomplish that:
1) use Amon Ra to flash con's vigorStock OTA ROM. It will do its thing then reboot to hboot. I think it then asks you if you want to update. Don't do it yet.
2) At this point you want to relock. So go into fastboot on the phone. Using adb/fastboot type the following at the cmd prompt:
fastboot oem lock
3) Reboot phone and let it flash the PHzip file. It should reboot completely when it's finished.
4) delete the PHzip file using a file explorer app like ES File Explorer or Root Explorer.
5) get the phone back into fastboot. Unlock again using adb/fastboot. I don't remember the exact command but you can find that in the guide for unlocking.
6) reinstall su using Amon Ra.
Now you should be stock OTA rooted with the new goodies.
Check in Settings > About phone > Software info > More to see that you got all the new stuff.
Click to expand...
Click to collapse
Thank you feralicious. I'm actually gonna give this a shot today. But I have one more small question, the radio is also included in this RUU/OTA update, correct?
Another thank you for this one, this is going to be very helpful .
Sent from my ADR6425LVW using XDA App
EmerikL said:
Yes you can flash over CWM with Amon Ra.
In fastboot type fastboot oem lock. To unlock type fastboot oem unlock unlockrohen.bin
Sent from my VTAB1008 using xda premium
Click to expand...
Click to collapse
Hey emerikL,
I've already updated my radio and firmware to the latest versions. I was wondering, is it okay to still reflash Ineffabilis v1.0 with the latest update?
Yeah there isnt a pronlem with that i think. Just dont restore you nandroid over top of it. You'll need to do pretty much a clean install.
Sent from my VTAB1008 using xda premium
So I take it that I will not get to update my phone? I have the main ver 3.x.x, so that will mean the waiting game won't it?
vlen22 said:
So I take it that I will not get to update my phone? I have the main ver 3.x.x, so that will mean the waiting game won't it?
Click to expand...
Click to collapse
unless you hex your bootloader... I Downloaded the Official RUU .. locked the bootloader ran the update, unlocked... booted into android enabled debugging.. pulled that thing and changed my mainver down to 1.. sent the file back and rebooted
If your already on a mainver pass 3.602.11 (some****) then you need to find a way to flash the radio via a PH98IMG or hex your bootloader down and flash the RUU /OTA
Guess I have to deal with the stupid audio hiss then, until the real one comes out, thanks for your response.
vlen22 said:
Guess I have to deal with the stupid audio hiss then, until the real one comes out, thanks for your response.
Click to expand...
Click to collapse
No, you can get the OTA without editing your actual phone file.
There's a link to that in my lengthy post above. See the part where it says if you are on mainver 3.x, there's a link to a thread about dealing with that there. Also try searching using the terms "stock ics" and you should come up with threads about getting back to stock from 3.x mainver. I guess I forgot to paste my results in that post cuz I see I mentioned it.
Basically you need to edit a text file included in whatever package you are flashing OR you should be able to flash in fastboot without worrying about it. I successfully flashed a kernel in fastboot that had given me a mainver error when I tried to flash in recovery.
EmerikL said:
Nandroid backup
Flash radios via hboot
Relock
Flash kernel for ICS. You can find it in Nils kernel thread.
Unlock
Restore amon ra recovery
Reroot via amon ra
Restore nandroid.
That is ofcourse if you mainver is below or at 2.10. If not then you have to play that game again.
That is the short and sweet version. If you need more I can lay it out again in a more detailed way later tonight.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Sorry to post in another users topic but after I "relock" my phone wont boot it sits at white screen, adb reboot recovery just says waiting for devices and if I go to fastboot or try to open recovery I can not.
Sorry it should have been in this order:
Nandroid backup
Relock
Flash radios via hboot
Unlock
Flash kernel for ICS. You can find it in Nils kernel thread.
Restore amon ra recovery
Reroot via amon ra
Restore nandroid.
You are probably on the wrong kernel.
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Click to expand...
Click to collapse
Something I don't understand here: how were you able to run fastboot oem writecid while S-ON? Have you since gone S-ON after writing the incorrect CID?
Furthermore, why in the world would you venture from my explicit instructions on how to fix the radio? I can't imagine any reason you would want to re-lock the bootloader or go S-ON. As I keep saying: if you are already unlocked or S-OFF, I almost never see a legitimate reason to run the RUU!
I assume you still can boot into CyanogenMod? If so, follow these instructions (Windows):
Set this in CM: Settings > Developer options > Root access > Apps and ADB
Download the latest unlock script package (we will not run the script, but we do need the files there)
Extract the unlock script package and open a command window in that directory
Type these commands:
Code:
adb root
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
This should revert your CID back to VZW__001.
deleted
cyberkeeper1 said:
See I wish I could boot. I didn't understand why it accepted an oem command while s-on either. But alas, it did. I wrote that command after relocking. I am not s-off. Never was, hence my entire problem. I was afraid to try s-off because of the higher possibility of bricking my phone. It's not like the thunderbolt where it always works. If I was s-off I would know what to do and could flash hotdogs as my Cid if I wanted. My first problem is being stuck in hboot and can't restore. I wiped everything. Boot, data, system, recovery all in prep for stock since I am s-on
Click to expand...
Click to collapse
From the bootloader, what is the output this?
Code:
fastboot getvar cid
deleted
cyberkeeper1 said:
The output is:
VZW_0001
Click to expand...
Click to collapse
I can't even explain the number of ways you shot yourself in the foot. You really wiped recovery and boot too? How did you come to believe this would be a good idea? Or is necessary at all?
I believe the only option you have is to try and flash the stock signed recovery through fastboot (not even sure if it'll work), and then use ruu mode to TRY and fix things up:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
I suspect even that will complain about the incorrect CID though. Perhaps jose has some other ideas.
deleted
deleted
deleted
deleted
deleted
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
cyberkeeper1 said:
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
Click to expand...
Click to collapse
moderators, after a few replies from the users, i don't mind if you close my thread because my problem is solved.
EDIT: maybe not yet... bootlooping after fix and restore of last backup before the incident. do i have to have the Super CID written to boot from any custom rom?
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
are you rooted?
EDIT: got confused and was thinking this was a new thread sorry
jose51197 said:
you rooted?
Click to expand...
Click to collapse
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
cyberkeeper1 said:
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
Click to expand...
Click to collapse
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
i am inclined to agree based on what its doing, but wanted to be sure. i just didnt want to have to re-re unlock again. lol. i'll see what happens.
I was able to successfully flash cyanogenmod, but my phone only works for data, not for calls or texts. I assume this is because I'm still on Super CID (11111111). When I try to revert to the VZW cid, i receive an error executing the adb shell. It tells me that it's a read only file system. I'm rooted, s off, and bootloader unlocked. Any help would be greatly appreciated as my phone is only half usable right now
Don't use adb shell once you're s-off. Use these commands:
Code:
adb reboot bootloader
Once in fastboot, issue this command to revert to the VZW CID:
Code:
fastboot oem writecid VZW__001
that's it.
Sent from my Incredible 4G LTE using xda app-developers app
Thanks so much for the quick response. I knew I was overthinking it. Just applied the change, rebooting now. I'll follow up with my findings.
---------- Post added at 06:27 PM ---------- Previous post was at 06:16 PM ----------
Well, it changed the CID, but the issue still persists. If I look in about phone > status, it says my mobile phone number is 000-000-0000. I'm definitely preplexed to say the least.
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.