I have a rooted MT4GS w/ the Revolutionary bootloader. I noticed that running
fastboot oem ?
Click to expand...
Click to collapse
brings up the list of commands that can be run.
(bootloader) command list
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) mw
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
Click to expand...
Click to collapse
Coming from the G2, I know that a couple of commands are missing. I'm most concerned with this command
fastboot oem emapiWlanMac
Click to expand...
Click to collapse
so that I can mac spoof in order to use my university's wifi.
If I have a copy of HBOOT 1.44.0006, obtained using
dd if=/dev/block/mmcblk0p? of=/sdcard/hboot.img
Click to expand...
Click to collapse
and I have S-OFF (via unrevoked), do you think I can switch to the HBOOT 1.44.0006 using the inverse of the previous dd command? And if so, does anybody know the mmcblk0p? number or have a copy of that specific HBOOT version?
Thanks in advance
i wonder if you could flash that HBOOT by using this stock RUU for our device?
http://forum.xda-developers.com/showthread.php?t=1178082
IF you have the .0006 HBOOT in the proper format, i bet you could delete everything in the RUU zip except perhaps the android_info.txt, then paste in the copy that you have of the HBOOT. this is basically what i did to flash ClockworkMod thru the bootloader. you could always test it by renaming it PG59IMG.zip, putting it on the root of your sdcard and booting into the bootloader. you could see if it reads the file properly and prompts you to update(it should show that you will only be 'updating' the HBOOT). if it does this and you're brave, you could try updating.
not sure if this is what you mean or not also not positive if this is the way to do it. but the RUU definitely does flash an HBOOT, so if you have it in the proper format, maybe it could work?
I messed up a little with strings (1) and file (1). Apparently hboot is stored in /dev/block/mmcblk0p12. If you feel really adventurous you can try to flash a new hboot via dd as you suggested.
I am not 100% sure it will help you: revolutionary hboot (1.44.1107) contains some reference to emapiWlanMac even if it gives an error if you try to use the command.
---------- Post added at 03:29 PM ---------- Previous post was at 02:36 PM ----------
question: where have you got 1.44.0006 ???
I just compared 1.44.0007 (the original hboot) with 1.44.1107 (revolutionary's). They are almost identical: I guess they simply hexedited the significant bits to unlock it (they also changed version number and added the "-Revolutionary-" signature) so none of them will help you change your mac address.
Hboot 1.45.0013 (the latest hboot) is a significantly different beast and might have the desired features but I would not flash it since it will lock your phone again.
I'm down to try the dd command, but I'll still need a copy of the 1.44.0006 hboot. If anybody has the 1.44.0006 hboot, can you please open a terminal and run
dd if=/dev/block/mmcblk0p12 of=/data/local/tmp/hboot.img
mv /data/local/tmp/hboot.img /sdcard/
Click to expand...
Click to collapse
Then send me the file on you sdcard?
Etn40ff said:
I messed up a little with strings (1) and file (1). Apparently hboot is stored in /dev/block/mmcblk0p12. If you feel really adventurous you can try to flash a new hboot via dd as you suggested.
I am not 100% sure it will help you: revolutionary hboot (1.44.1107) contains some reference to emapiWlanMac even if it gives an error if you try to use the command.
---------- Post added at 03:29 PM ---------- Previous post was at 02:36 PM ----------
question: where have you got 1.44.0006 ???
I just compared 1.44.0007 (the original hboot) with 1.44.1107 (revolutionary's). They are almost identical: I guess they simply hexedited the significant bits to unlock it (they also changed version number and added the "-Revolutionary-" signature) so none of them will help you change your mac address.
Hboot 1.45.0013 (the latest hboot) is a significantly different beast and might have the desired features but I would not flash it since it will lock your phone again.
Click to expand...
Click to collapse
I know that HTC's engineering bootloader enables the use of more "fastboot oem xxx" commands, and many of them are missing with revolutionary's bootlaoder
at least these 2 guys had 1.44.0006 sometime in the past
daniel60104 and nyolsson
try to pm them and see if they can help (I'd love an ENG bootloader).
Man, me too. I'd love a copy of that to play with.
I just PM'd them now. I hope we can still find a copy, at least for reference sake, since there no XDA Wiki entry for the MT4G yet
Sent from my HTC myTouch_4G_Slide using xda premium
yogi2010 said:
i wonder if you could flash that HBOOT by using this stock RUU for our device?
http://forum.xda-developers.com/showthread.php?t=1178082
IF you have the .0006 HBOOT in the proper format, i bet you could delete everything in the RUU zip except perhaps the android_info.txt, then paste in the copy that you have of the HBOOT. this is basically what i did to flash ClockworkMod thru the bootloader. you could always test it by renaming it PG59IMG.zip, putting it on the root of your sdcard and booting into the bootloader. you could see if it reads the file properly and prompts you to update(it should show that you will only be 'updating' the HBOOT). if it does this and you're brave, you could try updating.
not sure if this is what you mean or not also not positive if this is the way to do it. but the RUU definitely does flash an HBOOT, so if you have it in the proper format, maybe it could work?
Click to expand...
Click to collapse
i jsut tested this theory and it does work. when i had a custom recovery and custom rom, my hboot was 1.44.1107. when i reflashed the stock rom posted in these forums, it reverted to 1.44.0007.
But its still S-OFF no?
Sent from my myTouch_4G_Slide using xda premium
It should still be S-OFF after having done that, that's the result I always end up with.
If it somehow magically went back to S-ON, a whole lot of people (myself included) will be dying to know what happened and how to do it again.
yep, so far S-OFF has been a key safety valve that no one has managed to lose once they had it, whether downgrading or updating
thrice43 said:
But its still S-OFF no?
Sent from my myTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
It IS, in fact, still s off. Pretty sure that's been determined as passing the point of no return, once you turn it off.
Sent from my myTouch_4G_Slide using XDA App
We would know for sure if its truly the "point of no return" if somebody can grab ahold of that ENG_Hboot 1.44.0006. As with 1.44.0007 or any other hboot, I know the S-off status is irreversible.
Sent from my myTouch_4G_Slide using xda premium
Upon running dd if=S-OnHboot of=mmcblk0p12, then m5sum check, it seems that mmcblk012 cannot be written to. Therefore, I believe its safe to assume write protection is still enabled for select partitions, even though revolutionary claims otherwise.
Anybody know a workaround? I found a kernel module that's compiled for htc vision, called wpthis.ko, that enables writing to hboot partition but it wouldnt work cuz its not for mt4gs.
Sent from my myTouch_4G_Slide using xda premium
like i was saying before, if you had a copy of it, couldn't you just flash it thru the HBOOT itself as a PG59IMG.zip? when you flash the full factory firmware that way, it changes you back to the stock HBOOT, but still S-OFF of course.
yogi2010 said:
like i was saying before, if you had a copy of it, couldn't you just flash it thru the HBOOT itself as a PG59IMG.zip? when you flash the full factory firmware that way, it changes you back to the stock HBOOT, but still S-OFF of course.
Click to expand...
Click to collapse
This is most likely what you'll have to do to get it on - making a copy of what's there should be no problem.
To my understanding, the kernel prevents you from writing outside of a certain memory range unless you are in fastboot mode or flashing a failsafe-recovery (PG59...)
This is why I was unable to include a bootsplash as part of what changed when you flashed my ROM - I wasted a solid day of development pre-release trying to figure out how to get it to flash the boot splash as well when you flashed the ROM.
In fastboot or using a failsafe-recovery image, it happens before any higher-level software (kernel ...cough...cough) starts up and you aren't held to that limitation.
Edit -
re-writing the software to allow you to flash things out of the safe memory range in recovery mode would be a disastrously bad idea. We will start getting reports of bricked phones left and right if someone does that.
The obvious (since it was not mentioned yet):
Code:
fastboot erase hboot
fastboot flash hboot hboot.img
The only issue here might be that the new hboot has no fastboot in it so you may nit be able to revert using the same flashing metod.
Why not just flash the whole stock rom image? It includes the hboot
Sent from my myTouch_4G_Slide using XDA App
he's looking for the stock ENG HBOOT, which very few people have had.
but here is another guy who did have it: http://forum.xda-developers.com/showthread.php?t=1330617
yogi2010 said:
he's looking for the stock ENG HBOOT, which very few people have had.
but here is another guy who did have it: http://forum.xda-developers.com/showthread.php?t=1330617
Click to expand...
Click to collapse
Beautiful. Thanks yogi!
Sent from my myTouch_4G_Slide using XDA App
Related
I believe I may have bricked my Desire S also.
I rooted my Desire S through the official HTC method. (I have since relocked)
I then attempted to flash a custom ROM.
The custom ROM (Reaper 2.2) got stuck in (what I believe to be a boot loop) so I attempted to revert to the backup I made - that failed.
I did manage to get CyanogenMod 7 working but with missing functionality
Now I could not get beyond the white HTC screen (or the Black screen with the circle/number pattern on Reaper)
My desire S originally was on Vodafone (Ireland)
Whem I try to load the error is:
SD Checking
Loading...[PG88DIAG.zip]
No image!
Loading...[PG88DIAG.nbh]
No image or wrong image!
Loding...[PG88IMG.zip]
No image!
Loading...[PG88IMG.nbh]
No image or wrong image!
My phone was on 2.3.5 and Sense 3.0
Other details I obtained:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.161.3
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei:xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
I have spent hours upon hours trawling through forums, posts and guides but nothing has worked.
I have tried RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed.exe and got error [170]:device not detected and I have tried from the command line via fastboot....
I really need help here please.
OR is my Desire S totally bricked beyond repair
If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.
eyahl said:
If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.
Click to expand...
Click to collapse
this and bootloader need to be ****unlocked**** in order to boot custom rom, and ***re-locked*** when installing RUU
Thanks for the reply's guys.
I managed to get the RUU working this evening but the phone was still ***unlocked***... I got some error (didn't make note of it)
I will re-read both posts when I am not so tired and try the suggestions
Thanks again
(I will post my results)
Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom
GSR-James said:
Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom
Click to expand...
Click to collapse
Did you read what I wrote?? Do what I said or search forum about that if you need more information. It is definitely necessary, you won't succeed without flashing boot.img separately.
Sent by my fingers to your head.
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
Yes, that's what I meant
Sent by my fingers to your head.
GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
YEs that sounds about right, although the full command is
Code:
fastboot flash boot boot.img
Thank you both for the reply's.
I will try this when I sober up in the morning
Now that I am sober I want to thank eyahl, nenad_l and ben_pyett for your input.
I managed to get the rom working last night (drunk and all as I was )
I am now running a MIUI rom
Baseband version: 20.4801.30.0822U_3822.10.08.04_M
I need to ask a couple more questions if I may?
The interface is not what I am used to and don't particularly like it. It reminds me of the UI I had on my old Galaxy I9000. Is this as a result of my kernel version?
Kernel version: [email protected]#1 Thur Oct 6 14:48:57 BST 2011
My understanding of what I have done by flashing the boot.img is that my kernel is that of the rom from where the boot.img was taken and the MIUI rom sits atop - is this correct?
So if I extract a boot.img from a different rom and then flash I will have a different kernel version and subsequently return my UI to (SENSE) that I'm more familiar to?
Sorry for the n00b questions but I am only learning about this at the moment
Thanks guys
No problem, and your understanding is not really correct, the UI is determined by the ROM not the boot image (which is ultimately the kernel), so to get sense back you need to flash a sense ROM like Endy
Every time you flash a new ROM simply flash the associated boot
You shouldn't flash a boot from one ROM under another, it's not mix and match, well that's not completely true.
Swyped form ym Dersie S unsig XAD Permuim
Thanks Ben.
I will look for the 'Endy' rom you suggested.
Ok, so I dl the zip, extract the boot.img, write it from cmd and then flash the rom like normal?
I find it very frustrating to find roms.....almost every time I select a rom to dl I'm redirected to a bad link or to a referral to another referral etc....
If anyone has a source for roms please post it!
Best source for roms is the development section here at desire s xda. Just look through the threads, you will find good quality and stable roms. Endy=endymion ROM
You can look to the index thread, additionally zac made a torrent thread where you can find torrents for the most used roms
Sent by my fingers to your head.
Thanks eyahl
I have dl Endy and will try it now.
I'll have a look where you suggested
Thanks
You must wipe your device (all partitions except sd) prior to each ROM flash
Swyped form ym Dersie S unsig XAD Permuim
Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again
GSR-James said:
Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again
Click to expand...
Click to collapse
You're welcome
Yes, you can mark the thread solved
Sent by my fingers to your head.
Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!
GSR-James said:
Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!
Click to expand...
Click to collapse
Go to your first post, click EDIT, then on the edit panel, click on ADVANCED and then modify the topic of your thread by adding [SOLVED] in front of it.
You're done.
Hello!
Just got my hands on a desire S from someone who said they bricked it, i dont think it is though.
I can access fastboot/HBOOT but it doesnt seem to have a custom recovery installed, shows the stock recovery or download mode logo, the screen goes blank and vibrates 7 times.
Every time i try to flash anything through fastboot it gives me the error in the heading
FAILED (remote: not allowed)
The ROM just doesnt boot and shows T mobile logo indefinitely (must be a bootloop) but the phone doesnt have any Tmo logos on the body.
more details
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
I read about ENG S-off but i dont know what this phone has, maybe its just radio S-OFF cos its Tmo and doesnt have a recovery though i dont understand what the 7 vibrates mean either.
little help please?
even more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.110.3
(bootloader) serialno: HT15TTJ01262
(bootloader) imei: 356708041646975
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0e35ea5b
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
7 vibrations most likely mean overheating, and this can't be cured by any means.
The phone is S-OFF, but doesn't have Engineering HBOOT - so you can't use fastboot, it won't allow you (just what it says).
Your best bet is to try a stock RUU and see if it helps.
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Tectas said:
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
raheeljessa said:
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
Click to expand...
Click to collapse
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot
Tectas said:
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot
Ok then try it with a ruu, sry that i took your time for nothing
Tectas said:
Ok then try it with a ruu, sry that i took your time for nothing
Click to expand...
Click to collapse
how do i do that? sorry i seem to know nothing
Do you know from which regions your phone is?
Try in fastboot : fastboot getvar all, and Google your main version then download the appropriate file from this link
http://forum.xda-developers.com/showthread.php?t=1002506
Once you are sure you have the right RUU, you might have to make a goldcard to get rid of the CID error
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Jack_R1 said:
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Click to expand...
Click to collapse
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
raheeljessa said:
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
Click to expand...
Click to collapse
3 possibilities:
1. Let the ruu run without attached device till the only option is to close the program, search in your temp folder for the rom.zip, copy it to another folder, close the program, copy it to sd and try to flash it the same way you did before with the hboot (rename the rom.zip to PG88IMG.zip before you flash it)
2. Do the same like at 1. but create a goldcard before
3. Do the same I described before with hboot, but create a goldcard before
Swyped because PC is under full load or to far away
If the RUU installer hangs - your chances aren't too good.
If it hangs on "rebooting to bootloader" - boot to FASTBOOT manually and start RUU while in fastboot mode.
If it hangs updating - chances are you're another case of faulty eMMC.
gave the phone to some guy in the market. says he'll take 5£ to open it and check it out and let me know whats wrong.
the RUU rom.zip file when renamed to pg88img.zip or whatever does work as its the only zip file it detects in hboot mode,
it starts the update, heats up like an angry mountain and then sucks its battery off..
thanks you guys for all the help. I'll update you on what was the actual problem when this guy tells me so you know what these symptoms are for in future
Have you tried using the gold card? As it has already been stated that it should get rid of the wrong cid issue.
Sent from my HTC Desire S using XDA
Hello, after looking into my problem all night (it is 4 a.m. now) I still cannot get my One X out of its issue.
Background to this story:
Bought this phone from a friend who had TWRP2 as the recovery, unlocked, s-on, supercid. I wanted to upgrade to a newer ROM, specifically Carbon on Jellybean 4.2.2, and I needed to update hboot to accept the newer ROM. Follow the procedures of multiple threads and they all lead me down the same path of re-locking your bootloader and let the install do the rest. However, the installer has failed multiple times (error codes 140 and 158) and I am now stuck and have no idea where to go next.
The current status of the One X is not to great. It now has a relocked bootloader, HBOOT version of 2.14.0000, A broken recovery, what seems to be a mismatched baseband, Stuck at FASTBOOT USB, no ADB, will not boot into a ROM, RUU will not complete its job (fails at sending ROM), and I am all out energy and grammar.
*Trying to re-unlock the bootloader via HTCdev will NOT unlock it.
I am stuck, (yea I am a noob). If you need anymore info, just ask.
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Flashing the stock recovery only really applies when you're trying to take an OTA, it isn't required for an RUU.
Sent from my Evita
whoooops just kidding then. might worth a shot to give it a try though? I was just tossing out ideas.
brotherross said:
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
I am not exactly sure how to do that.
I honestly don't think that's going to help you anyway.
Sent from my Evita
timmaaa said:
I honestly don't think that's going to help you anyway.
Sent from my Evita
Click to expand...
Click to collapse
Alright, gonna need to fix it later. (Recovery still broken, I assume because of the failed RUU)
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
brotherross said:
After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
redpoint73 said:
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
Click to expand...
Click to collapse
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Anytype of backup was made on the phone with TWRP, if TWRP still exists on the phone, it should be there.
I have not tried flashing TWRP back. I can try that next, can you point me in the right direction? Which version of TWRP do you recommend? (I am a noob)
"With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot." I am not aware of this, (again, noob) do I just extract the boot.img from the zip and use 'fastboot flash boot boot.img' ?
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
timmaaa said:
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
Click to expand...
Click to collapse
I may need to reiterate, that my bootloader is still locked.
MDAWG25 said:
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Click to expand...
Click to collapse
This is why you are getting errors 140 and 158. As timmaaa mentioned, you can't run an older RUU than the hboot that is already on your phone. The RUU you stated is very old, the 1.73 firmware with 1.09 hboot that came out at the phone's release. You are on hboot 2.14, so once the RUU sees that your hboot version is greater than that of the RUU (1.09), it fails.
Thye 3.18 RUU (which comes with hboot 2.14) would be what you want. BUT as already mentioned, you should not run this with S-on and SuperCID, as there is a bug with the Jellybean RUUs where this combo will brick the phone (not fixable without JTAG or new motherboard).
Follow timmaaa's steps in the previous post.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
You might be in a catch-22 here then. As you know, you can't install custom recovery with a relocked bootloader (and S-on). You can keep trying to unlock it, but I'm not sure if that can be done if the phone can't boot.
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
Sorry, I missed that. As Redpoint said above, you might be in a catch 22 situation here unfortunately.
Sent from my Evita
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
redpoint73 said:
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
Click to expand...
Click to collapse
I am currently not home to interface with the device physically (RDP). I should be returning around 4PM EST.
The superCID was written by the previous owner. Writing a generic CID (like HTC_001) is not an option with s-on, is it?
*Are there any RUUs that won't brick when flashing?
<Sorry for the double post but this post is different then my last>
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
MDAWG25 said:
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
Click to expand...
Click to collapse
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
timmaaa said:
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
Click to expand...
Click to collapse
Fastboot claims it wrote the recovery image, it just failed the signature check, unless it reverted, should it still be there?
I am not home to try it. I am RDPing to my computer at home, which the phone is connected to. I should be home at 4PM EST (4 hours from now).
Here is a 'getvar all'
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT246*********** (omitted for privacy)
(bootloader) imei: 359****************** (omitted for privacy)
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
See anything out of the usual?
Being able to unlock the bootloader will solve all my issues, I should be able to try again when I get home.
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
timmaaa said:
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
I won't post again until 4pm est, as I do not have full access to the device.
Thank you for your help, I really do appreciate it.
I decided to write this, even though it was already written by SO many people already, to have it in an easily accessible spot
YOU MUST ALSO BE SUPERCID!!
YOU MUST BE S-OFF!!!!!!! http://forum.xda-developers.com/showthread.php?t=2155071
So here we go!
2.15 Firmware: http://www.androidfilehost.com/?fid=23060877490004040
2.18 Firmware: https://www.androidfilehost.com/?fid=23329332407572084
Download the firmware zip. Put it in a folder where you have the fastboot sdk tool
Plug your phone in with USB Debugging
Reboot into bootloader:
adb reboot bootloader
Click to expand...
Click to collapse
Open a command window in the folder with fastboot sdk
Once the phone gets to bootloader, go into fastboot
Check if fastboot commands are working:
fastboot devices
Click to expand...
Click to collapse
Now the fun starts:
fastboot oem rebootRUU
fastboot flash zip <WhateverYouCalledYourFirmwareZip.zip>
Click to expand...
Click to collapse
if it shows FAILED (remote: 90 hboot pre-update! please flush image again immediately)":
fastboot flash zip <WhateverYouCalledYourFirmwareZip.zip>
Click to expand...
Click to collapse
If it ends with "INFO..... OK", reboot to the bootloader:
fastboot reboot-bootloader
Click to expand...
Click to collapse
Verify everything was successful by running:
fastboot getvar all
Click to expand...
Click to collapse
This is what you're supposed to see:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000 (2.18.0000 if you used the 2.18 zip)
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2 (5.18.xxx.x if you used 2.18 zip)
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android:
fastboot reboot
Click to expand...
Click to collapse
Reboot into Recovery:
fastboot reboot-recovery
Click to expand...
Click to collapse
Thanks to Turge and everyone else who helped with this firmware and Sense 5
Thanks @24ky for 2.18 firmware zip
CLICK THANKS IF I HELPED!!!!!!
I might be wrong, but this probably belongs in the General section as it isn't your own development.
Sent from my Evita
Moved to General.
Yeah sorry guys. Was in a rush to create this between classes and wasn't paying attention to the section.
Sent from my HTC One XL using XDA Premium 4 mobile app
Worked fine
I saw this in other threads but used this one since it was right there at the top. Everything went fine, thanks
Madcat8686 said:
I saw this in other threads but used this one since it was right there at the top. Everything went fine, thanks
Click to expand...
Click to collapse
can you do update to firmware 2.15 with S-ON and no SuperCID (it's still Roger001)?
cause I'm getting lost connection and random reboots with Viper XL 4.2.0
I tried Beastmode kernel but WiFi stopped working..
No you can't. Maybe it's time you got SuperCID and s-off, it's a good thing to have anyway.
Sent from my Evita
timmaaa said:
No you can't. Maybe it's time you got SuperCID and s-off, it's a good thing to have anyway.
Sent from my Evita
Click to expand...
Click to collapse
believe me I want to!
but I'm not sure how to do it yet.
(chicken-egg situation, lol)
I've read conflicting things, like you have to have SuperCID first before you S-off..
but then I read that you need to S-off first
which one is it?
If you can't read and understand the instructions in the S-OFF thread you are not ready
Sent from my HTC One XL
Get s-off before they patch it in the next update. Besides, you can fully customize your systems with kernels easily
Did I mention no fastboot commands?
Sent from my HTC One XL using XDA Premium 4 mobile app
clockwars said:
believe me I want to!
but I'm not sure how to do it yet.
(chicken-egg situation, lol)
I've read conflicting things, like you have to have SuperCID first before you S-off..
but then I read that you need to S-off first
which one is it?
Click to expand...
Click to collapse
It's stated pretty clearly in the s-off thread that you must have SuperCID first. I'm not sure where you think you read that s-off is required for SuperCID but that's 100% incorrect.
Sent from my Evita
timmaaa said:
It's stated pretty clearly in the s-off thread that you must have SuperCID first. I'm not sure where you think you read that s-off is required for SuperCID but that's 100% incorrect.
Sent from my Evita
Click to expand...
Click to collapse
no offence!
I'm not accusing anyone of anything! lol
and I'm obviously not an Android guru..
As you can see from my number of posts, I'm not a regular here!
so I wasn't following the progress of things..
and I'm not familiar with the specific thread you guys mention.
I was mostly using Google,
and trying to find someone with a Rogers version, to see how they did it.
And almost every bit I found would read "SuperCID for S-off" so I assumed that you need an S-off device in order to get SuperCID..
Ok, I wouldn't suggest going to any site for info other than XDA, you could end up with incorrect information as other sites don't properly distinguish between models. Long story short, stay on XDA and specifically within this forum.
You can get SuperCID using hex edit method. Then you can get s-off using Facepalm S-off.
Sent from my Evita
clockwars said:
no offence!
I'm not accusing anyone of anything! lol
and I'm obviously not an Android guru..
As you can see from my number of posts, I'm not a regular here!
so I wasn't following the progress of things..
and I'm not familiar with the specific thread you guys mention.
I was mostly using Google,
and trying to find someone with a Rogers version, to see how they did it.
And almost every bit I found would read "SuperCID for S-off" so I assumed that you need an S-off device in order to get SuperCID..
Click to expand...
Click to collapse
You are definitely on the right site but you need to read through the directions and understand what they mean. It's important that you know just what S-Off and Super CID mean to the phone before you try these procedures out. Taking a test drive without getting ALL the steps (and there are more) in order and correct CAN and WILL brick your phone. Bottom line...spend the time researching what you need to do to get where you want to be. Good luck out there.
Madcat8686 said:
You are definitely in the right sight but you need to read through the directions and understand what they mean. It's important that you know just what S-Off and Super CID mean to the phone before you try these procedures out. Taking a test drive without getting ALL the steps (and there are more) in order and correct CAN and WILL brick your phone. Bottom line...spend the time researching what you need to do to get where you want to be. Good luck out there.
Click to expand...
Click to collapse
Yeah I can see this site is a wealth of information.
A lot of brilliant people here!
timmaaa said:
Ok, I wouldn't suggest going to any site for info other than XDA, you could end up with incorrect information as other sites don't properly distinguish between models. Long story short, stay on XDA and specifically within this forum.
You can get SuperCID using hex edit method. Then you can get s-off using Facepalm S-off.
Sent from my Evita
Click to expand...
Click to collapse
thanks a million!
you sir are a true gentleman.
I followed the SuperCID instructions and everything seemed to work perfectly.
Now when I type: fastboot oem readcid in fastboot I get: (bootloader) cid: 11111111
which is great, but I also have an app called CID Getter (with a cupcake icon), and that app is telling me that my CID is [ROGER001].
Before I go any further, I need your help!
what does it mean?
I rebooted in fastboot again and fastboot oem readcid command still gives me 11111111
CID Getter doesn't display the correct CID, I'm not sure where it pulls it from but it's incorrect. The 11111111 you get from the fastboot command is your true CID so you can go ahead and proceed with s-off.
Sent from my Evita
Hi i am pretty new to the forums but have been flashing roms for awhile. I have super cid and s-off and recently upgraded to 2.15 after I was having a lot of random reboots/boot loops/no signal on CM10.2, CarbonJB, Beanstalk. I could only get my phone to boot with the 2.14 hboot when i flashed KickDroid but there were still no signal problems and some random reboots.
This seems to be fixed with the 2.15 hboot but I've been wanting to return to a pure android rom for awhile. I hear 2.15 does not work with any non-sense roms and indeed when i tried to flash CM10.2 again it would bootloop. I have heard however, in random threads throughout the forums that i could possibly use 2.15 hboot along with the Beastmode kernel to run Beanstalk.
Does anybody who is more knowledgeable than me at these things know which roms are now compatible with the 2.15 update?
Hailfire said:
Hi i am pretty new to the forums but have been flashing roms for awhile. I have super cid and s-off and recently upgraded to 2.15 after I was having a lot of random reboots/boot loops/no signal on CM10.2, CarbonJB, Beanstalk. I could only get my phone to boot with the 2.14 hboot when i flashed KickDroid but there were still no signal problems and some random reboots.
This seems to be fixed with the 2.15 hboot but I've been wanting to return to a pure android rom for awhile. I hear 2.15 does not work with any non-sense roms and indeed when i tried to flash CM10.2 again it would bootloop. I have heard however, in random threads throughout the forums that i could possibly use 2.15 hboot along with the Beastmode kernel to run Beanstalk.
Does anybody who is more knowledgeable than me at these things know which roms are now compatible with the 2.15 update?
Click to expand...
Click to collapse
AOSP-wise, I'm pretty sure CFX is 2.15 compatible
Sent from my HTC One XL using XDA Premium 4 mobile app
CM10.2 is definitely compatible with the 2.15 firmware package, the bootloop was likely caused by the current bugs with the ROM itself.
Sent from my Evita
timmaaa said:
CM10.2 is definitely compatible with the 2.15 firmware package, the bootloop was likely caused by the current bugs with the ROM itself.
Sent from my Evita
Click to expand...
Click to collapse
4.3 just wasn't a good run for aosp
Sent from my HTC One XL using XDA Premium 4 mobile app
So I am a little (a lot) scared to touch my new phone.
I recently acquired an AT&T One X, and it is currently rooted, and running CleanROM 6.5.0. I don't have the history of the device, so I am not sure how its previous owner got it to here, and what the safest steps would be to get it back to pure stock.
I am not worried about resetting the tamper indication or warranty issues. I just would like to get back to the stock AT&T software, and then I can go from there getting it where I want it.
The phone has TWRP Recovery, but had no recovery images. I have made a recovery for where it is at currently.
Bootloader currently shows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
CID- 11111111
HBOOT-2.15.0000
RADIO -0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Aug 14 2013, 16:02:22 -1
I would say my skill level with phones is "moderate". I at least know enough to not mess with something if I am not 100% sure.
So, from what I am seeing, the phone is S-on, and bootloader is locked, and I have superCID, so I should be able to just flash the proper RUU?
Or, is there anything else I need to do first?
Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.
timmaaa said:
Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.
Click to expand...
Click to collapse
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.
Your thread is now in the Q&A section:good:
floodx4 said:
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.
Click to expand...
Click to collapse
I admire the fact that you want to get it there yourself, the learning aspect of unlocking a device is very important in my eyes. The first thing you need to do is get s-off so you can safely run an RUU without bricking your device. I'll give you a quick run down of the entire process first though.
1. Get s-off.
2. Run the 3.18 RUU.
3. Change CID from SuperCID to original CID.
4. Use the 3.18 root method to gain SuperCID again.
5. Unlock your bootloader at htcdev.
6. Install TWRP recovery.
7. Upgrade to the 2.15 firmware package.
8. Flash Cleanrom 7.x.
So, first you'll need s-off. The easiest way is probably to use the Rumrunner method, you'll find it here:
Http://Rumrunner.us
Even before doing that though you'll need to setup an adb/fastboot environment on your PC. Adb.exe and fastboot.exe are programs you install on Windows in order to communicate with your phone via the usb cable and command prompt. In order for these to work you'll also need HTC drivers installed.
This thread is the easiest way to install adb/fastboot:
http://forum.xda-developers.com/showthread.php?p=42407269
This is where you can find the latest HTC drivers:
http://forum.xda-developers.com/showthread.php?t=2535581
Once you have those both installed you should test out the communication. Connect your phone in fastboot mode (boot into bootloader and connect device, it'll say fastboot usb on the phone), open a command prompt from within your fastboot folder (navigate to where fastboot is located on your PC, shift + right click anywhere in that folder, select open command prompt here), and issue this command:
Code:
fastboot devices
It should now return your device serial number, if it does you can go ahead and attempt Rumrunner s-off. If it doesn't return the serial you have a problem with communication.
Sent from my Evita.
How do I know what the original CID should be?
The above post by me lists how to go about the entire process, which isn't completely necessary but I've outlined it because you said you want to start from the beginning. There is a shorter way to do this, if you'd like to go for that just let me know and I'll outline though too. Your steps there look ok but I'd make a slight change.
Sent from my Evita.
floodx4 please be sure to click timmaaa thanks button.
That's how we show appreciation on XDA
Dang.......
Went through the Rumrunner process, everything seemed to go as it should, but I am still S-on.
Also, tried to unlock through HTC DEV, and I get nothing after flash the unlock token. (phone never gives me the "accept" screen.
Communication is good through fastboot, but something doesn't seem right.
Any ideas, or should I just leave well enough alone and live with 4.1?
Oh, that's my fault, I forgot you need an unlocked bootloader for Rumrunner to work. Sometimes it can take several attempts at flashing the unlock token for it to work, so keep trying that.
Sent from my Evita.
Man.....not sure what the previous owner did here, but....
I tried flashing the unlock token several times....all seemed to go through, but no "accept" screen on the phone.
Finally, I sent the fastboot oem lock command, and it "somewhat" acted like it relocked it. (I did get a FAILED message in there somewhere).
Resent the flash token command, and viola! I got the "accept" screen. Accepted the warning....and.....still locked
Went through Rumrunner again, just to see, and same result. I get the success message, but still have a locked bootloader, and still have s-on.
Back to the drawing board.......
EDIT: Went back through the process again, and noticed that when I send the fastboot oem lock command, the status changes to ***RELOCKED***, and after I flash the token, and accept the warning, the phone resets back to factory.....but bootloader still shows locked.
2nd EDIT: I think I may be on to something here!
Could the phone have one of the tools installed that "spoof" the hboot screen?
Here is what I get from a getvar all:
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT255W302399
(bootloader) imei: 3xxxx6
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4052mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.083s
Could I be s-off and unlocked, and just not seeing it?
Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now disconnect your phone and select recovery from the bootloader screen on your phone. Hopefully it boots into TWRP recovery, this proves that your bootloader is in fact unlocked.
Sent from my Evita.
timmaaa said:
Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
<snip>
Click to expand...
Click to collapse
OK, we are getting somewhere!
I have the TWRP recovery. (I believe I already may have had this same recovery, but It did flash successfully via the commands, so I think I'm good)
So....now what? Can I "un-spoof" the hboot to be sure? Or just be satisfied with the above experiment? And if so, does this put me at Step #2 "Flash the 3.18 RUU"?
Yeah I believe you're good to go, I'd like to be doubly sure first though. You can change your CID as many times as you like if you have s-off, but with s-on you can't do that. So I'd suggest trying to change it and this will confirm your security status. The command is:
Code:
fastboot oem writecid 22222222
Hopefully that'll work, confirm by giving this command:
Code:
fastboot oem readcid
Hopefully you'll see eight two's. Once you've confirmed that works you can change it back, and you'll be good to go with the 3.18 RUU. The RUU will install the official 2.14 hboot so the locked/unlocked/relocked flags at the top of your bootloader screen will be normal again.
PS. You might want to edit the IMEI out of your post above, you should never post that publicly.
Sent from my Evita.
Cool, writecid worked.
And speaking of that, Step 3, Change CID to original......what would the original CID be?
I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.
timmaaa said:
I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.
Click to expand...
Click to collapse
Awesome.
Just to be sure here....do I want my bootloader locked or unlocked when I flash the RUU?
You're s-off so you can leave the bootloader unlocked. Here's a link for the RUU.
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
Sent from my Evita.
I cant hit the thanks button enough!
CleanRom 7 installed and working great, and best of all, I know where it came from.
Now its time to take this thing for a test drive.......
Oohhhh yeah! That's what I'm talkin bout!
Great news, and once again I admire you for actually wanting to put in the effort and do some learning along the way. Most people want to take the shortest road possible, and they're inevitably the ones who have no idea what to do when something goes wrong.
If you do ever need help in the future just let me know.
Sent from my Evita.