Database Develop

[Q] How can change the Cid Number HTC__622 to HTC__J15 ???

Hello,
i need change cid number from HTC__622 to HTC__J15 ...
i follow the instructions applied for Sensation (with adb tools) in windows 7
My incredible s respond to the adb method but give me Error after last step as following:
Code:
Code:
C:\adb>fastboot oem writecid HTC__J15
...
[bootloader] [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s
Any idea PLz???
HTC Incredible S 2.3.3
HBOOT 1.09.1000
AlphaRev S-offed & Rooted

UP
Sent from my HTC Incredible S using XDA Premium App

I am too uninformed to help you so all I can do is give a +1 to help your cause.
Your welcome.

itsbeertimenow said:
I am too uninformed to help you so all I can do is give a +1 to help your cause.
Your welcome.
Click to expand...
Click to collapse
Thank u

up
Sent from my HTC Incredible S using XDA Premium App

any ideas please ???

>>> up <<<

Stop doing that.

we cant do that at this time with the IS we dont have the same amount of access we do on sensation

Thanks..
Sent from my HTC Incredible S using XDA Premium App

See the list of available commands: fastboot oem h

thats all i get when i type in the command fastboot oem h
Code:
C:\adb>fastboot oem h
...
(bootloader) command list
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]

UP
إرسلت من HTC Incredible S باستخدام برنامج XDA Premium App

1) execute:
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/cid.img
2) edit cid.img with any hex editor (but don't use notepad or any other text editor)
3) write it back:
Code:
dd if=/sdcard/cid.img of=/dev/block/mmcblk0p17
4) reboot and check. your cid should now be changed.
It worked for me, but I'm not responsible if your device will become a brick (which is unlikely anyway)
Good luck.

NeverGone\RU said:
1) execute:
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/cid.img
2) edit cid.img with any hex editor (but don't use notepad or any other text editor)
3) write it back:
Code:
dd if=/sdcard/cid.img of=/dev/block/mmcblk0p17
4) reboot and check. your cid should now be changed.
It worked for me, but I'm not responsible if your device will become a brick (which is unlikely anyway)
Good luck.
Click to expand...
Click to collapse
i try but i get
$ dd if=/dev/block/mmcblk0p17 of=/sdcard/cid.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/cid.img
/dev/block/mmcblk0p17: cannot open for read: Permission denied

moustafatch said:
i try but i get
$ dd if=/dev/block/mmcblk0p17 of=/sdcard/cid.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/cid.img
/dev/block/mmcblk0p17: cannot open for read: Permission denied
Click to expand...
Click to collapse
You need to have a rooted system and running the adb shell as Superuser to issue these commands.

it is temporary or not?
thanks

goki1 said:
it is temporary or not?
thanks
Click to expand...
Click to collapse
On a properly rooted system this would make a permanent change.

I have read about this method causing a USB brick in some cases on other models. Would be interested if anyone has similar issues.
Edit: if you're going to change the Cid might as well supercid it (11111111).

[DEV] S-OFF (wirte permission to NAND)

i started, this in the dev section, to have a CLEAN THREAD, with ONLY RELEVANT info.
if mod gives me permission i will clean this thread several times each day (if someone posts nonsense)
FOR DEVS ONLY! theres alot of other threads about this for Q&A etc..
thanks to orb3000 for making it a stickie..

reserved for later

What we got so far:
fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloadre) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
fastboot oem writesecureflag 0
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
C:\Users\Turkish>fastboot oem rebootRUU
...
(bootloader) erase sector 163328 ~ 163839 (512)
OKAY [ 0.484s]
finished. total time: 0.484s
C:\Users\Turkish>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Turkish>fastboot writesecureflag 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Turkish>fastboot reboot
rebooting...
finished. total time: 0.312s
Click to expand...
Click to collapse
We have tested to do these commands on the s-offed device of jammysunny.
cd/
cd SDK
cd platform-tools
adb devices
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
This worked successfully and we got an hboot.img file of his Device on the SD.
On the next step i tried to install his s-off hboot.img to my s-on device with the following commands:
cd/
cd SDK
cd platform-tools
adb devices
adb shell
su
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
This worked successfully too, but my bootloader is the same as before. Its s-on
Click to expand...
Click to collapse
hboot is useless from S-off device, as our bootloaders are unlocked.
What needs to be done is: get rid of Nand write protection, so we can flash radio's
Click to expand...
Click to collapse

Stickied, thanks!

waiting boot.img s-off

Im pretty sure s-off invokves the security flag on hboot not the boot.img
Sent from my HTC Sensation XL with Beats Audio X315b using XDA

Hi booyaga,
where I can find the s-off hboot.img file ?
thanks.
bye

Would love to see s-off lol
not sure if this can help...but my desire was s-off using alpharev
http://alpharev.nl/
maybe they can give some info ...?!?
with kind regards

It would be great to get alpharev on board. Seems everyone is neglecting our xl lol.
Sent from my GT-N7000 using xda premium

shingers5 said:
It would be great to get alpharev on board. Seems everyone is neglecting our xl lol.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
yep...if they dont want or do it (if we ask) maybe we can give a bit support...real s-off is nice...

Alex-V said:
yep...if they dont want or do it (if we ask) maybe we can give a bit support...real s-off is nice...
Click to expand...
Click to collapse
Willing to donate if needs be.
Sent from my GT-N7000 using xda premium

shingers5 said:
Willing to donate if needs be.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i also
with kind regards

Setting up a S-OFF donation thread to see who wants to donate and how much, might trigger there interest.
This is been seen on many dev treads, and can run up to few hundrerd euros

DutchDanny said:
Setting up a S-OFF donation thread to see who wants to donate and how much, might trigger there interest.
This is been seen on many dev treads, and can run up to few hundrerd euros
Click to expand...
Click to collapse
yea but not many devs even looking at xl and dont wanna line someones pocket who doesnt deliver!

shingers5 said:
yea but not many devs even looking at xl and dont wanna line someones pocket who doesnt deliver!
Click to expand...
Click to collapse
Guide them to the thread, and money will only be deliverd when s-off is deleverd

iḿ for that what DutchDanny says...and want give 20€ for s-off...who go with me...???!!!!!!!???!!
with kind regards

Alex-V said:
iḿ for that what DutchDanny says...and want give 20€ for s-off...who go with me...???!!!!!!!???!!
with kind regards
Click to expand...
Click to collapse
im in, with 10

DutchDanny said:
Guide them to the thread, and money will only be deliverd when s-off is deleverd
Click to expand...
Click to collapse
cool I shall donate soon as with 20 when needs be
Sent from my GT-N7000 using xda premium

30
Just because I want to learn more on this device and it will make life much easier!

Nice to See Some ideas, but Please make a bounty thread as its not really related to Development progress.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

[Q] Google Nexus One Stuck into boot screen

Hi Guys, i my Google nexus one stuck on boot screen.i had read lots of post on XDA to solve this problem but not able to solve.
My Nexus one has unlocked bootloader.
I flash recovery from fastboot and it successfully flashed.
but when i try to boot into recovery mode, device stuck on boot screen with lock symbol below, which denots unlock bootloader.
Please can any buddy tell what the problem or how can it flash custome rom into it .
Thanks .

try wipe all partition again
Code:
fastboot -w
fastboot erase recovery
fastboot reboot-bootloader
and reflash recovery
must use 4ext recovery
Edited: fixed

Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium

HTC Nexus One Problems- All Self-inflicted
demkantor said:
Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hi, First off, I'm so damn new I don't even qualify yet to be called "Noob". I bought an HTC Nexus One on eBay and it was loaded with 2.3.4. But I could not get it to update. I then took a look at the build # "3.11.405.2CL81940" with "release keys" added in a line below. Google came up with two or three hits, all starting with "Weird Build....", so I decided to get rid of it by rooting the phone. Over three days of fooling around with it and I am asking for help: after doing ALL KINDS OF THINGS (can't even remember the sequence), I'm stuck with a phone which when powered on no longer goes to the "X" splash screen but to "htc" with small yield signs with exclamation points in the four corners of the screen. The only way to power it down is to remove the battery. If I connect it to my Windows PC, it is recognized (I've downloaded the drivers, SDK Manager and AVD Manager) and I can perform certain functions using the command line within the SDK. But I can't format and start all over with a "stock" release let alone Jelly Bean which was my goal when starting all this. Additional information I can provide: when I remove the phone from the USB, the Black "htc" screen disappears and a white screen replaces it with the following: Line 1) BlackRose-Made by LeCache dl95244; line 2) STOCK 145/95/196; line 3) NEXUS ONE PV(or U)T S-off; line 4) HBOOT 7.3.5.5017 (PB9910000); line 4) TOUCHPANEL SYNT0103; line 5) RADIO-5.12.00.00; line 6) Apr 21 2012, 04:53:16; line 7) RUU. Line one, "BlackRose...", is black with white characters. Lines 2-6 are green characters on a white background (resembling the old boot screen) and finally, line 7, the "RUU" characters are white in an orange background, as though it's highlighted, asking for something. As said above, no buttons work (Track ball, Vol up/Vol down), and this is where the battery has to be pulled to power it down. Can anyone help?? I'll do my best to reply with any specifics that I DO remember, but I've done so many, many things in the past three days I've lost track. Thanks.

When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium

In response to your question:
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Let me describe it from the start. After insuring the device is fully charged I power it off the only way I can, pulling the battery, waiting 5 seconds, then reassembling the battery and back.
I get out the USB cord and insert it into the Windows PC. Then, (either powered on BEFORE insertion of the Micro USB or AFTER), when the device is powered on it goes to a new splash screen with "htc" in white on a gray/black background with caution signs at each corner of the screen. The device will stay that way for hours, plugged into a PC or powered on without tethering. THE ONLY WAY to access the white screen (which resembles the old boot screen without skateboards) is to unplug the device from the USB/PC WHILE POWERED ON.
When you do this, you have the "BlackRose" in white on a black line, then the rest as described, with "RUU" in orange.
There is one additional detail I do remember doing: I downloaded and installed "HTC One (M7//T-Mobile/AT&T/Sprint) AIO Kit by Hasoon2000v2.1 and Flashed CWM (GSM Only) Recovery. That was the last time the screen was at all responsive: lot's of lines rolling upward and then the words, I think, "Update failed".
Hasoon2000, I believe, is a member of this Forum and lives in Orland Park, IL, a suburb frustratingly close to me, in Chicago!!
---------- Post added at 07:02 AM ---------- Previous post was at 06:55 AM ----------
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Short answer, yes: Device Manager recognizes it and I hear a "cer-chunk" when its plugged in.

now you can enter bootloader or not?

bootloader
hxq88 said:
now you can enter bootloader or not?
Click to expand...
Click to collapse
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot devices HT0ALP801351
Click to expand...
Click to collapse
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>

its ok . did you run commands in post #2?
let try full wipe all and try it from beginning 1 more time. or use PASSIMG method to fast restore stock rom.
edit: ok full wiped, now reflash recovery ( try 4ext or TWRP, sorry i dont know link, you can find in search forum )

Post 2
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.

rickz41 said:
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.
Click to expand...
Click to collapse
wrong command: it must be fastboot reboot-bootloader

command
hxq88 said:
wrong command: it must be fastboot reboot-bootloader
Click to expand...
Click to collapse
Success!!
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.028s]
finished. total time: 0.029s
C:\android-sdk\platform-tools>
(Phone powered off- heard PC disconnect then reconnect, now screen is still same: whit "htc", black background with caution marks, all four corners....

enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
edit: its the name of recovery, i miss some letter cuz fast type

additional info
hxq88 said:
enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
Click to expand...
Click to collapse
Here I must repeat, I am not even Newbie or Noob- I am less than Noob!! What is 4ext, TWRP?? I will download them and do as you say but give detailed instructions for I am only an infant!! (when it comes to this, at least!)
---------- Post added at 10:55 AM ---------- Previous post was at 10:09 AM ----------
THANK YOU SO VERY MUCH FOR GETTING ME THIS FAR!!
It is greatly appreciated.
I will leave for awhile now, but thank you again.

Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium

Progress thus far:
demkantor said:
Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you for joining in and I must say at that I am in complete agreement with your feelings re: apple/MAC/iOS, etc.: they can go to Hell.
Let me post the results after following your instructions above:
C:\android-sdk\platform-tools>fastboot erase system -w
erasing 'system'...
OKAY [ 3.406s]
erasing 'userdata'...
OKAY [ 4.608s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.023s]
erasing 'cache'...
OKAY [ 2.223s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.022s]
finished. total time: 10.293s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.054s]
finished. total time: 0.057s
C:\android-sdk\platform-tools>fastboot flash recovery recovery-RA-passion-v2.2.1
.img
sending 'recovery' (3366 KB)...
OKAY [ 0.483s]
writing 'recovery'...
OKAY [ 1.082s]
finished. total time: 1.570s
But the n1 is still showing the gray/black splash with htc and the caution/yield signs at the corner. The line: "Erase successful, but not automatically formatting. Can't determine partition type." when erasing user data and formatting cache, is this something to be looked into?
I've flashed, I believe, successfully, AmonRa before but when I try to flash a 'Stock' passion image, it fails.
I'll continue reading your most helpful guides and hope for a step-by-step reply- I feel as though I am very close to solving this!
Again, many thanks!

Update
Sorry to report I've not made any progress since my last post despite the Guides provided.
A couple important points:
a) I cannot enter to cmd prompt level, fir whatever reason
b) This leave me with Fastboot and when the device is again wiped and prepared, Fastboot is entered, and I type Fastboot update update.zip with the following results attempting different "Stock Passion Images":
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
Any further thoughts??
Also, USB debugging is OFF complicating thins a lot, preventing me from getting a token from HTC's site!!

Bootloader should be unlocked being you have black rose, try different RUUs
http://forum.xda-developers.com/showthread.php?p=7495397
You may also try to change your cid to 11111111 this will allow you to flash any version
Sent from my Nexus 4 using xda premium

Questions:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
---------- Post added at 03:03 PM ---------- Previous post was at 02:48 PM ----------
rickz41 said:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
Click to expand...
Click to collapse
Took the advice here:
http://forum.xda-developers.com/showthread.php?t=2264322
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files\Android\android-sdk\platform-tools>
---------- Post added at 03:20 PM ---------- Previous post was at 03:03 PM ----------
C:\Program Files\Android\android-sdk\platform-tools>cd c:\mini-adb
The system cannot find the path specified.
C:\Program Files\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvarcid
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.024s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.019s
C:\Program Files\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.026s
C:\Program Files\Android\android-sdk\platform-tools>
It rebooted back to the same ole' 'htc' screen!

Try
fastboot oem getvar cid
To read it and
fastboot oem write cid 11111111
To write
As for which ruu to pick I'm not sure, never ran one on my n1, I did see a thread not to long ago where someone was trying to grab every official update from HTC, you can also try HTC directly and try to find the latest one
Sent from my Nexus 4 using xda premium

[Q] Please Help, Broke my HTC One

So yesterday i bought myself a new HTC ONE phone from Egypt, the original owner used it for just 48 hours then sold it. When i received it i found the SuperUser installed and the OTA updates were not installing sin11ce the phone has been modified.
I followed a tutorial on XDA about getting back to stock rom and after flashing custom recovery and moving the stock rom to SD card i flashed it from recovery and it failed in the process.
Now the phone just boots into recovery, can anyone please post me a quick tutorial on getting the stock firmware back? i would really appreciate it.
Here is the info from the recovery:
*** UNLOCKED ***
M7_U PVT SHIP S-OFF RH
CID- 11111111
HBOOT- 1.54.0000
RADIO- 4A.21.3263.04
OpenDSP- v31.120.274.0617
OS- 2.24.401.9
eMMC-boot 2048MB
AUG 9 2013, 16:20:20.0

hello 1.....relock bootloader with htcdev from google
2.....download this ruu and run it from fastboot http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ sorry i fixed the link
3..change cid to 0_32 as bellow
now let's change CID so we can run the RUU.EXE for your ModelID: PN0712000
in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>fastboot oem writecid CWS__0_32 <-- two underscores
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
then take all the avalible updates
good guid here http://forum.xda-developers.com/showthread.php?t=2541082

bygrave said:
hello 1.....relock bootloader with htcdev from google
2.....download this ruu and run it from fastboot http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ sorry i fixed the link
3..change cid to 0_32 as bellow
now let's change CID so we can run the RUU.EXE for your ModelID: PN0712000
in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>fastboot oem writecid CWS__0_32 <-- two underscores
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
then take all the avalible updates
good guid here http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thanks a lot for your reply. I am downloading the RUU now and till it finishes i have a quick question. Why should i change the CID to (0_32) instead of (11111111)?
Thanks again.

because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
bygrave said:
because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
Click to expand...
Click to collapse
also write cid like this fastboot oem writecid HTC__032
capital HTC, two underscores, then 032

bygrave said:
because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
also write cid like this fastboot oem writecid HTC__032
capital HTC, two underscores, then 032
Click to expand...
Click to collapse
Thanks a lot, now i get it.
One last question, should i change the CID before running the RUU or after running it?

yes it needs to be changed before u run the ruu. i always run the ruu from in fastboot mode
Sent from my HTC One using Tapatalk

let us know how u got on
Sent from my HTC One using Tapatalk

bygrave said:
let us know how u got on
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Unfortunately although i changed the CID but the RUU failed with an error that the RUU doesn't match my phone model number. :crying:

fastboot getvart all
and give us the results.
u did relock you're bootloader didn't u
Sent from my HTC One using Tapatalk

C:\mini-sdk>fastboot getvart all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an

DArkSm4sh said:
C:\mini-sdk>fastboot getvart all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
Click to expand...
Click to collapse
fastboot getvar all
NOT getvarT
Remove your imei and serial number

sorry its fastboot getvar all
Sent from my HTC One using Tapatalk

bygrave said:
sorry its fastboot getvar all
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
The bootloader is still unlocked, should i relock it first?
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4324mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s

yes needs to be locked for it to work
---------- Post added at 11:21 PM ---------- Previous post was at 11:14 PM ----------
just looking for a ruu u are in tawian is that write

did you get this sorted

[Q] HTC ONE Bricked S off

ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.

Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
if you can get to bootloader you're not bricked.
don't fiddle with your phone - just leave it like it is.
someone here who knows way more about this stuff than I do will be able to tell you what you need to do.

Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition

raghav kapur said:
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition
Click to expand...
Click to collapse
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28

Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
Download and install latest android sdk http://developer.android.com/sdk/index.html
download in install latest htc sync (for drivers installation) then uninstall it, the drivers still be installed. http://www.htc.com/www/software/htc-sync-manager/
go to the folder you installed the android sdk then ---> sdk/platform-tools. Adb.exe and fastboot.exe should be in this folder. Always work in this folder (where adb and fastboot.exe are).
boot your phone in bootloader mode, select fastboot and connect usb cable to computer
Right click on a blank space in the folder where fastboot/adb are then select ''open a cmd prompt here''
in the command prompt type
Code:
fastboot getvar all
and copy paste output here MINUS IMEI AND SN
and please tell us what operating system are you using on your ocmputer? windows 7, 8.0 or 8.1?

How do I get into fastboot mode?

Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
and how did you messed your phone?
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
Jamesdbritt said:
How do I get into fastboot mode?
Click to expand...
Click to collapse
when you are in bootloarder mode, select ''fastboot''. use vol up and down to navigate then power button to select.
{
"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"
}
When in fastboot mode you'll have a screen similar to this with fastboot highlighted in red:

When I right click there is no cmd option

Jamesdbritt said:
When I right click there is no cmd option
Click to expand...
Click to collapse
sry my bad
hold left SHIFT + right click

Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..

Jamesdbritt said:
Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..
Click to expand...
Click to collapse
please can you make a screenshot of your cmd prompt and post it here? I want to see the command you typed and the ouput

commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable

Jamesdbritt said:
commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable
Click to expand...
Click to collapse
type this command:
Code:
fastboot devices
what is the output?

C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>

Jamesdbritt said:
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL -------> 1 ''o'' is missing from fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
fastboot is case sensitive don't use capitals letter unless specified
type
''fastboot getvar all'' NOT ''FASTBOT GETVAR ALL''
and there is a letter missing at fastboot

C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>

Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so now type ''fastboot getvar all'' DON'T USE CAPITALS!

C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA39DS900733
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>

Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so you want to go back to stock rom or you want to install a custom rom?

alray said:
ok so you want to go back to stock rom or you want to install a custom rom?
Click to expand...
Click to collapse
stock right now I know SuperSU is not installed if that means anything
I was having data connection problems before all this started