Here's the deal:
I'm trying to create a system to flash the One X via fastboot.
Currently, my device has an unlocked bootloader (changed CID, used HTC Dev) and is running the stock 2.20.507 release.
Using 'fastboot flash system system.img' and providing the stock system.img for this build extracted from the rom.zip inside of the RUU does not work - I get an 'out of space error.'
Running "fastboot oem rebootRUU" and attempting to flash the ROM.zip that way provides the following error.
What's up?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I dont think that works, atleast not on att
DvineLord said:
I dont think that works, atleast not on att
Click to expand...
Click to collapse
Do you know why?
Hboot lockdown
DvineLord said:
Hboot lockdown
Click to expand...
Click to collapse
What does that mean?
Does that mean the version of Hboot on this device literally doesn't allow anything to be flashed to system?
Is it possible to downgrade to something older than what the device shipped with (1.14.0002) or do they have the same restrictions too?
I dont know what version allowed it or if any. Also wish we could run fastboot erase userdata
DvineLord said:
I dont know what version allowed it or if any. Also wish we could run fastboot erase userdata
Click to expand...
Click to collapse
It's remarkable how useless this is. Thanks HTC for providing an "Unlocked" bootloader that is anything but.
Do you know what the earliest version shipped on HTC One X's would be? And is it possible to flash hboot by itself from fastboot (without screwing anything up?)
why not flash the ruu? what are you trying to do?
according to your picture you can't use that method because of supercid, it might work if you changed cid back to original
DvineLord said:
why not flash the ruu? what are you trying to do?
Click to expand...
Click to collapse
Well good question... there is a reason, and it has to do with an automated build flashing/testing system I've been assigned to work on. If it's impossible, I'll find another way (with a custom recovery), but I want to exhaust all possibilities and at least understand why this device is so 'picky'
think the problem is supercid, might work on devices not supercid. will unlock token work if you remove supercid on att htc one xl?
DvineLord said:
think the problem is supercid, might work on devices not supercid. will unlock token work if you remove supercid on att htc one xl?
Click to expand...
Click to collapse
I know to do the HTC Dev unlock in the first place I had to change it...you think I should revert it, try the unlock token again? Is it correct that you have to relock the bootloader to revert the CID? Never done it before...
[2.20 Firmware] Remove Pesky root
this is the only way i know to revert it. also a funny thread. it was made before 2.20 root. enjoy the thread. =)
DvineLord said:
[2.20 Firmware] Remove Pesky root
this is the only way i know to revert it. also a funny thread. it was made before 2.20 root. enjoy the thread. =)
Click to expand...
Click to collapse
LOL this guy...
Anyhow I guess I'll try it, if in fact I cannot unlock again after doing that, I'll just have to re-SuperCID again to get back to my present state...guess it's worth a shot.
DvineLord said:
[2.20 Firmware] Remove Pesky root
this is the only way i know to revert it. also a funny thread. it was made before 2.20 root. enjoy the thread. =)
Click to expand...
Click to collapse
can you not extract mmcblk0p23, hex edit it to change the cid and the copy it back to system? or is the cid in mmcblk0p4?
Why would it be in system?
DvineLord said:
Why would it be in system?
Click to expand...
Click to collapse
erm my bad. i meant push it back to emmc tired today
That's what the thread says i think
When you flash the rom.zip, you get supercid please flush, resend the fastboot flash command, then you will get bootloader flush, resend command again and it will have finish the flash
Sent from my SPH-L710 using Tapatalk 2
18th.abn said:
When you flash the rom.zip, you get supercid please flush, resend the fastboot flash command, then you will get bootloader flush, resend command again and it will have finish the flash
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Run the same command three times in a row? I'm certain I tried at least that many, but I'll have to give it another try...
It works, dont reboot device.
Sent from my SPH-L710 using Tapatalk 2
Related
HI all,
just got my phone back, but with a new boot loader. I tried the htcdev unlock method but no sigar for me.
Anyone else?
Sent from my HTC Sensation Z710e using xda premium
The error:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.172s
Any chance using a "official" ruu with an older boot loader will downgrade the phone?
Sent from my HTC Sensation Z710e using xda premium
http://forum.xda-developers.com/showthread.php?t=1616836
This is not possible and I cant remember quite how I did it but :-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry about the crap pic. Wife's SGS2 lol
duryard said:
This is not possible and I cant remember quite how I did it but :-
Sorry about the crap pic. Wife's SGS2 lol
Click to expand...
Click to collapse
so the question is how did you this indeed
Sent from my HTC Sensation Z710e using xda premium
well dont quote me on this but
Downgraded to 1.17
rev unlock
upgrade (by 2 steps I think) to get back to 1.27
htc dev unlock
and thats what came up
duryard said:
well dont quote me on this but
Downgraded to 1.17
rev unlock
upgrade (by 2 steps I think) to get back to 1.27
htc dev unlock
and thats what came up
Click to expand...
Click to collapse
so "quote" , how to downgrade, tried different RUU's but all hung on an error.
Can't write device (or something similar).
AngryB said:
http://forum.xda-developers.com/showthread.php?t=1616836
Click to expand...
Click to collapse
Tried: root-sensation-windows from: http://forum.xda-developers.com/showpost.php?p=25910487&postcount=53
Shows me:
ECHO EVERYTHING DONE..ROOT SUCCESS...ONE FINAL REBOOT NOW
But after the reboot, still no root, so no flashing yet....
what exactly are you trying to achieve by rooting?
There is a way to install 4ext recovery which gives you a sort of root on 1.27 that allows flashing
duryard said:
what exactly are you trying to achieve by rooting?
There is a way to install 4ext recovery which gives you a sort of root on 1.27 that allows flashing
Click to expand...
Click to collapse
i just want to use my phone as i always did, flashing roms, compiling stuff etc. This hboot (1.27) won't let me do anything, can't flash **** anymore
peewster said:
Tried: root-sensation-windows from: http://forum.xda-developers.com/showpost.php?p=25910487&postcount=53
Shows me:
ECHO EVERYTHING DONE..ROOT SUCCESS...ONE FINAL REBOOT NOW
But after the reboot, still no root, so no flashing yet....
Click to expand...
Click to collapse
This happens because after you reset the phone back to its original ****...
AngryB said:
This happens because after you reset the phone back to its original ****...
Click to expand...
Click to collapse
i think i'll just sell it with the default stuff on it, and buy a S2 or swap it with a S2
Ok I will need to find the post and the file. was a while ago so don't hold your breath
duryard said:
Ok I will need to find the post and the file. was a while ago so don't hold your breath
Click to expand...
Click to collapse
Cool, let me know if you find it
Think this is it.
Here's 4EXT in PG58IMG.zip form. Flash via HBOOT (not stock recovery)
Attached Files
http://dl.dropbox.com/u/8397645/PG58IMG.zip
duryard said:
Think this is it.
Here's 4EXT in PG58IMG.zip form. Flash via HBOOT (not stock recovery)
Attached Files
http://dl.dropbox.com/u/8397645/PG58IMG.zip
Click to expand...
Click to collapse
ok, so it checking the zip file, and then it just quits the checking and that's it, this happens with all the PG58IMG.zip files i try. It looks like a flash block or something, idk, weird stuff.
bit of a long shot. Try downgrading. Then flash the PG58IMG
duryard said:
bit of a long shot. Try downgrading. Then flash the PG58IMG
Click to expand...
Click to collapse
downgrading with an official RUU doesn't work either, just device write errors, nothing specific...
Official RUU from KPN ?
duryard said:
Official RUU from KPN ?
Click to expand...
Click to collapse
i tried multiple. Do you have a link to the kpn one? Can always try it
Sent from my HTC Sensation Z710e using xda premium
How to return to stock to return to stock
1. Download HTC One S All-In-One Toolkit V1.0.
2. Unzip it and run it.
3. Please make sure you have your Unlock_code.bin in One_S_All-In-One_Kit_v1.0 data folder
4. Highlight stock under recovery and click flash recovery.
5. Your phone will reboot then click relock bootloader.
6. after you relock bootloader run carrier ruu
T-Mobile USA RUU.
Roger RUU
Correction: run your carrier's RUU...
http://forum.xda-developers.com/showthread.php?t=1543588
Sent from my HTC One S using xda premium
Any options for Mac/Linux users since there's no intentions of bringing this tool to us? It'd be greatly appreciated.
NienorGT said:
Correction: run your carrier's RUU...
http://forum.xda-developers.com/showthread.php?t=1543588
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No I think you misunderstand what OP has done...... Toolkit I'm assuming that locks your bootloader back and also runs the ruu.exe. thanks. OP
Sent from my HTC VLE_U using XDA Premium HD app
alwayshalfway said:
Any options for Mac/Linux users since there's no intentions of bringing this tool to us? It'd be greatly appreciated.
Click to expand...
Click to collapse
these are all commands achieveable through terminal and fastboot, its just nicely packaged for windows in this.
JDenson77 said:
No I think you misunderstand what OP has done...... Toolkit I'm assuming that locks your bootloader back and also runs the ruu.exe.
Click to expand...
Click to collapse
Nah he previously said in it's tutorial to run the T-Mobile RUU, which applies only to T-Mobile users. He did correct that little ambiguity
Sent from my HTC One S using xda premium
I follow step by step, but i cant instal the RUU, it give me error 155. 3 uk Htc one s! Help please!
Sent from my HTC one s using xda premium
Do you have the right RUU
There's no longer a need to go back to stock. If you're looking for the radio file, it's here.
The kernel will probably be baked into the next AOKP and CM9 roms, and I'm sure there'll be a flashable zip of the new kernel coming out very soon as well.
NOTE: If you're flashing the new radio, you need to use TWRP. Clockworkmod will NOT work properly for this, so don't bother trying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i got the right ruu for the us htc one s for tmobile but for some reason i must be missing something cause my pc keeps asking me what program would i like to run the ruu with lol. does anyone know why it wont open the ruu? its been so long since ive ran the file.
The RUU is an .exe file.
RUU are very useful to reset the phone to stock before returns/selling it. It's also useful to go back to see if an issue was provocked by the Rom/root/whatever and not the phone itself.
Sent from my HTC One S using xda premium
s10shane said:
i got the right ruu for the us htc one s for tmobile but for some reason i must be missing something cause my pc keeps asking me what program would i like to run the ruu with lol. does anyone know why it wont open the ruu? its been so long since ive ran the file.
Click to expand...
Click to collapse
Ruu.exe', you mast remove (')
Sent from my HTC one s
cbetso said:
Do you have the right RUU
Click to expand...
Click to collapse
Yes for 3uk! :-(
Sent from my HTC one s
I get error 140 when running RUU because I upgraded to 1.84 today. Is it safe to downgrade to a 1.53 ROM and then run RUU?
Tells me the files are gone now.
---------- Post added at 09:20 PM ---------- Previous post was at 09:03 PM ----------
cbetso said:
How to return to stock to return to stock
1. Please make sure you have your Unlock_code.bin on your sdcard root
2. Download HTC One S All-In-One Toolkit V1.0.
3. Unzip it and run it.
4. Highlight stock under recovery and click flash recovery.
5. Your phone will reboot then click relock bootloader.
6. after you relock bootloader run carrier ruu
T-Mobile USA RUU.
Roger RUU
Click to expand...
Click to collapse
Why do you keep the unlock bin on the phone? Also don't you need to get a new one after you do this to unroot it?
Minor corrections. Just relock the bootloader. Let the phone turn on after it is relocked. Run the RUU for your device's carrier. No need to flash stock recovery.
andorinho said:
I get error 140 when running RUU because I upgraded to 1.84 today. Is it safe to downgrade to a 1.53 ROM and then run RUU?
Click to expand...
Click to collapse
+1 I'm in the same boat. Want to get back to 1.53 but the ruu gives me the same error.
HTC Android Phone ROM Update Utility 1.0.5.2011
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
michaelh99 said:
+1 I'm in the same boat. Want to get back to 1.53 but the ruu gives me the same error.
HTC Android Phone ROM Update Utility 1.0.5.2011
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
If your rooted just restore the 1.53 Nandroid floating around the dev section.
No, not rooted
michaelh99 said:
No, not rooted
Click to expand...
Click to collapse
Sorry, root is your only option to downgrade. If your having issues then I would pursue a replacement from T-Mobile as my phone works perfectly fine on 1.84.
I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
1. download rogers ruu.zip
2. get supercid or downgrade follow http://forum.xda-developers.com/showthread.php?t=1671135
3. use the windows ruu tool ..... or .... get adb and fastboot installed correctly. google this if you dont know how
4a. for windows ruu tool follow my post in dev section
4b. for adb and fastboot do
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
it will ask u to run the last command again...
Berserk87 said:
I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
Click to expand...
Click to collapse
Have you relocked your bootloader?
1. make sure fastboot in android is turned off under power.
2. power off device
3. power phone on by holding down the volume down key + pressing power - don't release the volume down key until you see the bootloader screen
4. select fastboot
5. connect phone usb
6. screen should now read fastboot usb in red
7. type fastboot oem lock
Phone might restart back into fastboot can't really remember but now you can run the RUU.
The RUU should be an .exe for the above
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Berserk87 said:
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Click to expand...
Click to collapse
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
niceppl said:
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
Click to expand...
Click to collapse
I did.
and my bootloader has never been unlocked.
its giving me something about incorrect bootloader version. even though its the rogers rom.
Do i need to super cid if im flashing the same version? (1.73 to 1.73)
aruwizard just keeps saying "wrong bootloader version"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what im getting everytime i try to use aruwizard.
Berserk87 said:
this is what im getting everytime i try to use aruwizard.
Click to expand...
Click to collapse
where did u get the aruwizard tool seems its not the one for hox...too old maybe...try the adb amd fastboot method i mentioned above
Sent from my HTC One X using xda app-developers app
niceppl said:
where did u get the aruwizard tool seems its not the one for hox...
Click to expand...
Click to collapse
downloaded it from your other thread. http://forum.xda-developers.com/showthread.php?t=1658929
using fastboot it starts doing the checks, then gets to :
Code:
INFOchecking main version...
FAILED (remote: 43 main version check fail)
looks like even though im trying to flash 1.73 to 1.73 i still need to do the downgrading firmware stuff...
im curious if my failed update upgraded some stuff and failed on the rest...
now its giving me
Code:
FAILED (remote: 44 hboot version check fail)
anyone?
$5 to anyone that can tell me how to fix this (get back to full stock)
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
if you want to change supercid back to roger001
do previous steps again and change the cid to roger001 rather than supercid
Sent from my HTC One X using xda app-developers app
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
Lol $5 thought a twenty was the customary amount
Sent from my HTC One XL
niceppl said:
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
\
Click to expand...
Click to collapse
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Berserk87 said:
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Click to expand...
Click to collapse
You need to unlock, but alas once you flash the ruu ... The unlocked/tampered proof will be rewritten to stock as well...
From my HTC One X possessed by the Illuminati hybrid kernel
It will show relocked instead of locked.Not sure if warranty accept it
hi guys unfortunately i need to send my phone in warranty (sniff)
previously i'm rooting my ds with revolutionary
and now i follow this
i flashed eng boot and next i use android flasher flashing the hboot in the root of the folder..
anyway i'm now with:
***security warning***
saga pvt ship s-on rl
hboot-0.98.0002
radio-3831.19.00.110
emmc-boot
bla bla bla...
i'm tryng to use the ruu to revert the rom back to stock
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
but it says "unable to update"
now i think i have the h boot 98.0002 and the ruu have 98.0000
so it didn't work but i can't find the ruu thread on xda (i remember there it was some time ago)
any help?
Is it that link you are looking for ? : HTC Saga Shipped Roms
kiss!!!! xD
i have an error....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Husky34 said:
i have an error....
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Click to expand...
Click to collapse
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
NVardan said:
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
Click to expand...
Click to collapse
mmm no...what is it? (i think i'v heard it...is something inside the sd right?)
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
hipp0po said:
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
Click to expand...
Click to collapse
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Husky34 said:
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Click to expand...
Click to collapse
run the ruu in fastboot?
Sent from my supercharged :tank:
hisname said:
run the ruu in fastboot?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
yep is it correct? it works for a while and then bam error 140..
Husky34 said:
yep is it correct? it works for a while and then bam error 140..
Click to expand...
Click to collapse
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
hisname said:
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
i'll put the screen in the first page of this thread...and i even try to change misc version without success..
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
amidabuddha said:
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
Click to expand...
Click to collapse
but i want to send into warranty man...i can't unlock bootloader via htc dev
Husky34 said:
but i want to send into warranty man...i can't unlock bootloader via htc dev
Click to expand...
Click to collapse
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
Click to expand...
Click to collapse
can i fire my mmc in some way?if my phone doesen't boot i think they can change my motherboard...:'(
i know is a hard decision....but i think is the only one...
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Husky34 said:
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Click to expand...
Click to collapse
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
amidabuddha said:
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
Click to expand...
Click to collapse
of course i check
thanks for the info and have a good day all!
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
Click to expand...
Click to collapse
What are you talking about? He can just use tacoroot. Either way, he was S-OFF, so he can just S-OFF again, change miscversion, and then roll back to S-ON.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As soon as i was S-Off I did this and it worked great,
Code:
[SIZE="3"]adb reboot-bootloader[/SIZE]
Code:
[SIZE="3"]sudo fastboot oem writecid 11111111 [/SIZE]
The reason i put sudo in front of it is beacause now days you can install Adb and Fastboot Via PPA on Ubuntu and fastboot requires sudo,
If you have it installed the traditional way leave sudo in or out it wont hurt either way.
If you wanna go back to original then
Code:
sudo fastboot oem writecid VZW__001
The ouput should be
Code:
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.029s]
finished. total time: 0.029s
Or close to it as far as time goes..
Cheers All!
oh Hai
hope to start hangin here soon with you
This is my first HTC device so changing your CID is new to me. With S-OFF, i can flash recovery / roms. Why would I need to change my CID to 1111? Is the only profit the ability to install another carrier rom?
Alright, this is new to me. So, I have to ask.
As stated in the OP we can flash any carrier roms? That won't mess with anything specifically will it?
Above is my video guide on enabling SuperCID for those who would prefer a visual aid. Feel free to add to the OP if you like.
Sent from my SM-N900V using xda app-developers app
kwkw480 said:
This is my first HTC device so changing your CID is new to me. With S-OFF, i can flash recovery / roms. Why would I need to change my CID to 1111? Is the only profit the ability to install another carrier rom?
Click to expand...
Click to collapse
My understanding is that you need to change the CID to be able to unlock the bootloader using HTCdev.com that way it won't deny you anymore. Somebody correct me if I'm wrong.
ok now that im 111111 i can now go install http://forum.xda-developers.com/showthread.php?t=2706441 (GPE)?
Now that we are s-off and have a super cid, we can RUU.exe to different carriers. I have never done it ... But as stated in the op, I like options and for me this is kind of an incase something happens extra for me to have. if i need to RUU and all i have is google edition RUU then hey, It's enough to get me going . As always you can google to get alot more info from different sources, this is just somthing until my kernel finishes building
nicholi2789 said:
My understanding is that you need to change the CID to be able to unlock the bootloader using HTCdev.com that way it won't deny you anymore. Somebody correct me if I'm wrong.
Click to expand...
Click to collapse
All of the mods and the roms that you flash will check your cid and model before they will flash. If it detects a cid or model that it is not supported it will error out. This is just a way to change your cid to make sure that it will be accepted.
Zarboz said:
oh Hai
hope to start hangin here soon with you
Click to expand...
Click to collapse
Well Z... how come your not here already? It'll be like the old days.
androidoholic said:
All of the mods and the roms that you flash will check your cid and model before they will flash. If it detects a cid or model that it is not supported it will error out. This is just a way to change your cid to make sure that it will be accepted.
Click to expand...
Click to collapse
Ah okay. It's my first HTC device too, I always had samsung before. But won't this also make it so we can unlock via HTC dev? Or can we just do fastboot oem unlock?
nicholi2789 said:
My understanding is that you need to change the CID to be able to unlock the bootloader using HTCdev.com that way it won't deny you anymore. Somebody correct me if I'm wrong.
Click to expand...
Click to collapse
nicholi2789 said:
Ah okay. It's my first HTC device too, I always had samsung before. But won't this also make it so we can unlock via HTC dev? Or can we just do fastboot oem unlock?
Click to expand...
Click to collapse
That was the case on the m7, but firewater unlocks the bootloader as well, so no need to do it through HTCdev
androidoholic said:
That was the case on the m7, but firewater unlocks the bootloader as well, so no need to do it through HTCdev
Click to expand...
Click to collapse
Oh nice. I didn't know that. So I don't have to worry about backing up for a full factory reset or anything. Sweet.
nicholi2789 said:
Oh nice. I didn't know that. So I don't have to worry about backing up for a full factory reset or anything. Sweet.
Click to expand...
Click to collapse
flashing an international rom fails at getting the build product in the build prop. so that needs to be modified.
sgtmedeiros said:
flashing an international rom fails at getting the build product in the build prop. so that needs to be modified.
Click to expand...
Click to collapse
ya you would have to change the updater-script, but before it is fully tested I would not try to do that unless you have experience, should not cause any irreversible harm, but it would most likely be a waste of time, because of the different radios and such. The roms for the international version are going to have to be ported over. I'm working on the gpe tonight.
androidoholic said:
That was the case on the m7, but firewater unlocks the bootloader as well, so no need to do it through HTCdev
Click to expand...
Click to collapse
Even though we have S-OFF, the bootloader is still locked.
BFirebird101 said:
Even though we have S-OFF, the bootloader is still locked.
Click to expand...
Click to collapse
after firewater mine shows unlocked
Karl said:
after firewater mine shows unlocked
Click to expand...
Click to collapse
Yup, same here.
Karl said:
after firewater mine shows unlocked
Click to expand...
Click to collapse
It's my understanding that when you unlock the bootloader, the device gets wiped. At least, that was how it was on my Galaxy Nexus and Nexus 7 2013. By my fastboot screen showing unlocked, I just assumed that meant that S-OFF worked, but that the bootloader was still locked. If it is indeed unlocked, then that is awesome!
BFirebird101 said:
It's my understanding that when you unlock the bootloader, the device gets wiped. At least, that was how it was on my Galaxy Nexus and Nexus 7 2013. By my fastboot screen showing unlocked, I just assumed that meant that S-OFF worked, but that the bootloader was still locked. If it is indeed unlocked, then that is awesome!
Click to expand...
Click to collapse
it is unlocked after firewater